AUDIT WCAG 2.2 AA FOR PUBLIC ENTITIES
Report, repair priorities, recommendations, and consultations
—a complete package for tendering and implementation.
For whom? — complete set for tender and implementation.
Public sector entities
(offices, organizational units, municipal companies, cultural institutions, universities, hospitals, etc.)
Subcontractors/beneficiaries
projects financed from public funds (e.g. RPO, FERC – digital components)
Organizations and companies that want to achieve AA compliance and mitigate legal/reputational risks
Legal Notice:
In Poland, accessibility is guaranteed in accordance with WCAG 2.1 level AA (based on EN 301 549).
We conduct our audit in accordance with this standard, expanding the scope to include the new WCAG 2.2 criteria, to make the project future-proof.
Legal notice:
78 WCAG 2.2 Success Criteria (A/AA)
with full mapping to WCAG 2.1 AA criteria (statutory requirement)
Keyboard navigation
focus order, focus visibility and unobstructing, loops, skip links
Contrasts and typography
4.5:1 for body text, 3:1 for large text, interaction states, space, line‑height
Screen reader tests
NVDA (Windows, Firefox), JAWS (Windows, Chrome/Edge), VoiceOver (macOS/iOS, Safari)
Forms and Validation
labels, required fields, errors, help text, autocomplete, authentication
UI patterns
navigation components, tabs, accordions, dialogues, tooltips, carousels
Content and language
comprehensibility, heading hierarchy, page and fragment language, links “understandable out of context”
Multimedia
subtitles, transcripts, audio description (if applicable), players
WCAG 2.2 – selected new areas (A/AA)
- 2.4.11 Focus not obscured (Minimum)
- 2.5.7 Dragging movements
- 2.5.8 Target size (Minimum)T
- 3.2.6 Consistent help
- 3.3.7 Redundant entry
- 3.3.8 Accessible authentication (Minimum)
Methodology
Expert heuristics
(overview of templates and critical user paths)
Tool tests
(axe‑core/Lighthouse/WAVE) – only as support, not as the sole source
Manual scenario testing
tasks using the keyboard, readers, mobile devices
Sampling
sampling of representative subpages + pages with the highest traffic/risk
Mapping
and WCAG 2.1/2.2 (A/AA) matrix
Peer review
cross-audit by two specialists for critical findings
Artifacts
What we deliver
PDF report
with Executive Summary (compliance status, risks, strategic recommendations) +detailed error cards (ID, location, criterion, impact, screen/evidence, solution, priority, est. effort)
Repair Backlog
(CSV/Jira): prioritization by impact × effort; labels (FE/BE/Content/Design)
Compatibility matrix
(checklists A/AA) + risk heatmap
UX/content recommendations
(link patterns, titles, alternatives, microcopy errors)
Evidence package
(optional)
screenshots, short .webm recordings, test scripts
Presentation of results
60–90 min workshop (online or onsite):
performance review, priority decisions, recovery plan, Q&A
Handover to IT/Content Team:
discussion of PR examples, components and quick wins
Entries and requirements
Accesses:
URLs (prod/stage), logins (if content is protected), CMS/stack type
Contact to owners:
IT, content, UX, BIP (if applicable)
Scope of service:
list of key templates and critical paths:
Schedule
Receipt and acceptance
Acceptance of report and backlog;
confirmation of the scope of repair responsibility (we / your team)
Possibility of continuation:
implementation + re-audit + declaration + SLA