Last updated: October 5, 2026 · 3 min read · By Ali Raza
Start with the six issues that make up about 96% of detected errors in the 2026 WebAIM Million report: low-contrast text, missing alt text, missing form labels, empty links, empty buttons and missing page language. Then test every page with the keyboard only, check headings and focus, make forms and error messages clear, add captions to video, and check the newer WCAG 2.2 criteria such as focus visibility, target size and accessible logins.
WCAG has dozens of success criteria, which can feel overwhelming for a small business. The good news is that a few issues cause most real-world problems, and many can be fixed once in a template.
This checklist puts the high-impact fixes first. It is a starting point, not a substitute for a full audit.
Most common failures on the top 1 million home pages (WebAIM, 2026)
1. Fix the six most common issues
- Contrast: normal text needs a contrast ratio of at least 4.5:1, large text 3:1. Check your brand colours, placeholder text and text on images.
- Alt text: describe meaningful images; mark decorative images with empty alt so screen readers skip them.
- Form labels: every field needs a visible label tied to it in code; placeholders are not labels.
- Empty links and buttons: icon links such as social icons, search and menu buttons need an accessible name.
- Page language: set the lang attribute on every page.
2. Test with the keyboard
- Put the mouse away and use Tab, Shift+Tab, Enter, Space and arrow keys.
- Can you reach every link, button, menu and form field?
- Can you always see where focus is?
- Can you open and close menus, pop-ups and cookie banners?
- Is there a “skip to content” link?
3. Structure and content
- One H1 per page, then headings in logical order.
- Descriptive link text: “View kitchen projects”, not “Click here”.
- Text that can be zoomed to 200% without breaking the layout.
- Captions for videos and transcripts for audio.
- No content that flashes or moves automatically without a way to pause it.
4. Forms and checkout
- Clear error messages that explain what went wrong and how to fix it.
- Required fields marked in text, not by colour alone.
- Autocomplete attributes for name, email, address and phone.
- Do not ask users to re-enter information they already gave in the same process.
5. Newer WCAG 2.2 checks
- Focus not obscured: sticky headers or chat widgets must not hide the focused element.
- Target size: tap targets at least 24 by 24 CSS pixels, or enough space around them.
- Dragging movements: provide a single-pointer alternative to drag-and-drop.
- Accessible authentication: do not rely on memory puzzles; allow password managers and paste.
- Consistent help: keep help and contact options in the same place across pages.
Avoid shortcuts: our guide to accessibility overlays explains why. For legal context, see ADA, AODA and the European Accessibility Act. Want a full audit? Our web accessibility service tests and fixes all of this for you.
Frequently asked questions
What are the most common accessibility errors on websites?
According to the 2026 WebAIM Million report: low-contrast text, missing alt text, missing form labels, empty links, empty buttons and missing page language.
What contrast ratio does WCAG AA require?
At least 4.5:1 for normal text and 3:1 for large text.
What is new in WCAG 2.2?
New success criteria include focus not obscured, target size, dragging movement alternatives, accessible authentication, consistent help and avoiding redundant entry.
Can automated tools check WCAG compliance?
They catch many issues, such as contrast and missing labels, but not all. Manual keyboard and screen reader testing is needed for a full picture.