Accessibility and usability belong together – just like doors and access. If a door is closed, people can’t enter. If a website isn’t accessible, people can’t use it. Accessibility requirements are evolving. So we evolve monitoring.
Websites come to life in the user's browser – not on the server. The server only delivers the building blocks. How a page actually looks, behaves and performs is determined in the browser. Anyone testing only on the server is checking the plan, not the result. Whether a page truly works becomes visible on the screen where it appears. That's where we look.
The Barrierefreiheitsstärkungsgesetz (BFSG) is requiring private sector websites to meet WCAG 2.1 AA since June 28, 2025.
Automated accessibility testing can detect only part of the WCAG requirements. The following criteria belong to the technically testable rules where automated checks can identify common violations.
Perceivable
Operable
Understandable
Robust & BFSG-specific
Automated checks detect common WCAG 2.1 AA violations directly in the browser.
WCAG Compliance
Images
Document Structure
Touch & Mobile
Common questions about BFSG, WCAG, and website accessibility.