AA Accessibility: What WCAG Level AA Means and How to Achieve It

If someone mentions WCAG Level AA in a meeting and you are not entirely sure what it means or why your website should meet it, you are not alone. The Web Content Accessibility Guidelines can feel impenetrable at first glance, full of technical criteria, success levels and conformance requirements that seem designed for developers rather than business owners. But Level AA is the standard that matters for most organisations, and understanding what it requires is the first step toward making your website accessible. Businesses that want to achieve and maintain AA compliance benefit from working with a team experienced in website accessibility who can translate the guidelines into practical, achievable improvements.

Level AA is not about perfection. It is about removing the barriers that prevent real people from using your website.

Understanding WCAG Conformance Levels

WCAG defines three conformance levels: A, AA and AAA. Each level builds on the one below it, with A being the minimum baseline and AAA being the most stringent. The W3C designed these levels to provide a progressive framework that organisations can work toward based on their context, resources and audience needs, with detailed requirements for each of the WCAG conformance levels.

Level AA is the standard referenced in UK legislation, including the Public Sector Bodies Accessibility Regulations 2018, and it is the standard that courts and regulators use as their benchmark when assessing whether a website meets accessibility requirements under the Equality Act 2010. It is also the standard that most private sector organisations target because it covers the broadest range of accessibility needs without requiring the specialist provisions of AAA.

What Level AA Requires

WCAG is organised around four principles: Perceivable, Operable, Understandable and strong. Level AA includes all Level A criteria plus additional requirements under each principle. Here is what the most impactful Level AA criteria mean in practical terms.

Colour contrast is one of the most visible AA requirements. Text must have a contrast ratio of at least 4.5:1 against its background for normal-sized text and 3:1 for large text. This ensures that people with low vision, colour blindness or those using screens in bright conditions can read your content. Grey text on a white background, a common design choice, frequently fails this criterion.

Text resize is another key requirement. Users must be able to increase text size to 200% without losing content or functionality. If your website layout breaks when someone uses their browser’s zoom function, that is an AA failure. Responsive design helps here, but it is not automatically sufficient. Fixed-height containers, overflow:hidden on text elements and absolute positioning can all cause content to disappear or overlap when text is enlarged.

Keyboard accessibility at Level AA means that all interactive elements must be operable using a keyboard alone, and the focus indicator, the visual outline that shows which element is currently selected, must be visible. Many websites remove the default browser focus outline for aesthetic reasons without providing an alternative, which makes keyboard navigation impossible for users who cannot use a mouse.

Removing the browser’s default focus outline without adding a custom one is the single most common AA failure we encounter during accessibility audits. It takes minutes to fix and affects every keyboard user who visits your site.

That perspective highlights an important consideration for what follows.

Common AA Failures and How to Fix Them

Certain accessibility issues appear consistently across the majority of websites that have not been specifically designed with WCAG AA in mind. Knowing what these are helps you prioritise your remediation efforts.

• Missing or inadequate alt text on images. Every non-decorative image needs descriptive alt text. Decorative images should have empty alt attributes (alt=””) so screen readers skip them entirely.
• Form inputs without associated labels. Every form field needs a programmatically associated label element. Placeholder text does not count because it disappears when the user starts typing.
• Insufficient colour contrast. Check all text/background combinations including headers, body text, links and form labels against WCAG’s 4.5:1 ratio requirement.
• Missing heading hierarchy. Pages should use heading levels (H1 through H6) in a logical order. Skipping from H2 to H4 confuses screen reader users who work through by heading level.
• Non-descriptive link text. Links that say “click here” or “read more” convey no information when read out of context. Link text should describe the destination.
• Inaccessible dropdown menus and navigation. Complex menus need proper ARIA attributes and keyboard support to be usable without a mouse.

Most of these issues are straightforward to fix once identified. The challenge is identifying them comprehensively, which is where tools and manual testing work together. Automated scanners like WebAIM’s WAVE catch some of these issues, but manual testing with a screen reader and keyboard catches the rest.

The Business Case for AA Compliance

Legal compliance is the most frequently cited reason for pursuing AA accessibility, but it is not the only one. The commercial benefits are genuine and measurable for businesses that approach accessibility as a user experience improvement rather than purely a compliance exercise.

Accessible websites tend to be better structured, faster loading and easier to use for everyone. The same clear heading structure that helps a screen reader user work through also helps a sighted user scan your content. The same keyboard navigability that a motor-impaired user depends on also benefits power users who prefer keyboard shortcuts. The same readable colour contrast that helps someone with low vision also helps anyone reading on a phone in bright sunlight.

From an SEO perspective, many accessibility improvements align directly with search engine best practices. Semantic HTML, descriptive alt text, clear heading hierarchies, readable content and fast page loads are all factors that search engines reward. Investing in accessibility often produces organic search improvements as a side benefit.

The disabled community in the UK represents a significant market. According to government statistics, around one in five people in the UK have a disability. The combined spending power of disabled people and their households is substantial. A website that excludes this audience through accessibility barriers is leaving money on the table.

Achieving AA Compliance: A Practical Approach

Full WCAG AA compliance across an entire website is achievable, but it requires a structured approach rather than a scattergun effort. Prioritise the highest-impact issues first, fix them properly and then work through the remaining items systematically.

Start with an audit. Whether you conduct this internally or with an agency, you need a thorough list of all AA failures on your site. The audit should test a representative sample of page templates, including your homepage, key landing pages, forms, navigation and any interactive components.

Prioritise fixes based on user impact. Issues that completely block access, such as forms that cannot be submitted via keyboard or content that is invisible to screen readers, should be addressed before issues that cause inconvenience but do not prevent access. This impact-based prioritisation ensures that the most significant barriers are removed first.

Build accessibility into your processes going forward. Every new page, feature and content update should be checked against AA criteria before publication. This prevents the common pattern of achieving compliance, then gradually introducing new barriers through ongoing content and development work. As Equalize Digital recommends, accessibility is most effective when treated as a continuous practice rather than a one-time project.

Maintaining Compliance Over Time

Achieving AA compliance is a milestone, not a finish line. Websites change constantly through new content, updated features, redesigned components and third-party integrations. Each change has the potential to introduce new accessibility barriers, which means ongoing monitoring is important.

Automated monitoring tools can catch regressions in measurable criteria like colour contrast, missing alt text and form label associations. Run these checks regularly, ideally as part of your deployment process so that new barriers are caught before they reach your users. Manual testing should happen quarterly or whenever significant changes are made to your site structure or functionality.

Your accessibility statement, which is legally required for public sector organisations and best practice for everyone else, should be reviewed and updated whenever significant changes occur. The statement should accurately describe your current conformance level, any known limitations and how users can report accessibility issues they encounter.

WCAG itself evolves. Version 2.2, published in 2023, added new success criteria including focus appearance requirements and accessible authentication. Future versions will continue raising the bar. Staying informed about these changes and planning for them keeps your website ahead of compliance requirements rather than perpetually catching up. Treat accessibility as a component of your ongoing website maintenance programme, and it becomes a manageable, continuous improvement rather than an overwhelming remediation project.