Accessible Apps: BFSG Rules for iOS and Android
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 is created in everyday work: in components, editorial templates, documents and test routines. This category collects articles from implementation — accessible navigation, dialogs and carousels, alternative texts and image descriptions, captions and transcripts, tables and data visualisations, PDF documents and native apps. Added to this are topics such as screen reader testing, assistive technologies, plain language and involving people with disabilities in evaluation. We also cover the organisational side: training for editors and developers, acceptance criteria in tenders, documenting test results and dealing with legacy content that cannot be reworked all at once. It is equally about recording test results so they remain traceable at the next change instead of getting lost when the project ends.
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 is an ongoing editorial process: train alt text, link text, headings and accessible PDFs in the team to prevent the gradual re-barriering of your site.
Accessible navigation per WCAG 2.2: skip links, accessible menus with ARIA, aria-current, landmarks and visible focus management in practice.
The German Accessibility Strengthening Act has been in effect since June 2025. Who is affected, which deadlines apply, and what first steps are needed.
WCAG 2.2 introduces nine new success criteria. Focus Not Obscured, Dragging Movements and Redundant Entry explained with practical guidance.
Accessible checkout process: Usable payment forms, error handling, address fields and progress indicators for online shops.
Screen reader optimization for websites: ARIA landmarks, roles, live regions, semantic HTML and screen reader testing across all platforms.
Understanding and implementing WCAG contrast requirements: tools, dark mode, focus indicators and non-text contrast for accessible websites.
Build accessibility in early instead of retrofitting it: the cost advantage of shift-left, clear roles, design tokens and a Definition of Done for the BFSG.
Keyboard navigation for accessible websites: tab order, focus management, skip links, keyboard traps and custom widgets.
Creating accessible PDFs: tagged PDFs, reading order, alt text, tables and forms tested and implemented per the PDF/UA standard.
Website accessibility testing: automated and manual testing methods, keyboard and screen reader testing and the professional WCAG audit at a glance.