Table of contents
Since June 2025, the European Accessibility Act (EAA) has been in force in the EU. In practice: all e-commerce sites, banks, insurance, transport and e-books MUST meet WCAG 2.2 level AA. Penalty: up to 100,000 zł or 2% of annual turnover. I'll show you how to handle it in WordPress without rebuilding your site from scratch.
In short
- WCAG 2.2 is the W3C accessibility standard — it defines how people with disabilities should be able to use your website.
- Level AA is a legal requirement — it's not a “nice-to-have”, it's the law.
- In practice: contrast of at least 4.5:1, focus indicator, keyboard navigation, alt texts, ARIA labels.
- Implementation time in WordPress: 1–3 weeks for a site with up to 200 pages.
What exactly changed in WCAG 2.2
WCAG 2.0 (2008) → WCAG 2.1 (2018) → WCAG 2.2 (2023) — the latest version.
WCAG 2.2 adds 9 new criteria (vs. 2.1):
- Focus Not Obscured (Minimum) — focus must be visible, not hidden
- Focus Not Obscured (Enhanced) — fully visible, not partially
- Focus Appearance — minimum size and contrast of the indicator
- Dragging Movements — drag&drop must have an alternative (click)
- Target Size — interactive elements min. 24×24 px (mobile 44×44)
- Consistent Help — a help link in the same place on every page
- Redundant Entry — don't make users enter the same data again
- Accessible Authentication (Minimum) — login without “cognitive tests” (puzzle CAPTCHAs are out)
- Accessible Authentication (Enhanced) — without even remembering a password (one-time codes, passkeys)
Three levels of compliance
- A — minimum (most websites already have it)
- AA — legal requirement (EAA, Polish law for the public sector)
- AAA — the highest level, not required for businesses
Goal: AA level.
Key requirements — 12 items to complete
1. Text contrast of at least 4.5:1
Text on a background must have a contrast ratio of 4.5:1 for sizes < 18 pt, and 3:1 for larger text.
Test: WebAIM Contrast Checker — enter the hex codes of the text and background.
Most common mistakes:
– Gray text #999 on a white background = 2.8:1 contrast (FAIL)
– White on orange #FFA500 = 1.9:1 contrast (FAIL)
– Different contrast in light vs. dark mode
Fix: a darker gray (#333+ on white), a different accent color, adding an outline/shadow.
2. Every image has an alt attribute
<!-- WRONG -->
<img src="logo.png">
<!-- DOBRZE -->
<img src="logo.png" alt="Websky Studio - logo">
In WordPress: add alt text when uploading media. The Alt Text Generator plugin can auto-generate AI alt text for existing images.
Exception: decorative images can have alt="" (empty) — screen readers will ignore them.
3. Visible focus indicator
Every interactive element (link, button, input) must visibly show focus during keyboard navigation (Tab).
The browser's default focus is often good enough. If your theme removes it with CSS (outline: none), that's wrong — restore it:
:focus-visible {
outline: 3px solid #0066ff;
outline-offset: 2px;
}
4. The entire site can be operated with a keyboard
Test: unplug your mouse. Try to:
– Tab through all elements
– Fill out a form
– Buy a product
– Open and close modals
Everything has to work. A dropdown menu that opens only on hover = FAIL — add opening on focus/Enter.
5. Skip link at the top of the page
The first element on the page is a “Skip to main content” link (visible on focus):
<a href="#main" class="skip-link">Skip to main content</a>
Lets screen reader users skip the menu.
6. Logical heading hierarchy
H1 once per page → H2 for sections → H3 for subsections. Don't skip levels (H1 → H4 = wrong).
The Headers Order plugin (free) will check your headings and warn you about errors.
7. Forms with <label>
Every input field has a label (visible or aria-label):
<label for="email">Adres e-mail</label>
<input type="email" id="email" name="email" required>
Without it, a screen reader doesn't know what the field is for.
8. Accessible error messages
After submitting a form with an error:
– Error message next to the field (not just at the top of the page)
– Color + icon + text (not color alone — color-blind users won't see it)
– aria-invalid="true" on the field with the error
– Focus moved to the first error
9. Video with captions (closed captions)
Every video with speech must have captions. YouTube offers auto-captions, but check them for accuracy (auto-captions often mangle Polish diacritics).
For self-hosted video — a .vtt file with captions:
<video controls>
<source src="film.mp4" type="video/mp4">
<track kind="captions" src="napisy.vtt" srclang="pl" label="Polski">
</video>
10. Semantic HTML structure
Use the right tags:
– <nav> for navigation
– <main> for main content
– <header>, <footer>, <article>, <section>
– <button> for buttons, <a> for links (NOT the other way around)
WordPress core already does this well. Custom themes often break it — check yours.
11. Target size min. 24×24 px
Every clickable element must be at least 24×24 px (44×44 on mobile). 16×16 social media icons in the footer = FAIL.
Fix: add padding around the icon without enlarging the graphic itself.
12. No flickering
No animations flashing more than 3× per second (epilepsy risk). Check all of them:
– Loading spinners
– Hover effects
– Animated GIFs
– Videos with strobe effects
WordPress plugins that help
WP Accessibility (free)
Fixes basic issues:
– Skip link
– Checks alt text
– Brightens focus indicator contrast
– Hides role redundancy
Accessibility Checker (freemium)
Scans every page and shows WCAG errors. Free for up to 25 pages, Pro from 49 USD/year.
One Click Accessibility (free)
Adds a “widget” with options: larger text, readable fonts, high contrast. Note: this doesn't replace real accessibility — it's just a “vanity feature” for the auditor.
WCAG 2.2 (original)
The official WordPress plugin: lightweight and a good place to start.
Accessibility audit — how to do one
Automated tools
- axe DevTools (Chrome extension, free) — the most useful automated tool
- WAVE (WebAIM, free online) — a visual error report
- Lighthouse (built into Chrome) — Accessibility audit
The limit of automated tools: they detect 30% of errors. The rest has to be checked by a human.
Manual audit
- Navigate the site with the keyboard (Tab, Enter, Esc, arrow keys)
- Test it with a screen reader (NVDA for Windows — free)
- Check the contrast of all text
- Check mobile — target size, touch zoom
- Turn off CSS: does the page still make sense?
Professional audit
A full WCAG 2.2 AA audit by an external company: 5 000–15 000 zł for a site with up to 100 pages. Includes a certificate of compliance to present in case of an inspection.
3-week implementation plan
Week 1: Analysis
– Automated audit (axe, WAVE)
– Listing all errors
– Prioritization: critical → important → minor
Week 2: Critical fixes
– Text contrast
– Alt text (AI auto-generated + key images manually)
– Focus indicators
– Skip link
– Keyboard
Week 3: Minor fixes + documentation
– ARIA labels
– Logical heading order
– Forms with labels
– Screen reader test
– Accessibility statement (published on the site)
What's next
This week:
- Install axe DevTools in Chrome
- Open your website → DevTools → axe → Run scan
- Write down the top 10 mistakes
- Schedule the repair
We do WCAG 2.2 audits + error fixing — in 2 weeks, we make your site meet EAA requirements. Package price from 2 500 zł. Get in touch.
Your feedback
Was this article helpful?
One click — it helps me choose future topics.

