The Accessibility Mistakes Designers Should Fix First, by the Numbers

This is the most practical of the trends that change the work, because the numbers are public and the fixes are small. Here is where to start.

What Accessibility Problems Should Designers Fix First?

Low-contrast text first: it appears on 83.9% of the top million home pages in the WebAIM Million 2026. Then the problems that start in the design file: buttons and links without a name, form fields without visible labels, images without a text alternative, and tap targets smaller than 24 by 24 pixels. Fix them in the design, before handoff, where each one takes minutes.

The Numbers Behind the Problem

Every year WebAIM runs automated checks on the home pages of the top million websites. In the February 2026 run, the checks found WCAG 2 errors on 95.9% of them, up from 94.8% a year earlier, with 56.1 errors per page on average. Automated checks catch only part of what real people run into, so the true picture is worse, and the list of the most common problems has barely moved in years.

Triage, Like an Emergency Room

An emergency room doesn't treat patients in the order they arrive. It sorts them by how badly and how many people are affected. Accessibility work goes the same way. Contrast comes first because it affects the most pages and the most readers, including anyone looking at a phone in sunlight. Names for buttons and links come next, because without them a screen reader user can't tell what a control does. Everything else follows.

Five Checks Before Handoff

1. Contrast on every text style: WCAG 2.2 asks for at least 4.5:1 for normal text and 3:1 for large text, which starts at 18 point, or 14 point bold. Check the styles once in the library, and every screen that uses them is covered.
2. A name for every icon control: write the accessible name next to each icon-only button and link in your spec, such as "Search" or "Close dialog".
3. Visible labels on every field: a placeholder disappears as soon as someone types. Keep a label above the field.
4. Tap targets of at least 24 by 24 pixels: that is the WCAG 2.2 minimum at level AA, or enough spacing around a smaller target. Larger is kinder.
5. Text alternatives for images that carry meaning: say what the image tells the user. Decorative images get marked as decorative.

The free DesignPath courses Color Accessibility & Semantic Systems and Button Labels and CTAs cover the first two checks in depth, with practice tasks. Both are in the course library.

"Isn't WCAG 3 Coming In 2026?"

That claim went around design social media this year, and it's wrong. WCAG 3 is still a W3C working draft; the latest one was published in September 2026, and the W3C says it isn't expected to be a finished standard for a few more years. WCAG 2.2 is the version to design and test against today, and WCAG 2 will stay valid for years after WCAG 3 arrives.

The other objection I hear is "developers handle accessibility". They fix the code. Contrast, labels, names and sizes are decided in the design file, and that's where they're cheapest to get right.

Make Accessibility Part of Your Craft

Has an audit ever sent issues back to your design file? Do your text styles have a contrast check built in? Would a short list of checks before handoff save you a release-week scramble?

If that is three yeses, start with the two accessibility courses in the course library, or read how accessibility fits among the other ui ux design trends that change the work. Treating accessibility-first design as a habit is one of the clearest signs of a designer moving toward senior-level craft.