TECH Oct 18, 2026 · by Skills Team

Web Accessibility 2026: WCAG Checklist for Websites

A practical 2026 WCAG checklist for business websites: what WCAG 2.2 Level AA requires, what changed in 2.2, where WCAG 3.0 stands, and how to audit your site before the law or a lawsuit forces the issue.

Web Accessibility 2026: WCAG Checklist for Websites

The Short Answer

If your website cannot be used by everyone, it is not finished. A web accessibility WCAG checklist is the most practical way to find out where your business website stands, because it turns a large technical standard into checks your team can actually run. The World Health Organization estimates that 1.3 billion people, about 1…

If your website cannot be used by everyone, it is not finished. A web accessibility WCAG checklist is the most practical way to find out where your business website stands, because it turns a large technical standard into checks your team can actually run. The World Health Organization estimates that 1.3 billion people, about 1 in 6 people worldwide, experience significant disability. When your site blocks those visitors, you lose customers, damage your brand, and invite legal risk. This guide explains what WCAG requires in 2026, what changed in WCAG 2.2, where WCAG 3.0 stands, and gives you a checklist you can apply this week.

What Is Web Accessibility and What Is WCAG?

Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with your website. That includes people who are blind and use screen readers, people with low vision who zoom or increase contrast, people who cannot use a mouse, people who are deaf or hard of hearing, and people with cognitive differences who need clear language and predictable behavior.

WCAG, the Web Content Accessibility Guidelines, is the international standard that defines how to achieve that. It is published by the World Wide Web Consortium (W3C).

WCAG organizes its requirements under four principles, often called POUR:

  • Perceivable: users must be able to perceive content with at least one sense. Images need text alternatives, video needs captions, and text needs enough contrast.
  • Operable: users must be able to operate the interface. Everything works with a keyboard, nothing traps focus, and users get enough time.
  • Understandable: content and behavior must make sense. Page language is declared, labels are clear, and errors are explained.
  • Robust: content must work with current and future assistive technologies. Interactive elements expose their name, role, and state.

Each principle contains testable success criteria, grouped into three conformance levels. Level A is the minimum baseline. Level AA is the level referenced by laws and regulations almost everywhere, and it is the target most businesses should aim for. Level AAA is the highest level and is usually applied selectively.

Web Accessibility WCAG Checklist: The Standard to Follow in 2026

The standard to test against in 2026 is WCAG 2.2 Level AA. WCAG 2.2 was published as a W3C Recommendation in October 2023, and it remains the current standard. It is backward compatible, which means content that meets WCAG 2.2 also meets WCAG 2.1 and 2.0. In total, WCAG 2.2 has 86 success criteria, with 55 of them at Levels A and AA combined.

What about WCAG 3.0? It is still a working draft, not a finished standard. The W3C published an updated WCAG 3.0 Working Draft in September 2026, and the draft itself warns that it should not be cited as anything other than a work in progress. WCAG 3.0 will move from the pass-or-fail A, AA, and AAA model toward outcome-based scoring with Bronze, Silver, and Gold levels. A final Recommendation is not expected before 2028. The W3C advises organizations to keep meeting WCAG 2.2 Level AA requirements while WCAG 3.0 is being developed. Conforming to WCAG 2.2 AA today is also the best preparation for whatever comes next.

What Is New in WCAG 2.2?

WCAG 2.2 adds nine new success criteria and removes one obsolete criterion, 4.1.1 Parsing, which modern browsers made unnecessary. Six of the nine new criteria sit at Levels A or AA:

CriterionLevelWhat it requires
2.4.11 Focus Not Obscured (Minimum)AAWhen a component receives keyboard focus, it must not be completely hidden behind sticky headers, cookie banners, or chat widgets.
2.5.7 Dragging MovementsAAAnything that works by dragging must also work with a single tap or click, unless dragging is essential.
2.5.8 Target Size (Minimum)AAPointer targets must be at least 24 by 24 CSS pixels, or have enough spacing around them.
3.2.6 Consistent HelpAHelp options, such as contact links or chat, must appear in the same relative place across pages.
3.3.7 Redundant EntryAUsers must not have to re-enter information they already provided within the same process.
3.3.8 Accessible Authentication (Minimum)AALogin must not require a cognitive test, such as solving a puzzle or retyping characters, unless an alternative exists.

The remaining three new criteria, Focus Not Obscured (Enhanced), Focus Appearance, and Accessible Authentication (Enhanced), are Level AAA.

United States: ADA Title III lawsuits keep rising

According to law firm Seyfarth Shaw, plaintiffs filed 3,117 federal website accessibility lawsuits in 2025, up 27 percent from 2,452 in 2024. Those cases made up 36 percent of all federal ADA Title III lawsuits filed that year. Industry estimates put typical website accessibility settlements in the range of $5,000 to $50,000, before legal fees and remediation costs.

Europe: the European Accessibility Act is now enforceable

The European Accessibility Act, Directive (EU) 2019/882, has applied since 28 June 2025. It reaches private businesses that sell to EU consumers, including companies based outside the EU. The technical reference standard, EN 301 549, incorporates WCAG Level AA criteria. Penalties are set nationally and vary widely: Germany allows fines of up to 100,000 euros per infringement, Ireland allows fines of up to 60,000 euros along with possible imprisonment, and Spain allows fines of up to 1,000,000 euros for very serious infringements.

The business case beyond compliance

The legal risk is real, but the opportunity is larger. With roughly 1 in 6 people worldwide living with significant disability, an inaccessible checkout, booking form, or contact page quietly turns away a large share of your market. Accessible sites also tend to be better for everyone: clearer headings help search engines and good contrast helps mobile users in bright sunlight. Accessibility work is simply good web development, and it compounds over time instead of expiring.

The Practical Web Accessibility WCAG Checklist for Business Websites

Use this checklist as your audit worksheet. Check each item on your most important pages first: the home page, key landing pages, contact and quote forms, and the full checkout or signup flow. A process only conforms if every step of it conforms.

Perceivable: can everyone perceive the content?

  • Every meaningful image has a concise, accurate alt text. Decorative images are marked as decorative so screen readers skip them.
  • All pre-recorded video has captions, and video with important speech has a transcript.
  • Text can be resized to 200 percent without loss of content or function, and the page reflows to a single column at 320 CSS pixels wide without horizontal scrolling.

Operable: can everyone operate the interface?

  • Every interactive element is reachable and usable with a keyboard alone, in a logical order that matches the visual layout.
  • A visible focus indicator is always present, and the focused element is never fully hidden behind sticky headers, cookie banners, or chat widgets.
  • Click and tap targets are at least 24 by 24 CSS pixels, or have enough spacing to prevent accidental activation.
  • Page titles, headings, and link text are descriptive. Links never say "click here" without context.

Understandable: does everything make sense?

  • The language of each page is declared in the HTML, and passages in a different language are marked.
  • Form fields have visible, persistent labels, not placeholder text alone. Required fields and formats are explained before submission.
  • Errors are described in text, identify the field in error, and suggest a correction where possible.
  • Multi-step forms do not ask users to re-enter information already provided, unless re-entry is essential for security.

Robust: does it work with assistive technology?

  • Markup uses proper semantic HTML: real buttons for actions, real links for navigation, headings in a logical hierarchy, and lists marked as lists.
  • Modals trap focus while open, return focus to the triggering element when closed, and can be dismissed with the Escape key.

How to Test Your Website Against This Checklist

Automated scanners are a useful starting point, but they catch only a fraction of real barriers. Industry reporting consistently notes that automated checkers find roughly a quarter to a third of accessibility issues. Use a layered testing approach:

  1. Run an automated scan on your key templates to catch repeatable issues such as missing alt text, empty headings, and contrast failures.
  2. Do a keyboard-only pass. Unplug the mouse and complete your main conversion journey: find a product or service, fill in the form, and reach the confirmation step.
  3. Test with a real screen reader, such as NVDA or VoiceOver, on at least the home page, one content page, and one form.
  4. Document everything. Record each failure with the page address, the criterion number, and a screenshot.

One warning: quick-fix accessibility overlays and widgets do not make a site compliant. Reports on 2025 litigation show that sites running overlays still get sued, because an overlay cannot fix broken markup, unlabeled controls, or a confusing flow. Real accessibility is built into the code, the design, and the content.

Common Accessibility Failures We See on Business Websites

WebAIM's 2025 analysis of the top one million home pages found WCAG failures on 94.8 percent of them, with an average of 51 errors per page. Most of those failures come from a small set of repeat offenders:

  • Low contrast text: light gray text on a white background is the single most common failure, and it hurts every visitor, not only users with low vision.
  • Missing or meaningless alt text: images with no alt text, or alt text that says "image" or repeats the file name, leave screen reader users with nothing.
  • Missing form labels: placeholders that disappear when you type are not labels, and they fail the moment a user starts filling in the field.

Fixing these categories often removes the majority of errors on a typical business site. That is why a focused audit beats a vague intention to "be more accessible." A structured review of your UI and UX design will catch many of these problems before they reach production.

Building Accessibility Into Every Redesign and Release

Accessibility is cheapest when it is part of the process, not a project at the end. Add accessibility checks to your definition of done: every new component ships with semantic markup, labels, contrast, keyboard support, and focus handling. Add it to QA, so releases are tested with a keyboard and at high zoom. Schedule a full re-audit at least once a year, plus a smaller check after every major redesign.

If you are planning a rebuild, accessibility should be in the brief from day one, alongside content, SEO, and conversion goals. Our website redesign checklist for 2026 covers the wider planning steps.

Finally, publish an accessibility statement. Under the European Accessibility Act it is a legal requirement for in-scope services, and everywhere else it is good practice. State your conformance target and provide a real feedback channel.

FAQ

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 is a backward-compatible update to WCAG 2.1. It adds nine new success criteria, six of which apply at Levels A and AA. It also removes the obsolete 4.1.1 Parsing criterion. A site that meets WCAG 2.2 AA automatically meets WCAG 2.1 AA.

Is WCAG 2.2 Level AA legally required?

WCAG itself is a technical standard, not a law, but laws and regulations point to it. In the US, courts treat WCAG 2.1 Level AA as the de facto standard in ADA Title III cases. In the EU, the European Accessibility Act references EN 301 549, which incorporates WCAG Level AA criteria. If you serve customers in the US or the EU, treat Level AA as your legal baseline.

Do I need to worry about WCAG 3.0 yet?

No. WCAG 3.0 is still a working draft, with a final Recommendation not expected before 2028. Nothing in law requires it yet. The W3C advises organizations to keep meeting WCAG 2.2 Level A and AA requirements.

Does the European Accessibility Act apply to businesses outside the EU?

Yes, if you sell products or services to EU consumers. The Act applies based on where your customers are, not where your company is registered. Penalties are set by each member state's national law.

Will an accessibility overlay or widget make my website compliant?

No. Overlays cannot fix broken markup, unlabeled controls, or confusing flows, and sites using overlays have still faced lawsuits. Genuine compliance requires fixing the underlying code, design, and content, plus manual testing with a keyboard and a screen reader.

How often should I audit my website for accessibility?

Run a full audit at least once a year, and re-check after every major redesign, platform migration, or template change.

Accessibility is not a one-time project. It is a standard of quality that decides whether real people can use your website, and in 2026 it is also a legal obligation in your most important markets. Work through the checklist above, fix the failures on your highest-traffic pages and conversion flows first, and build the checks into every future release. If you want expert help making your website accessible and compliant, contact SK Technology and we will audit your site against WCAG 2.2 and build a practical remediation plan.

#web accessibility#WCAG#WCAG 2.2#ADA compliance#European Accessibility Act#website audit#inclusive design