Skip to content
Start a Project
tech@softlixx.com
+92 347 0970 627

Web DevelopmentBy Softlixx TeamPublished Updated 9 min read

What does web accessibility ask of a business website?

I read the W3C standard, official pages on the law in four places, two large studies of real websites and a regulator's order, and put it in plain language.

On this page

The short answer

It asks that people with disabilities can use your website, measured against the Web Content Accessibility Guidelines (WCAG). The laws I read that name a standard point to Level AA, and the W3C says meeting WCAG 2.2 also meets the older versions. Most websites fall short: WebAIM found detected failures on 95.9% of the top million home pages in 2026. Laws differ by country, so check your own case. That is what I found after reading the sources below.

Key takeaways

  • The Web Content Accessibility Guidelines (WCAG) 2.2 are the standard, and Level AA is the level the laws I read point to.
  • The World Health Organization estimates 1.3 billion people, 16% of the world's population, experience significant disability.
  • WebAIM found detected WCAG failures on 95.9% of the top 1,000,000 home pages in 2026, most often low contrast text.
  • EU accessibility rules apply to products and services placed on the market after 28 June 2025, except very small service businesses.
  • The US Federal Trade Commission ordered an overlay maker to pay $1 million over claims its tool could make any website compliant.
  • Automated tools find only part of the problems: in a UK government test, 42 of 143 barriers were missed by every tool.

What does web accessibility mean, and what is the standard?

It means people with disabilities can use your website. The standard laws point to is the Web Content Accessibility Guidelines (WCAG), now at version 2.2.

Softlixx builds business websites, so I have a stake here, and accessibility work is easy to sell with fear of lawsuits. I report what the official pages say, with their dates, and none of this is legal advice. Speed is the other half of how well a site works, covered in the website speed research.

The W3C's introduction to web accessibility defines it as websites, tools and technologies designed and developed so that people with disabilities can use them. Its WCAG 2 overview, updated in September 2026, says WCAG 2.2 has 13 guidelines under 4 principles: perceivable, operable, understandable and robust. Each requirement, called a success criterion, sits at one of three levels: A, AA or AAA. WCAG 2.2 was published in October 2023 and is also an ISO standard, ISO/IEC 40500:2025.

The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.

Tim Berners-Lee, W3C Director and inventor of the World Wide Web, quoted by the W3C. Read the source

Who does website accessibility affect?

About 1 in 6 people worldwide, and the W3C says it helps people without disabilities too.

The World Health Organization estimates that 1.3 billion people experience significant disability: 16% of the world's population, or 1 in 6. The W3C adds that web accessibility also benefits people without disabilities, and that it is required by law in many situations. One of its examples: an accessible website does not rely on the mouse, and makes all functionality available from a keyboard.

The US Justice Department's 2022 guidance puts it in physical terms: an inaccessible website can exclude people just as much as steps at an entrance to a physical location.

What did WCAG 2.2 add, and which level should you aim for?

Level AA is the level named by the laws I read. Meeting WCAG 2.2 also meets the older versions.

The W3C overview says WCAG 2.2 adds 9 success criteria, and that content which conforms to WCAG 2.2 also conforms to WCAG 2.1 and 2.0. The standard itself lists the 9 with their levels: 3 at Level A, 3 at AA and 3 at AAA. One new AA rule, Target Size (Minimum), asks that things you tap or click are at least 24 by 24 CSS pixels, with some exceptions. Older AA rules ask for a contrast ratio of at least 4.5:1 for text and 3:1 for large text.

Four WCAG 2.2 rules with numbers you can check
RuleWhat it asksLevel
Text contrastAt least 4.5:1 against the background.AA
Large text contrastAt least 3:1.AA
Target size, new in 2.2At least 24 by 24 CSS pixels, with some exceptions.AA
KeyboardEverything works from a keyboard.A

Source: W3C.

The laws that name a standard use AA. The US rule for state and local governments names WCAG 2.1 Level AA, and the EU's current reference standard is based on WCAG 2.1 Level AA. In September 2026 the European standard EN 301 549 was updated to WCAG 2.2, but it is not yet the legal reference for the European Accessibility Act.

My readingFor a new website, I would set one simple target: WCAG 2.2 Level AA. It covers the 2.1 AA benchmark the laws name today, and the European standard has already moved to 2.2.

What goes wrong most often on real websites?

Low contrast text, missing image descriptions and unlabelled forms, on nearly every popular home page.

The WebAIM Million, a yearly test of the top 1,000,000 home pages, found detected WCAG 2 failures on 95.9% of them in February 2026, up from 94.8% in 2025. It detected 56,114,377 errors, an average of 56.1 per page. Low contrast text appeared on 83.9% of home pages, missing alternative text for images on 53.1% and missing form input labels on 51%. 96% of all detected errors fell into six categories.

The six most common accessibility errors on the top 1,000,000 home pages

Share of home pages with each error, February 2026 (WebAIM)

Low contrast text83.9%
Missing image alt text53.1%
Missing form input labels51%
Empty links46.3%
Empty buttons30.6%
Missing page language13.5%

Bars use a scale of 0 to 100%. Automated checks of home pages only.

Source: WebAIM.

The HTTP Archive's Web Almanac 2025 accessibility chapter found that colour contrast, link naming, heading hierarchy and image alt text remain the top four issues, and that only 31% of mobile sites meet minimum colour contrast requirements. The median Lighthouse accessibility score, from Google's automated checker, improved by 1% to over 85%.

A perfect score doesn't guarantee full accessibility.

Bogdan Lazar and Mike Gifford, authors of the Web Almanac 2025 accessibility chapter. Read the source

My readingWebAIM tests home pages with automated checks only, and says not every failure can be detected that way. So I read 95.9% as a floor. The six common errors are the cheapest place to start, because they are easy to find and fix.

Which laws apply to a business website?

It depends on where you sell and who you are. I read the official pages for the US, the EU, Great Britain and Pakistan, and none of this is legal advice.

In the EU, Your Europe says the European Accessibility Act applies to products and services placed on the market after 28 June 2025, such as online shops, ticketing platforms and banking services. A service-based business with fewer than 10 employees and under €2 million in turnover is exempt. Any business can claim a disproportionate burden, but must provide evidence, reviewed every 5 years.

In the US, the Justice Department's Title II rule names WCAG 2.1 Level AA for state and local governments, with deadlines moved in April 2026 to 26 April 2027, or 26 April 2028 for smaller areas. For businesses open to the public, its 2022 guidance says the ADA applies to what they offer on the web, but that the Department does not have a regulation setting out detailed standards. The guidance has no legally binding effect.

In Great Britain, the Equality and Human Rights Commission's 2011 code says websites may in themselves be a service, and that the duty to make adjustments is anticipatory. In Pakistan, the ICT Rights of Persons with Disability Act, 2020 covers the Islamabad Capital Territory and says the Government shall ensure that all websites hosted by Pakistani website service providers are accessible. Neither names a technical standard.

What the official pages say, by place
WhereWho it coversStandard namedKey date
European UnionProducts and services such as online shops and banking. Very small service firms are exempt.EN 301 549 V3.2.1, based on WCAG 2.1 AAOn the market after 28 June 2025
US, governmentState and local governments (ADA Title II).WCAG 2.1 Level AA26 April 2027, or 2028 for smaller areas
US, businessesBusinesses open to the public (ADA Title III).None in a regulationNon-binding guidance, 2022
Great BritainService providers whose website is part of the service.None namedIn force since 1 October 2010
PakistanIslamabad Capital Territory. The duty is on the Government.None namedAct of 2020

Sources: U.S. Department of Justice (Title II rule), U.S. Department of Justice (web guidance), Your Europe, AccessibleEU, Equality and Human Rights Commission, The Gazette of Pakistan.

My readingI read one pattern even where the law is vague: where a standard is named, it is WCAG at Level AA. I would ask a lawyer about your own markets, and start the work anyway.

Can a plug-in make my website compliant?

No source I read says so, and the US Federal Trade Commission acted against a company that claimed it.

In January 2025 the Federal Trade Commission announced an order requiring accessiBe, a software provider, to pay $1 million to settle allegations that it misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with WCAG. The FTC alleged that the tool did not make all user websites WCAG-compliant.

Companies looking for help making their websites WCAG compliant must be able to trust that products do what they are advertised to do

Samuel Levine, Director of the FTC’s Bureau of Consumer Protection. Read the source

The Web Almanac authors say these overlays, widgets added on top of a site, often promise quick-fix compliance but fall short of addressing complex accessibility challenges, and that relying on them often leads organisations to stop investing in proper accessibility.

My readingA widget can add features on top, but it does not fix the code underneath. The fixes still have to be made in the website itself.

How do you check your own website?

Run the free checks, then use the site with a keyboard and get a person to review it. Tools alone find only part of the problems.

The W3C's Easy Checks cover a few issues, such as alt text, contrast, keyboard focus and form labels. They are quick rather than exhaustive, and the W3C warns that a page could pass them and still have significant barriers. Its introduction adds that no tool alone can determine if a site meets the guidelines, and that knowledgeable human evaluation is required.

In a landmark 2017 test, the UK Government Digital Service built a page with 143 failures. The automated tools it tested picked up 71% of them together, and 42 were missed by all of them. Google's developer tools alone picked up 17%. Google's current DevTools accessibility reference says some errors are easy to detect automatically, but the only way to find others is to try the page with a keyboard or screen reader yourself.

How much automated tools found on a page built to fail

A UK government test page with 143 accessibility failures (2017).

  • Found by the tools together71%All the tools tested, combined. Google’s developer tools alone found 17%.
  • Missed by every tool42 of 143Barriers that none of the tools tested picked up.

Source: GOV.UK Government Digital Service.

A good analogy is to think of a testing tool as like using a spellchecker.

Mehmet Duran, Government Digital Service, UK, writing in 2017. Read the source

My readingI read the tools the way GDS does: worth running every time, but no proof of a finished job. A keyboard test takes a few minutes and finds problems the tools cannot.

What should a business do first?

If I were starting today, I would set the target, fix the common errors, then test by hand. It is my reading of the sources above.

  • Aim for WCAG 2.2 Level AAThe laws I read name AA, and 2.2 also meets 2.1 and 2.0.
  • Build it in from the startThe W3C says that is the most efficient and effective way.
  • Fix the six common errorsWebAIM found 96% of detected errors fall into six categories.
  • Use the site by keyboardGoogle says some errors only show with a keyboard or screen reader.
  • Add a human reviewGDS advises manual checks, an audit and user testing on top of tools.
  • Skip the overlay plug-insThe FTC acted against claims that a tool could make any site compliant.
  • Check the law where you sellThe EU, US, UK and Pakistan pages differ in who they cover.

Questions people ask

What level of WCAG does a business website need?

The laws I read that name a standard point to Level AA: the US rule for state and local governments names WCAG 2.1 AA, and so does the EU's current reference standard. The W3C says content that meets WCAG 2.2 also meets 2.1, so WCAG 2.2 AA covers both. Check the law for your own markets.

Does the European Accessibility Act apply to small businesses?

Your Europe, the EU's official business site, says a service-based business with fewer than 10 employees and under €2 million in turnover is exempt. Others selling covered products and services, such as online shops, ticketing and banking, must meet the rules for anything placed on the market after 28 June 2025. Any business can claim a disproportionate burden, with evidence.

Can an accessibility plug-in make my website compliant?

No source I read says so. In January 2025 the US Federal Trade Commission ordered accessiBe to pay $1 million to settle allegations that it misrepresented its AI tool's ability to make any website WCAG compliant. The Web Almanac's authors say such overlays fall short of addressing complex accessibility challenges.

How many websites are accessible?

Very few. The WebAIM Million found detected WCAG 2 failures on 95.9% of the top 1,000,000 home pages in February 2026, an average of 56.1 errors per page. It says the rate of full WCAG 2 A and AA conformance was certainly lower than 4.1%, because automated tools cannot detect every failure.

Sources

How I checked this. I opened every source linked here and checked each figure and each quotation against the source page, most recently on 3 October 2026. Anything in a box marked “My reading” is my own interpretation, not a finding of the studies. Studies change and new ones appear, so I will update this piece and change its dates when the evidence does.

KEEP READING

See all research