WCAG Compliance for B2B Websites: The Accessibility Checklist

WebAIM's 2026 Million report tested the home pages of the top one million websites and found detectable WCAG failures on 95.9% of them, with an average of 56.1 errors per page. Those are the errors software can find. The ones that need a person to catch them sit on top. For a B2B company, WCAG compliance decides whether a buyer who uses a screen reader, a keyboard or a magnifier can use your site at all.

That group is large. The WHO estimates 1.3 billion people experience significant disability, about 16% of the world's population. The buyers, procurement reviewers and users inside your target accounts include them. Accessibility has also moved from good practice to law in several places Indian B2B companies sell to, including parts of Indian regulation.

This guide will explain what WCAG compliance means, which version a B2B website should target, what Indian and international rules ask for and a 12-point checklist mapped to WCAG 2.2 success criteria.

Key Takeaways

WCAG compliance means meeting the success criteria of the Web Content Accessibility Guidelines at a stated level, usually AA. Build to WCAG 2.2 AA.

Six error types cause most detected failures: low contrast, missing alt text, missing form labels, empty links, empty buttons and missing page language.

In India, the Rights of Persons with Disabilities Act covers private service providers, and SEBI now requires digital accessibility from every regulated entity.

Selling to Europe or US public bodies brings the European Accessibility Act and the ADA web rule into play.

Accessibility built in from the start costs far less than a retrofit. Automated scans find part of the problem, so budget for manual testing.

What is WCAG compliance?

WCAG compliance means a website meets the success criteria of the Web Content Accessibility Guidelines, published by the W3C, at a chosen conformance level. There are three levels. Level A covers the basics, Level AA is the level laws and contracts usually require, and Level AAA is the strictest. The criteria sit under four principles: content must be perceivable, operable and understandable, and it must work with current and future assistive technology.

The guidelines have three current versions. People still search for the WCAG 2.0 Web Content Accessibility Guidelines, which set the original structure. WCAG 2.1 added criteria for mobile, low vision and cognitive needs. The current WCAG 2.2 became a W3C Recommendation in October 2023. It added nine new success criteria and retired one, 4.1.1 Parsing. Each version builds on the last, so a site that meets 2.2 AA also meets 2.1 AA.

Which WCAG version should a B2B website target?

Build to WCAG 2.2 Level AA. Many rules still cite WCAG 2.1 AA compliance, and a site built to 2.2 satisfies them. Meeting the newer version also covers criteria buyers notice directly, such as focus indicators that stay visible and click targets big enough to hit on a phone.

India's own government standard shows the pattern. The GIGW 3.0 government guidelines state that they ensure conformity with Level AA of WCAG 2.1. If you sell to government departments or public sector companies, expect that standard in the tender. If you sell to private enterprises, expect a questionnaire asking which WCAG level your product meets.

Is website accessibility mandatory in India?

For many companies, yes, and the scope is widening. Website accessibility in India rests on the RPwD Act, 2016, the Rights of Persons with Disabilities Act. Section 40 asks the Central Government to set accessibility standards covering information and communication technology. Section 46 requires service providers, government or private, to provide services in line with those rules within two years of their notification.

The rules themselves have been tested in court. In November 2024, the Supreme Court ruled in the Rajive Raturi judgment. It found that the accessibility rules under the Act leaned on self-regulatory guidelines, and directed the Union Government to prescribe a baseline of mandatory, non-negotiable rules. The judgment names accessible digital interfaces among the principles the new rules should cover.

Regulators are moving too. A July 2025 SEBI circular, dated 31 July, made digital accessibility mandatory for every SEBI-regulated entity. Their platforms must follow WCAG 2.1 or the latest version, the GIGW guidelines, IS 17802 and the RPwD Act. SEBI has since issued clarifications and revised timelines. For a fintech selling to brokers, AMCs or exchanges, WCAG compliance is now part of your customer's compliance, which our fintech website work plans for from the start.

Note: this section summarises public sources as of September 2026 and is not legal advice. Rules and timelines change, so confirm your obligations with qualified counsel.

Does WCAG compliance matter if we sell abroad?

Yes, depending on who you sell to. The European Accessibility Act applies to covered services provided to consumers after 28 June 2025, including e-commerce and banking services. Microenterprises providing services are exempt. A B2B SaaS product sold only to businesses may fall outside the Act, and a consumer-facing product in the EU usually falls inside it.

In the United States, the DOJ web rule requires state and local governments to meet WCAG 2.1 Level AA. Compliance dates are now April 2027 or April 2028, depending on size. It also covers content that vendors provide for those bodies. If US public sector buyers are on your roadmap, WCAG 2.1 AA compliance becomes a condition of the sale.

The WCAG compliance checklist for B2B websites

These twelve WCAG compliance checks cover the failures that show up most often and the WCAG 2.2 additions buyers notice. Each maps to a success criterion, so your developer can look up the exact requirement.

#	Check	WCAG 2.2 criterion	How to test
1	Body text contrast of at least 4.5:1, large text 3:1	1.4.3 Contrast (Minimum), AA	Contrast checker on every text colour pair
2	Buttons, inputs and icons contrast at 3:1 against the background	1.4.11 Non-text Contrast, AA	Check text, borders and icons
3	Every meaningful image has alt text, decorative ones are marked as such	1.1.1 Non-text Content, A	Screen reader pass, alt attribute review
4	Every form field has a visible label	3.3.2 Labels or Instructions, A	Click each label, it should focus the field
5	Errors say what went wrong and how to fix it	3.3.1 Error Identification, A	Submit each form with mistakes
6	Everything works with a keyboard alone	2.1.1 Keyboard, A	Unplug the mouse and complete key tasks
7	Focus is always visible and never hidden by sticky bars	2.4.7 Focus Visible and 2.4.11 Focus Not Obscured, AA	Tab through each page
8	Click targets are at least 24 by 24 CSS pixels	2.5.8 Target Size (Minimum), AA	Measure small icons and inline links
9	Buttons and links have accessible names	4.1.2 Name, Role, Value, A	Screen reader reads every control
10	Headings follow a logical structure	1.3.1 Info and Relationships, A	Heading outline makes sense on its own
11	Login does not depend on memory puzzles	3.3.8 Accessible Authentication (Minimum), AA	Password managers and paste work
12	Help and contact links sit in the same place on every page	3.2.6 Consistent Help, A	Compare layouts across templates

Checks one to five catch the failures WebAIM finds most often. Low-contrast text appeared on 83.9% of home pages, missing alt text on 53.1% and missing form labels on 51%. Our free contrast checker and touch target checker handle checks one and eight in a browser tab.

How does a web accessibility audit work?

A web accessibility audit combines automated scanning with manual testing, because software alone misses a large part of the problem. It is the only reliable way to verify WCAG compliance. A scanner can flag missing alt text. It cannot tell whether the alt text describes the image usefully, or whether a keyboard user gets trapped inside a pop-up. A proper website accessibility audit runs four passes.

Automated scan of key templates to find the mechanical failures quickly.

Keyboard pass through every key task: navigation, forms, sign-up and checkout.

Screen reader pass on the same tasks, listening for missing names, wrong reading order and silent errors.

Report and retest, with each issue mapped to a success criterion, a severity and a fix, then retested after the fixes ship.

Accessibility is also one phase of our wider audit, covered in our guide to the SaaS UX audit. Clean structure helps machines too, since the headings, labels and alt text screen readers rely on are the same signals answer engines parse, as our answer engine optimization guide explains.

When should WCAG compliance be built in?

At the design stage, because a retrofit costs more. Colour palettes, component states and page templates decide most accessibility outcomes before a developer writes a line. Fixing contrast after launch can mean redesigning the brand colours. Fixing it in the design system means choosing them once. Accessibility is one of the lines worth checking in any quote, as our guide to website design cost in India explains.

Our development work builds to WCAG 2.2 AA, with visible focus states, full keyboard navigation, labelled forms and reduced-motion support. Our own accessibility statement lists what we have done and the known limitations, such as placeholder images still waiting for real project work. We think every site should publish one.

Frequently Asked Questions

What is WCAG compliance?

WCAG compliance means a website meets the success criteria of the Web Content Accessibility Guidelines at a stated level, usually AA. The criteria cover contrast, text alternatives, keyboard access, forms, structure and more. A compliant site can be used by people who rely on screen readers, keyboards, magnifiers or captions.

Which WCAG level do B2B websites need?

Level AA is the usual target in laws, tenders and enterprise questionnaires. Build to WCAG 2.2 AA, the current version, which also satisfies requirements that cite WCAG 2.1 AA. Level AAA is rarely required for a whole site, though some criteria are worth meeting where the content allows.

Is website accessibility a legal requirement in India?

The Rights of Persons with Disabilities Act, 2016 requires government and private service providers to follow the accessibility rules made under it. The Supreme Court directed the government in 2024 to make those rules mandatory, and SEBI requires all regulated entities to meet digital accessibility standards. Confirm your position with qualified counsel.

How often should we run a website accessibility audit?

Run a full audit before launch or after a redesign, then check new templates and features as they ship. A quarterly automated scan catches regressions, such as a new banner with low contrast. Retest after every significant change to navigation, forms or login, since those areas break most easily.

Can an accessibility overlay make a site compliant?

Overlays add a toolbar on top of the site and leave the underlying code unchanged. Missing labels, keyboard traps and poor structure stay in place, so the site still fails for many users. Fixing the code and the design system is the reliable route to compliance.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds nine success criteria to 2.1 and removes 4.1.1 Parsing. The additions include visible focus that is never hidden, minimum target sizes, accessible authentication without memory tests, consistent help and avoiding redundant data entry. A site that meets 2.2 AA also meets 2.1 AA.

Make accessibility part of the build

WCAG compliance is easiest when it is a design decision made once, then held in the components every page reuses. Target WCAG 2.2 AA, test with a scanner, a keyboard and a screen reader, and publish an honest accessibility statement. Buyers, regulators and the one in six people with a disability will all notice.