Custom Astro websites. Built on Cloudflare.

Explore Plyo

Website accessibility: where to start

What WCAG actually asks for, the handful of fixes that cover most of it, and why accessible websites tend to be faster and rank better too.

A line drawing of a focus ring around an element beside a contrast circle on a pale pink cover

Accessibility means people can use your website regardless of how they browse it: with a keyboard, with a screen reader, with low vision, with a tremor, or on a phone in bright sun. The standard most organisations work to is WCAG 2.2 at level AA. You do not need to read it to make real progress.

Why it is worth doing beyond compliance

Around one in five people has a disability of some kind. That is a fifth of your audience who may be unable to complete your enquiry form.

The overlap with everything else is large. Headings that make sense to a screen reader make sense to a search engine. Captions get indexed. Good contrast helps anyone outdoors. Keyboard support helps power users. Accessibility work is rarely only accessibility work.

The fixes that cover most of it

1. Colour contrast

Body text needs a contrast ratio of at least 4.5 to 1 against its background. Large text needs 3 to 1. The usual offenders are light grey placeholder text, pale text over photographs, and brand colours used for small type.

Check your palette once, write the passing combinations into your brand guide, and the problem stops recurring.

2. Keyboard access

Unplug your mouse and press Tab through a page. You should be able to reach every link, button and field, see clearly where you are, and never get stuck. Custom dropdowns, modals and sliders are where this usually breaks.

3. Real headings

One h1 per page, then h2 and h3 in order, with nothing skipped. Screen reader users navigate by heading the way sighted users skim. Headings are structure, not a way to make text big.

4. Alt text that says something

Describe what the image shows and why it is there. “Team filtering by location and specialty” beats “screenshot”. If an image is purely decorative, give it an empty alt so it is skipped rather than read out.

5. Labelled form fields

Every input needs a visible label that stays visible when typing. Placeholder text alone disappears the moment someone starts. Errors need to say what went wrong and how to fix it, in text, not colour alone.

6. Respect reduced motion

Some people get genuinely unwell from parallax and large movement. Honour the operating system setting and turn animation off for those visitors. It is a few lines of CSS.

What automated checkers will and will not find

Tools like axe or Lighthouse catch perhaps a third of issues: contrast, missing alt, unlabelled fields. They cannot tell you whether your alt text is useful, whether the tab order makes sense, or whether an error message is comprehensible. Run the tool, then do the keyboard pass yourself.

Our free website audit includes an accessibility pass, so you can see where you stand before committing to anything.

Updated

FAQ

Common questions

Ask a question

Is my business legally required to have an accessible website?

In Australia the Disability Discrimination Act applies to online services, and complaints have been upheld. In the US it is the ADA, in the EU the European Accessibility Act. The specifics vary, the direction does not.

Will accessibility make my site look worse?

No. It constrains contrast and asks for visible focus states. Plenty of well known, visually strong sites meet AA. Most of the work is invisible.

How much does it cost to fix?

Built in from the start, close to nothing. Retrofitted onto a finished site, it depends on how custom the components are. Either way the first step is a proper audit so you know the size of it.

About Plyo Studio

Custom Astro websites. Built on Cloudflare.

Plyo Studio is an independent web studio that designs and builds fast, search-ready websites, web apps and interactive maps. Sites are custom-built in Astro and hosted on Cloudflare, so they load quickly and are easy for search engines and AI answer engines to read.

Founded by Chloe Nixon, a full stack developer and UI/UX designer from Australia, and Micky, a software engineer from New Zealand. Clients work directly with the founders from the first call to launch. Typical work: custom websites, migrations off Webflow, WordPress, Wix and Squarespace, web apps, and interactive maps and GIS. Projects are quoted at a fixed price before work starts.