WCAG 2.1 AA

WCAG 2.1 level AA, Web Content Accessibility Guidelines 2.1 AA, WCAG AA, WCAG 2.1 conformance level AA, Web Content Accessibility Guidelines 2.1 AA
WCAG 2.1 AA is an internationally recognized accessibility standard that makes websites usable for people with disabilities. Required for government websites and increasingly for commercial sites.

What is WCAG 2.1 AA?

WCAG 2.1 AA is the most widely used accessibility standard for Web sites, developed by the World Wide Web Consortium (W3C). The abbreviation stands for Web Content Accessibility Guidelines version 2.1, level AA. The standard contains 50 success criteria that make websites usable for people with visual, hearing, motor or cognitive impairments. For Dutch government sites, WCAG 2.1 AA has been required by law since 2020. Commercial companies are also increasingly affected by this standard, for example through tenders or the European European Accessibility Act that comes into force in 2025.

How WCAG 2.1 AA works in practice

The standard is built around four basic principles: perceivable, operable, understandable and robust. Each principle contains guidelines, and each guideline contains testable success criteria. Level A is the basic level, AA is the common level for professional Web sites, and AAA is the highest level that is especially relevant for specific audiences. A Web site meets WCAG 2.1 AA if all 30 A criteria as well as all 20 AA criteria are met. This means: sufficient color contrast, keyboard controls for all functions, subtitles for video, logical headings and error messages that clearly explain what is wrong. In practice, you test this with a combination of automated tools and manual verification.

Why WCAG 2.1 came about and why it matters now

The first WCAG version appeared in 1999. Version 2.0 followed in 2008 and became the international standard. WCAG 2.1 came in 2018 and added 17 new criteria, mainly focused on mobile use, low vision and cognitive impairment. The standard became relevant as websites increasingly offer essential services. Those who cannot log in to their health insurance company or cannot order from an ecommerce store encounter concrete obstacles. In the United States, the Tijdelijk besluit digitale toegankelijkheid overheid has required all government agencies to AA level since 2020. Commercial organizations are increasingly following suit, driven by procurement requirements, reputation risk and expected European legislation.

What WCAG 2.1 AA brings to SMBs

An accessible website reaches a larger target audience. In the United States, approximately 20% of the population has some form of disability, whether temporary or permanent. In addition, a logical structure and clear error messages help all visitors, including those without disabilities. From a technical standpoint,WCAG compliance often yields SEO benefits as well: a clear heading structure, descriptive link text, and fast keyboard navigation are factors that Google values. In government tenders or collaborations with public authorities, AA level is increasingly becoming a mandatory requirement. Would you like to know how accessible your current website is and what adjustments are needed? A professional website audit identifies specific areas for improvement, including prioritization based on impact and effort.

Applications of WCAG 2.1 AA

WCAG 2.1 AA is not a theoretical framework but a practical checklist that you apply in design, development and content strategy. Below are four concrete situations in which SMEs deploy the standard, plus a decision criterion when AA level is or is not the right ambition.

Making ecommerce stores and forms accessible

A WCAG 2.1 AA compliant ecommerce store provides keyboard navigation throughout the ordering process, from product page to payment. Error messages at checkout are specifically worded, for example, "Zip code missing" instead of "Please complete all fields." Color contrast between text and background is at least 4.5:1 so that people with low vision can read prices and buttons. Alt-texts for product photos describe what is shown, so that screen readers can read the image. In practice, we see that ecommerce stores that apply these criteria also have fewer abandoned shopping carts. Clarity helps everyone. A good example is an ecommerce store with 800 products that saw a 12% increase in conversion after an accessibility audit, especially on mobile.

Government procurement and grant applications.

Anyone who wants to do business as an SME with municipalities, provinces or central government often has to demonstrate that the website or application offered is WCAG 2.1 AA compliant. This applies to software vendors, but also to agencies that develop websites for government agencies. The procurer usually asks for an accessibility statement or WCAG audit by an approved party. Without that declaration, your bid is out of the question, regardless of price or quality. Grant applications for digital innovation or European funds also increasingly include accessibility as a condition. The investment in a compliant website is then not a nice-to-have but an access ticket.

Client portals and employee intranet

WCAG 2.1 AA doesn't just apply to public Web sites. Customer portals where relationships view contracts, download invoices or submit support tickets also fall under the standard if you work with government customers. The same goes for internal systems if you employ employees with disabilities. A company with 40 employees and its own HR portal must ensure that a colleague with dyslexia can fill out leave requests, or that a colleague with RSI can operate the system entirely by keyboard. This requires clear labels at input fields, logical tab order and error messages appearing at the correct field. In practice, this also results in fewer IT support questions because the system becomes clearer for everyone.

When WCAG 2.1 AA is the right choice and when it is not

WCAG 2.1 AA is the right choice if your Web site offers essential services, if you work with governments or large clients, or if you want to avoid reputational risk. It is also wise if you want to reach a broad audience and not exclude based on restrictions. AA is not always necessary for a simple one-pager or an internal prototype. In those cases, you can suffice with the A criteria, or with a selection of AA criteria that have the most impact. Going for AAA level? Then you are working with a very specific target audience, for example, a website for the visually impaired. For most SMEs, AA is the realistic and responsible level. Want to know which level suits your situation? An SEO and accessibility scan provides insight into the current state and the most impactful improvement steps.

Want to apply this to your business? Monkey Vision helps SME entrepreneurs with web design, SEO and smart digital solutions. Schedule a no-obligation meeting and find out what's possible for you.

Schedule an introduction

Frequently Asked Questions

No, WCAG 2.1 AA is a specific standard within the broader concept of accessibility. Accessibility is about all aspects that make a product or service usable by people with disabilities. WCAG 2.1 AA is a measurable standard with 50 criteria that you can test. There are also other accessibility standards, such as the European EN 301 549 or the U.S. Section 508. WCAG 2.1 AA is the most widely used and is set as a minimum requirement by most governments and large companies. Accessibility also includes things that are not in WCAG, such as understandable language or a logical information structure. So WCAG is a part of accessibility, not the whole.

AA is the right level for most companies. It is required by law for governments, widely accepted in tenders, and achievable without excessive cost. AAA adds 28 additional criteria that are especially relevant to very specific audiences, such as Web sites for the blind or people with severe cognitive disabilities. Examples of AAA requirements: sign language interpreter for video, extended subtitles and even higher color contrast of 7:1. For an average ecommerce store, corporate site or customer portal, AAA delivers little extra and costs much more. Choose AAA only if your target audience really needs it. In all other cases, AA is the standard you should aim for. Want to hesitate? First test whether you meet A at all; that's the basics.

Start with an automated scan via tools like Lighthouse, Axe or WAVE. Those quickly find the most common errors: missing alt text, too low color contrast and faulty header structure. Fix those first. Then follow manual verification: test whether you can control the entire site using only the keyboard, whether forms give clear error messages, and whether videos have subtitles. Document your findings in an accessibility statement. Preferably involve a specialist for the final check because many criteria cannot be tested automatically. Plan accessibility into every new project from the beginning, to avoid expensive rounds of retrofitting. Want to know where your site stands now? Request a one-time audit.

The best approach depends on your situation. Do you have an existing Web site and want to know what needs to be done to meet AA? Then schedule a free 30-minute accessibility scan at Monkey Vision. We'll walk through your site live and immediately give you three concrete areas for improvement that you can pick up this week. You'll also get an honest estimate of the total effort and a roadmap in order of impact. No sales pitch, just practical advice. Are you building a new site? Then we'll integrate WCAG 2.1 AA into the web design and development from the start, so you launch compliant right away. Contact us for a no-obligation consultation.

About the author

Monkey Vision

Monkey Vision is a full-service digital agency at Nijmegen, specializing in web design, SEO, and AI automation for small and medium-sized businesses. The knowledge base has been compiled by our team of online strategists and is continuously updated based on current insights.

Publication date: 26-04-2026
Last update: 26-04-2026