Application flows fall outside the BFSG but inside the AGG and SGB IX. Where uploads, required fields and session timeouts cost you applications.
Speech input fails when the accessible name omits the visible text. How success criterion 2.5.3 works and how to test this way of operating your site.
ATAG 2.0 audits the tool instead of the website alone: Part A covers the editing interface, Part B covers the guardrails that make accessible content the likely outcome.
Paid online courses fall under the BFSG, universities under BITV 2.0. How to make the learning journey from booking to certificate genuinely accessible.
Automated scans stop at the sign-in form. How a WCAG audit covers the protected area: scope, test accounts, session timeouts and screen reader testing.
Auto-rotating carousels violate WCAG 2.2.2 and lock out keyboard and screen reader users. How to make sliders accessible with pause, keyboard and ARIA.
96% of all WCAG errors come from six patterns - all in building blocks. Solve focus, keyboard and ARIA once in the component instead of on every page.
Plain language vs. easy language: lower reading barriers without extra budget, reach more people and meet WCAG - a building block of your BFSG conformance.
Self-built date pickers fail on keyboard, focus and target size. Here is how to make appointment booking operable under WCAG 2.2 for screen reader and keyboard users.