Accessibility testing for your sign-up, login and payment journeys
Since 28 June 2025, the European Accessibility Act (Directive (EU) 2019/882) and Germany's BFSG require many consumer-facing digital services, including consumer banking and e-commerce services, to be accessible. I test your critical journeys against WCAG 2.1 AA, put automated checks into your CI and give you a report your developers can act on.
Not legal advice. Whether the EAA or BFSG applies to your product is a legal question for your counsel. Assertwise tests; it does not advise on law.
The problem
- Automated scanners catch only part of the issues. Keyboard traps, unclear error messages and broken screen-reader announcements need manual testing.
- Payment UIs have hard cases: SCA timeouts, one-time-code fields, third-party iframes, PDF statements.
- Without checks in CI, every release can undo last quarter's fixes.
How Assertwise helps
- Manual testing of your critical journeys with keyboard and screen readers on desktop and mobile.
- Automated accessibility checks (axe-core via Playwright) in your CI, failing the build on new violations.
- Findings mapped to WCAG success criteria, with reproduction steps, severity and a suggested fix.
- Retest after your fixes.
Scope and deliverables
- Written scope within 2 working days: which journeys, platforms (web) and assistive technologies.
- Baseline: WCAG 2.1 level AA, the basis of EN 301 549 v3.2.1, plus the additional WCAG 2.2 criteria adopted in EN 301 549 v4.1.1 (published September 2026; not yet cited in the Official Journal under the EAA) on request.
- Report with findings per journey and per WCAG criterion.
- Playwright accessibility tests in your repository.
- Retest report.
What we don't do
- No legal advice on whether the EAA, BFSG or another national law applies to you.
- No conformity declarations, accessibility certificates or seals.
- No writing of your accessibility statement.
- No design or front-end implementation of fixes unless separately agreed.
FAQ
Are we in scope? That depends on what you offer to whom; The service obligations target services for consumers, so purely B2B offerings are generally outside them. for example, the BFSG exempts microenterprises providing services (§ 3(3)). Ask your legal counsel – I can then test whatever is in scope.
Which standard do you test against? WCAG 2.1 AA, the basis of EN 301 549 v3.2.1, which the German Federal Accessibility Agency names as the central technical reference. EN 301 549 V3.2.1 is based on WCAG 2.1 AA and is the edition cited in the Official Journal, under the Web Accessibility Directive only; no edition is yet cited under the EAA. V4.1.1 (Sept 2026) moves to WCAG 2.2 and has not yet been cited in the Official Journal either (re-check on publication day). On request we include the WCAG 2.2 criteria.
Is an automated scan enough? No. It's a useful floor, but meaningful alt text, focus order and understandable errors need a human.
Start with your most important journey
Sign-up, login or payment: pick one and get a written scope within 2 working days.
Sources
- Directive (EU) 2019/882: https://eur-lex.europa.eu/eli/dir/2019/882/oj
- European Commission, European Accessibility Act: https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/union-equality-strategy-rights-persons-disabilities-2021-2030/european-accessibility-act_en
- BFSG § 2: https://www.gesetze-im-internet.de/bfsg/__2.html · § 3: https://www.gesetze-im-internet.de/bfsg/__3.html
- Bundesfachstelle Barrierefreiheit, Normen und Standards: https://www.bundesfachstelle-barrierefreiheit.de/DE/Barrierefreiheitsstaerkungsgesetz/Normen-und-Standards/normen-und-standards_node
- W3C WCAG 2.1: https://www.w3.org/TR/WCAG21/