Web Development

Web Accessibility with WCAG 2.2: A Practical Guide for Business and Government Websites

Almost all home pages of popular websites still fail automated accessibility tests. Learn the most common errors and the new WCAG 2.2 criteria you need to meet.

By Oemah Solution Editorial Updated 3 min read

This article was translated from Bahasa Indonesia with AI assistance and reviewed by our team.

Web accessibility means that websites and applications can be used by everyone — including users with visual, hearing, motor or cognitive impairments. For government agencies that serve all citizens, and for businesses that want to reach the widest possible market, accessibility is not an add-on feature but part of quality.

In reality, most websites are still far from the standard.

The scale of the problem: WebAIM Million data

Every year, WebAIM tests the home pages of one million popular websites using automated checking tools. The February 2026 results show that 95.9% of home pages have detected WCAG 2 failures, with an average of 56.1 errors per page.

The six most frequently found types of error:

Type of error Percentage of pages
Low-contrast text 83.9%
Images without alternative text 53.1%
Form inputs without labels 51%
Empty links 46.3%
Empty buttons 30.6%
Document language not declared 13.5%

The good news is that almost all of the errors above are relatively easy to fix and can be prevented from the design and development stage. It should also be noted that automated checks catch only some of the problems; manual testing is still needed.

What's new in WCAG 2.2

WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine new success criteria. Criterion 4.1.1 Parsing was declared obsolete and removed. Some of the new criteria most relevant to everyday websites and applications:

  • 2.4.11 Focus Not Obscured (Minimum) — level AA. An element that has keyboard focus must not be entirely hidden by content created by the site, such as a sticky header or cookie banner.
  • 2.5.8 Target Size (Minimum) — level AA. Touch or click targets must be at least 24 × 24 CSS pixels, with some exceptions.
  • 2.5.7 Dragging Movements — level AA. Functions that use dragging movements must have an alternative that works with a single click or tap.
  • 3.2.6 Consistent Help — level A. Help mechanisms (for example contact details or chat) are placed consistently on every page.
  • 3.3.7 Redundant Entry — level A. Users are not forced to retype information they have already entered in the same process.
  • 3.3.8 Accessible Authentication (Minimum) — level AA. The login process must not require users to solve a puzzle, remember something or retype something without an alternative — for example by allowing paste and password managers.

A practical checklist for your team

  1. Colour contrast. Test text and background colour combinations at the design stage, including in dark mode.
  2. Alternative text. Give every informative image a descriptive alt; give decorative images alt="".
  3. Form labels. Associate every input with a <label>; do not rely only on placeholders.
  4. Named links and buttons. Icons without text must be given a name that screen readers can read (for example via aria-label).
  5. Declare the language. The lang attribute on the <html> element helps screen readers pronounce text correctly.
  6. Keyboard navigation. Make sure all functions can be reached with the Tab key and that the focus indicator is always visible.
  7. Touch target size. Apply a minimum of 24 × 24 CSS pixels for adjacent buttons and links.

Accessibility also benefits business

Many accessibility practices align with SEO and general usability: alternative text helps search engines understand images, a tidy heading structure makes it easier for readers to scan a page, and clear forms reduce the rate of abandoned submissions. Building accessibility into the definition of done for every feature is far cheaper than fixing it after the site has launched.

#accessibility#wcag#ux#web development

Sources & references

This article is a summary and interpretation by the Oemah Solution team of the sources below. Refer to the original sources for full details and context.

  1. The WebAIM Million WebAIM · webaim.org
  2. What's New in WCAG 2.2 W3C Web Accessibility Initiative · w3.org
  3. Web Content Accessibility Guidelines (WCAG) 2.2 W3C · w3.org