Accessibility Statement and Feedback Mechanism
What BFSG Annex 3 requires for an accessibility statement and what the EU model adds: conformance status, known barriers and a feedback mechanism.
This is page 7 of the posts from our blog. The newer posts are on the pages before.
Each post explains one topic. Below the title there is a short text about it. Click on a post. Then you can read the whole text.
The posts are on more than one page. Below the list you can choose another page.
What BFSG Annex 3 requires for an accessibility statement and what the EU model adds: conformance status, known barriers and a feedback mechanism.
Captions, transcripts and audio description under WCAG guideline 1.2 and the BFSG: what makes video and audio accessible in 2026 - explained in practice.
How to write alt text under WCAG 1.1.1 correctly: describe informative, decorative and complex images, charts and infographics with long descriptions clearly.
How the BFSG is enforced: market surveillance, association lawsuits, defect reports, deadlines and statutory measures. Explained factually, with an action plan.
WAI-ARIA in practice: roles vs. native HTML, states like aria-expanded and aria-selected, live regions with polite and assertive plus common mistakes.
Accessible forms per WCAG 2.2: programmatic labels, required field marking, error messages with aria-describedby and role=alert, plus focus management.
Accessibility as a mandatory criterion in IT tenders: BITV 2.0, EN 301 549, required evidence such as a conformance report and VPAT, and the exclusion risk.
Readable font choice, size, line spacing and 200 percent scaling under WCAG 2.2: how to get accessible typography right, without the dyslexia-font myth.
The German Accessibility Strengthening Act has been in effect since June 2025. Who is affected, which deadlines apply, and what first steps are needed.