A statement built from findings, not boilerplate
The mandatory entries on non-accessible content come from the barriers actually found. When those change, the basis of the statement changes with them.
ISMS & Risk
Accessibility
The statement grows out of audit results, not out of boilerplate
The accessibility statement is the only compliance document that has to name your own shortcomings in public. It knows three conformance levels, and the worst is a permitted answer as long as you explain what does not work and which alternatives exist. That is precisely why it needs substance behind it: subjects, an automated quick test for the machine-detectable barriers, a guided WCAG 2.2 audit for everything else, and a barrier list with status. The statement is derived from all of that and served publicly.
BFSGBITV 2.0EN 301 549WCAG 2.2
Features
Your benefits
The quick test knows its limits
The automated part checks what can be read unambiguously from the page structure. Contrast, keyboard operation and focus visibility need people, so they run through the guided audit rather than a green tick.
A score that stays usable
Repeat hits of the same check are capped. A page with eighty images lacking alternative text is not eighty times worse, the finding is the same.
Barriers with a history
Every finding carries a severity, the WCAG criterion and the snippet of the element in question. Later runs carry known items forward and mark vanished ones as resolved.
Capabilities
Capabilities in detail
- Accessibility statement under the German BFSG and BITV 2.0
- Three conformance levels from full to non-conformant
- Mandatory entries on non-accessible content and alternatives
- Feedback contact with name, address, telephone and form URL
- Reference to the enforcement procedure
- Date drawn up and date last reviewed tracked separately
- Public statement page, reachable without signing in
- One statement per tenant plus one for the instance
- Subjects for websites, applications, documents and apps
- Automated quick test of the stored address
- Protection against scans reaching internal addresses
- Score per run with counts of checks passed and failed
- WCAG 2.2 success criteria as a reference catalog with test hints
- Guided manual audit with a selectable target level
- Result and comment for each individual success criterion
- Barriers from quick test, audit or manual entry
- Severity, WCAG reference and element snippet per barrier
- Status workflow through to resolution, with automatic reconciliation
- Reports on audit status and open barriers
Result
A statement you can publish without unease: evidenced by audits, honest about what is still missing, and carrying a date that actually moves.
Experience Accessibility live
Schedule a no-obligation demo – we will show you the module with your own use cases.