Service pillar
Accessibility audit (WCAG 2.2, BFSG, EAA)
Defensible conformance report, EU jurisdiction, B2B contracts.
Pricing is individual. I reply within one working day.
- WCAG 2.2 AA 86 success criteria, AA default
- EAA in force from 28 June 2025
- BFSG (DE) ecommerce pre-purchase flow scope
- Manual + auto scanner-only audits miss 60–70%
What I ship
A written conformance report mapping each failure to a specific WCAG 2.2 success criterion and the corresponding BFSG or EAA clause where applicable. Effort estimates per item. A partial conformance statement template ready to publish. A 60-minute walkthrough so your team can act on the backlog without me.
Why automated scans are not enough
Tools like axe DevTools and WAVE are essential, but they catch roughly a third of WCAG issues. The rest is keyboard navigation, screen reader behaviour, focus order, error messaging, content-quality judgements, and the pre-purchase flow that the EAA explicitly scopes for ecommerce. An audit that does not include manual review and assistive technology testing will not stand up if a regulator or claimant asks how the conformance statement was reached.
Accessibility as a measurable SEO lever
Accessibility is not only a compliance baseline, it is a measurable organic-search lever. Anne-Mieke Bovelett's WordCamp Portugal 2026 session "The SEO visibility hack" documented a 23 percent organic traffic lift on a case-study site after closing WCAG 2.2 AA gaps that overlap with on-page SEO signals (heading hierarchy, alt text quality, link text specificity, form labelling, error recovery copy). I attended the talk in Porto on 16 May 2026 and now include the overlap analysis as a standard appendix in the conformance report so the remediation backlog can be sorted by both legal exposure and organic-search impact.
Who this is for
- WooCommerce stores subject to the EAA pre-purchase scope from 28 June 2025
- German B2C and B2B sites covered by BFSG (in force the same date)
- Public-sector procurement processes that require a third-party conformance statement
- Headless front ends on Astro or Next.js where the WordPress admin accessibility is handled separately
Engagement model
Senior B2B contracts on EU jurisdiction. Three-week window from kickoff to report. Pricing is individual. Quarterly re-audits available on retainer.
Frequently asked questions
Which standards does the audit cover?
WCAG 2.2 Level AA as the technical baseline. The EU Accessibility Act (Directive 2019/882) and the German BFSG layer regulatory requirements on top, including the pre-purchase flow for ecommerce. Norwegian Likestillings- og diskrimineringsloven enforces WCAG 2.1 AA for public-sector and large private-sector sites.
Is automated scanning enough?
No. Tools like axe DevTools and WAVE catch roughly 30 to 40 percent of WCAG issues. The rest requires manual review with a keyboard, screen reader testing on real assistive tech, and a content-quality judgement that no scanner can make. The audit always combines both.
What does the conformance report look like?
A written report mapping each failure to a specific WCAG 2.2 success criterion, the corresponding BFSG or EAA clause where relevant, an effort estimate, and a remediation plan. Plus a partial conformance statement template that you can publish on your site to satisfy the regulator's transparency requirement.
Can you fix the issues you find?
Yes, as a separate engagement. The audit deliverable is decoupled from implementation so the conformance report stays defensible. If you ask me to also remediate, the implementation gets scoped from the audit findings; pricing is individual.
How does this work for headless WordPress front ends?
Same standards, different rendering layer. The WordPress back end has its own admin accessibility considerations; the public front end on Astro or Next.js carries the WCAG conformance burden. I audit the rendered front end against the same WCAG 2.2 success criteria and treat the headless boundary as part of the scope.
Explore other WordPress services and knowledge base
Strengthen your business with professional technical support in key areas of the WordPress ecosystem.
NIS2 and DORA scope mapping, supplier register, incident runbook.
Audit, hardening, and incident risk reduction.
WCAG 2.2, BFSG, EAA conformance report and remediation backlog.
Stability, updates, and post-launch support.
Custom WordPress engineering and architecture.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Supporting articles
CRA covers products with digital elements. NIS2 covers entities. DORA covers financial entities. When all three apply at once, headless WordPress sits at the intersection. I sketch what the joint evidence package looks like in 2026.
The NIS2 Directive (2022/2555) was to be transposed into national law by 2024-10-17. The DORA Regulation (2022/2554) applies directly from 2025-01-17. For a WordPress site operator this means specific obligations if the site relates to a regulated entity. We explain it without panic, with references to the texts of the acts.
Article 21 of Directive 2022/2555 lists ten risk-management measures every in-scope entity must implement. I map each one to a WordPress agency control, with the evidence file each one requires for audit.
Cluster reading
Standards and method
- WCAG 2.2, BFSG, and EU Accessibility Act: 2026 compliance stack
- WordPress accessibility under WCAG 2.2 (2026 guide)
- Practical accessibility auditing workflow
Regulatory scope
Adjacent services
Reference
Get the conformance report your procurement needs
Tell me the templates in scope and the regulatory frame (EAA, BFSG, sector-specific). I reply within one working day.
Contact me