This is page 5 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.
On 10 September 2026 the W3C published a new WCAG 3 Working Draft. What has changed, why WCAG 2.2 AA remains the relevant benchmark and what teams should do today.
Section 17 BFSG is no free pass but a burden of proof: how to calculate, document and notify the Annex 4 assessment and keep it on file for five years.
ATMs, ticket and check-in machines fall under the BFSG. What applies to existing terminals until 2040 and why the accompanying service gets no grace period.
EN 301 549 is the central EU standard for digital accessibility under the BFSG. How the EAA, the standard and WCAG 2.2 connect and what version 4.1.1 brings.
Accessible sign-in under WCAG 2.2 SC 3.3.8: password managers, magic links, passkeys and low-barrier CAPTCHA alternatives using object recognition and audio.
Cookie banners are the first interaction and fall under the BFSG. Where consent banners fail WCAG 2.2 and how to make them accessible and compliant.
Many businesses assume that as a micro-enterprise they are BFSG-exempt. When the exemption applies, why it covers services only and what Section 17 demands.
The BFSG now covers native apps too. What iOS and Android apps must meet for WCAG 2.1 AA and EN 301 549: labels, tap targets, contrast and focus order.
Accessibility overlays promise one-click BFSG compliance but only change the surface. Why studies, the DBSV and authorities reject them and what truly works.