This is page 4 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.
Self-built date pickers fail on keyboard, focus and target size. How to make appointment booking operable under WCAG 2.2 for screen reader and keyboard users.
XRechnung and ZUGFeRD flood invoicing - yet the human-readable PDF view must be accessible under PDF/UA for consumers. Here is how to get it right in practice.
Market surveillance authorities, information requests, deadlines and fines up to EUR 100,000: how a BFSG audit unfolds and how to prepare for it.
Parallax, auto-sliders and fast transitions can trigger dizziness. How prefers-reduced-motion and a pause mechanism make animations WCAG 2.2 compliant.
Alt text, descriptive link labels, semantic structure and contrast meet WCAG and support discoverability at the same time - accessibility and SEO as one lever.
Account opening, online banking and TAN approval must be accessible since 2025. What the BFSG requires of banks, savings banks and fintechs in practice.
Building search, autocomplete, facet filters and results lists accessibly: the combobox pattern, WCAG 2.2 and a practical test routine for shop teams.
Booking calendars, chat widgets and payment iframes are third-party code, yet BFSG duties stay with the operator. Evidence, testing and fallback routes.
E-books are a separate BFSG category: ten extra duties from Section 18 of the ordinance, EPUB Accessibility 1.1, metadata, testing and a backlist plan.