EN 301 549 · WCAG 2.2 AA · European Accessibility Act
Automated scanners find 30% of your accessibility issues. I find the rest and hand your engineers tickets, not a PDF.
A gap audit that translates legal accessibility mandates into a prioritized, engineering-ready backlog — scoped, estimated, and ready to assign in your sprint tomorrow. Pricing on request.
Why this, why now
If you sell digital products or services in the EU, EN 301 549 compliance is already enforceable. Most teams don't have a compliance gap — they have a translation gap: nobody has turned "meet WCAG 2.2 AA" into work an engineer can pick up.
01
Scanners miss what matters
axe-core and Lighthouse catch missing alt text and contrast. They can't tell you if your focus order is logical or your custom widgets are keyboard-operable.
02
Reports don't ship fixes
A 60-page compliance PDF tells legal you did something. It doesn't tell a frontend engineer which token to change.
03
Audit and build are usually split
Most auditors don't touch code. I do both — nothing gets lost in the handoff.
Before you email
A few things that usually come up before someone books the audit.