WCAG AA vs AAA: What WordPress Sites Actually Need
Most WordPress site owners think about WCAG compliance one of two ways:
“We added alt text to our images, so we’re probably fine.”
Or: “AAA sounds extreme. We’ll just aim for AA and call it done.”
Both of those are partly right — and partly how you end up with accessibility problems you didn’t know you had.
WCAG levels aren’t complicated once you strip away the acronym soup. This post breaks down what AA and AAA actually mean, what the difference is in practice, and — most importantly — what it looks like on a real WordPress or WooCommerce site.
First, a Quick Explainer: What Are WCAG Levels?
WCAG stands for Web Content Accessibility Guidelines. They’re published by the W3C and define how websites should be built so people with disabilities — visual, auditory, motor, cognitive — can actually use them.
The guidelines are split into three levels:
- Level A — the bare minimum. 30 criteria. Mostly about not actively blocking users (no keyboard traps, alt text on images, captions on video).
- Level AA — the legal standard. 24 additional criteria on top of A, so 54 total. This is what ADA compliance in the US, the European Accessibility Act, and Section 508 all point to.
- Level AAA — the highest level. 32 more criteria on top of AA, so 86 total. More specific, more demanding, and not required for full legal compliance.
The key thing: each level includes everything in the level below it. You can’t claim AA compliance while skipping Level A requirements. It’s additive.
WCAG 2.2 is the current standard (released October 2023). It added 9 new criteria — 6 at AA level, 3 at AAA. If you’re still targeting WCAG 2.1, you’re not current.
Myth #1: “If We Have Alt Text and Good Contrast, We’re AA Compliant”
Reality: AA has 54 criteria. Most sites are hitting maybe 30 of them.
Alt text and color contrast are the most visible AA requirements, so they get the most attention. But AA compliance covers a lot more than that.
Here’s what often gets missed on WordPress sites:
Consistent navigation (2.4.3 / 3.2.3): Every page on your site needs navigation in the same location and same order. Sounds simple — but theme builders, page builders, and custom templates often break this in subtle ways. A landing page with a stripped header, or a WooCommerce checkout page with a different nav structure, can fail this criterion.
Error identification and suggestions (3.3.1 / 3.3.3): When a form has an error, you need to tell the user what went wrong and how to fix it. Not just a red border around the field. An actual text explanation. Most default WooCommerce form validation fails this without a dedicated accessibility plugin or custom work.
Focus visible (2.4.7 / 2.4.11 in WCAG 2.2): Keyboard users need to see where they are on the page. Many WordPress themes remove the default browser focus ring because “it looks ugly.” That’s an AA failure. WCAG 2.2 tightened this with a minimum 3:1 contrast ratio for focus indicators.
Target size (2.5.8 in WCAG 2.2): Clickable elements need to be at least 24×24 pixels. Small icon buttons, tiny “remove” links in cart pages, close buttons on popups — these frequently fail on WooCommerce stores.
Reflow (1.4.10): Content must work at 320px viewport width without horizontal scrolling. This isn’t just about being “mobile-friendly” — it’s about users who zoom to 400% on their browser. Tables, data grids, and product comparison pages often break this.
Getting AA right means a thorough audit, not a checkbox pass.
Myth #2: “AAA Is Overkill — Nobody Actually Needs That”
Reality: You probably don’t need full AAA. But selective AAA criteria belong in every WooCommerce checkout.
W3C itself says full AAA compliance isn’t recommended as a blanket policy for entire websites — because some criteria genuinely can’t be applied universally. That’s not a bug in the system. It’s an acknowledgment that some requirements only make sense for specific content types.
But “we don’t need AAA” gets used as a reason to ignore AAA criteria entirely. That’s where it goes wrong.
Here are three AAA requirements that make a real difference on WooCommerce sites:
Enhanced contrast (1.4.6) — 7:1 ratio instead of 4.5:1: AA requires a 4.5:1 contrast ratio for normal text. AAA requires 7:1. The difference matters for users with low vision who aren’t using screen readers or assistive tech. On checkout pages, product descriptions, and pricing — where the stakes of misreading something are high — the 7:1 ratio is worth applying even if it’s not legally required.
No timing (2.2.3): AA allows session timeouts as long as you warn users first. AAA says: no essential timing at all (with some exceptions). For medical, legal, or high-value WooCommerce stores, a session timeout during checkout can cause real harm to users who type slowly or need to take breaks. Worth solving.
Context-sensitive help (3.3.5): Providing help text that’s specific to what the user is doing right now. Think “What is a CVV?” next to a card field, or clear guidance on address formatting next to international shipping fields. This is an AAA criterion — and also just good UX.
The practical approach: target AA across the full site, and apply specific AAA criteria to your most critical flows — checkout, forms, account access, and any health or legal content.
Myth #3: “An Accessibility Plugin Will Handle It”
Reality: Overlay plugins catch maybe 30-40% of issues. The rest needs real development work.
This one is probably the most common misconception we see. There’s a whole category of WordPress plugins — overlays, widgets, “one-click accessibility” tools — that claim to make your site compliant. They sit in a floating widget in the corner, let users adjust text size and contrast, and give you a badge to put in your footer.
They don’t make your site compliant.
Automated tools — even the good ones like axe DevTools or WAVE — catch around 30-40% of WCAG issues. The rest require manual testing: keyboard navigation, screen reader testing with NVDA, JAWS, or VoiceOver, actual human review of forms and interactive components.
Overlay plugins can’t fix:
- A WooCommerce checkout that breaks when navigated by keyboard
- A carousel that auto-plays without pause controls
- A product filter that doesn’t announce state changes to screen readers
- Custom JavaScript components that aren’t built with ARIA roles
They also introduce new problems. Some overlay plugins interfere with assistive technologies, creating a worse experience for the users they’re supposed to help.
Real WCAG compliance is built into the site. It’s not applied on top of it.
What WCAG AA Actually Looks Like on a WordPress Site
Here’s a practical breakdown by area:
Theme and Design
- Color contrast 4.5:1 for normal text, 3:1 for large text and UI components
- No information conveyed by color alone
- Visible focus indicators on all interactive elements (minimum 3:1 contrast in WCAG 2.2)
- Text resizable to 200% without loss of content or functionality
- Content reflows at 320px width
Navigation
- Consistent navigation location and order across all pages
- Skip navigation link at top of page (lets keyboard users jump to main content)
- Page titles that describe the current page
- Logical heading hierarchy (H1 → H2 → H3 — never skipped)
- Multiple ways to find a page: search, sitemap, or related links
Forms (especially WooCommerce)
- All fields have visible, descriptive labels — not just placeholder text
- Error messages identify the field and explain how to fix it
- Required fields clearly indicated
- No time limits on form completion (or extendable with warning)
- Minimum 24×24px touch targets for all buttons and controls (WCAG 2.2)
- No CAPTCHA that relies solely on visual recognition (WCAG 2.2)
Images and Media
- Descriptive alt text on all informative images
- Empty alt on decorative images (alt=””)
- Captions and transcripts for video and audio content
- No content that flashes more than 3 times per second
Dynamic Content and JavaScript
- ARIA roles and live regions for dynamically updated content
- Keyboard accessible modals, dropdowns, and custom components
- Carousels and sliders with pause controls
- State changes announced to screen readers
WCAG AA Checklist for WordPress Sites
Use this as a starting point for a self-assessment. It’s not a substitute for a full audit, but it’ll tell you quickly where the biggest gaps are.
Perceivable
- All images have descriptive alt text (or empty alt for decorative images)
- Videos have captions
- Color contrast is at least 4.5:1 for normal text, 3:1 for large text
- Information isn’t conveyed by color alone
- Content reflows at 320px without horizontal scroll
Operable
- All functionality works with keyboard only
- No keyboard traps
- Skip navigation link is present and working
- Focus indicators are visible on all interactive elements
- No auto-playing media without controls
- All clickable elements are at least 24×24px (WCAG 2.2)
- Drag-and-drop functionality has an alternative (WCAG 2.2)
Understandable
- Page language is set in HTML
- Navigation is consistent across all pages
- Form fields have descriptive labels (not just placeholders)
- Error messages identify the field and suggest a fix
- No CAPTCHAs that require visual interpretation (WCAG 2.2)
Robust
- Pages validate as clean HTML
- Custom components use correct ARIA roles and attributes
- Status messages are announced to screen readers without requiring focus
So, AA or AAA — Which Do You Need?
For most WordPress and WooCommerce sites: AA is the legal target, selective AAA is the smart play.
Full AAA compliance across your entire site is rarely practical and not legally required. But dismissing AAA entirely means leaving real users behind on the parts of your site where it matters most.
The places to go beyond AA:
- Checkout and payment forms
- Account creation and login
- Any health, legal, or medical content
- Email signup and contact forms
The places where AA is enough:
- Blog posts and editorial content
- Marketing pages
- Product catalog pages
And wherever you’re starting from — the most important step is an honest audit. Not a plugin. Not a badge. A real look at how your site behaves for users who navigate by keyboard, use a screen reader, or have low vision.
That’s the work. And it’s worth doing.
Ready to find out where your WordPress site actually stands on WCAG compliance? Book a free intro call and we’ll walk you through it.
