Zum Inhalt springen
BFSG compliance since 2025

Blog — Page 3

WAI-ARIA: Role, State and Live Region in the Accessibility Tree1. Role (role)First rule: prefer native HTML over rolebuttonnatively focusablerole=tabno HTML equivalentlandmark | widget | document | abstractrole defines what an element is2. State and Propertyaria-expanded=falsearia-selected=truearia-checked=mixedaria-disabled=trueState changes via JavaScriptScreen reader says: collapsed / expanded3. Live Region: dynamic announcementaria-live=politewaits for a speech pausestatus message, result countaria-live=assertiveinterrupts immediatelycritical errors onlyrole=status / alertregion must exist in DOM firstotherwise no announcementCore rule: No ARIA is better than bad ARIA (W3C WAI)Test with real screen readers | do not rely on automation alone
WCAG Jun 3, 2026

Using ARIA Correctly: Roles, States, Live Regions

WAI-ARIA in practice: roles vs. native HTML, states like aria-expanded and aria-selected, live regions with polite and assertive plus the most common mistakes.

13 min read Read →
Accessible Form: Label, Error and ValidationContact FormName*Anna ExampleEmail*anna@example!Please enter a complete email address (domain missing)PhoneOptional - format: 0123 4567890Message*Submit* Required fieldCorrect Associationlabel for=emailinput id=emailaria-required=truearia-invalid=truearia-describedby=errautocomplete=emailrole=alertWCAG 2.2 Form Criteria3.3.1 Error Identification3.3.2 Labels or Instructions3.3.3 Error Suggestion1.3.5 Identify Input Purpose3.3.7 Redundant Entry3.3.8 Accessible Authentication
WCAG Jun 1, 2026

Accessible Forms: Labels, Errors and Validation

Accessible forms per WCAG 2.2: programmatic labels, required field marking, error messages with aria-describedby and role=alert, plus focus management.

13 min read Read →
Accessibility as an Award Criterion in TendersAccessibility gate in the tender processBid Awith evidenceBid Bwithout evidenceEvaluation of the bidEN 301 549 / BITV 2.0Awardbid is eligibleExclusionnot eligibleevidence okevidence missingeligibleexcludedRequired evidence in IT tenders1Conformance report(ACR / VPAT)Documents clause by clausehow the bid meets theEN 301 549 standard.Mandatory2AccessibilitystatementPublic statement withconformance status anda feedback mechanism.Required3BITV test /audit reportIndependent evidenceof accessibility by arecognized procedure.EN 301 549Procurement volume 2024: EUR 135.2 bn - no bid is eligible without evidence
Vergabe & Recht May 29, 2026

Accessibility in Public Tenders and Procurement

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.

13 min read Read →
Accessible Typography: the four adjustment leversLine height1.5xline-heightParagraph spacing2xafter paragraphLetter spacing0.12xletter-spacingWord spacing0.16xword-spacingA layout must allow these text spacings without any loss of content (W3C WCAG 2.2, 1.4.12)Clearly distinguishable letterformsI l 1easily confusedI l 1Atkinson Hyperlegible200 percent scaling100%200%without layout breakage (WCAG 1.4.4)10 %of people are affectedby dyslexia(British Dyslexia Association)Better readability without a special fontLeft-aligned text, sans-serif screen fonts andadjustable spacing beat a dyslexia font(Annals of Dyslexia, British Dyslexia Association)
Webdesign May 27, 2026

Accessible Typography: Fonts, Size and Readability

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.

12 min read Read →
BFSG 2025: Legal Requirements OverviewAccessibility Strengthening Act (BFSG) - In Effect Since June 28, 2025Who Is Affected?E-Commerce ProvidersService ProvidersBanks, TelecommunicationsWhat Is Required?WCAG 2.2 AA ConformanceAccessible DocumentsAccessibility StatementWhat Penalties?Fines up to 100,000 EURSales ProhibitionsCease-and-Desist RiskFirst StepsConduct Status AnalysisPrioritize BarriersCreate Action PlanBFSG Timeline2021Enacted06/2025In Effect2025+Market SurveillanceOngoingFinesAffected IndustriesE-Commerce and Online ShopsBanking ServicesTelecommunicationsPassenger TransportBFSG Compliance ChecklistWCAG 2.2 AuditAccessibility StatementFeedback MechanismRegular TestingFines up to 100,000 EUR | Sales Ban | Cease-and-Desist | Market Surveillance by Authorities
Barrierefreiheit May 25, 2026

BFSG 2025: Key Facts for Companies

The German Accessibility Strengthening Act has been in effect since June 2025. Who is affected, which deadlines apply, and what first steps are needed.

14 min read Read →
WCAG 2.2: New Success Criteria in DetailWCAG 2.2 - Published October 2023 - 9 New Success CriteriaFocus Not Obscured2.4.11 (AA) / 2.4.12 (AAA)Focus must not be obscuredSticky headers, modals, overlaysDragging Movements2.5.7 (AA)Alternative to drag-and-dropSliders, sorting, file uploadRedundant Entry3.3.7 (A)No duplicate data entryAutofill, carry-over, checkboxAdditional AA Criteria2.4.13 Focus Appearance2.5.8 Target Size3.2.6 Consistent Help3.3.8 Accessible AuthConformance LevelsLevel ALevel AALevel AAABFSG requires at least AA conformancePractical Relevance of New CriteriaMobile use optimizedCognitive barriers reducedMotor impairments addressedTouch interaction improvedFrom WCAG 2.1 to 2.2: 9 New Criteria | 6 at AA Level | 3 at A/AAA LevelFocus Management | Touch Targets | Drag Alternatives | Authentication | Help Consistency | Input Reduction
Barrierefreiheit May 22, 2026

WCAG 2.2: Implementing the New Success Criteria

WCAG 2.2 introduces nine new success criteria. Focus Not Obscured, Dragging Movements and Redundant Entry explained with practical guidance.

13 min read Read →
Accessible Checkout: Inclusive Order Process1. Cart2. Address3. Payment4. ConfirmationAccessible Form FieldsFirst Name *JohnEmail *john@example.comZIP Code *Please enter a valid ZIP codelabel + aria-describedby + aria-invalid + autocompleteAccessible Payment SelectionCredit CardSEPA Direct DebitPurchase on Accountrole=radiogroup + aria-checked + keyboard navigationCheckout Accessibility RequirementsAll fields labeledInline error messagesKeyboard operableScreen reader optimizedAutocomplete attributesaria-live regionsSkip linksProgress indicatorResult: Higher Conversion Through Accessible Checkout+12% Conversion Rate71% fewer form errors15% of population reached
Barrierefreiheit May 19, 2026

Accessible Checkout for Shops

Accessible checkout process: Usable payment forms, error handling, address fields and progress indicators for online shops.

13 min read Read →
Accessible email: what actually mattersSubject: Your order is on its wayFrom: Example Shop • to: customer@example.comlang=enOrder confirmationReal text, not an image: readable aloud, scalableand visible even when images are blocked.alt: sneaker, side viewrole=presentationTrack shipmentContrast 4.5:1checkedFont size around 14–16 px, scalable via zoomColors robust in light and dark modelang attributeWCAG 3.1.162% missing (EMC)Alt textWCAG 1.1.148% missing (EMC)Contrast 4.5:1WCAG 1.4.3text on backgroundLayout tablerole=presentation84% missing (EMC)Font sizescalablearound 14–16 pxDark moderobustreadable in both modes99.88%of HTML emails withserious barriers (EMC)47.88%of images withoutalt text (EMC)How the email passes the testReal text, declared language, checked contrast, robust in dark mode
E-Mail-Marketing May 18, 2026

Accessible Newsletters: Email Marketing Under the EAA

Accessible newsletters and transactional emails under the EAA and WCAG 2.1: lang attribute, alt text, contrast, real text and dark mode made practical.

13 min read Read →
Screen Reader Optimization: Semantic Page Structurerole=banner | Navigation Bar | Skip Link: Jump to ContentLandmarksrole=bannerrole=navigationrole=mainrole=complementaryrole=contentinforole=searchScreen reader navigationjump between landmarksrole=mainh1: Page Title (once per page)Introductory text with semantic markuph2: Section HeadingParagraph text (p elements, not div)img alt=DescriptionDecorative: alt=emptyaria-live=politeDynamic contentHeading Hierarchy: h1 - h2 - h3 - h4Never skip levelsARIA Rolesaria-labelaria-describedbyaria-expandedaria-hiddenaria-currentaria-liveFirst rule: Prefernative HTML!Test with screen readers on Windows, macOS, iOS and Androidrole=contentinfo | Footer with Contact, Links and Accessibility Statement
Barrierefreiheit May 16, 2026

Screen Reader Optimization: Making Your Website Readable

Screen reader optimization for websites: ARIA landmarks, roles, live regions, semantic HTML and screen reader testing across all platforms.

14 min read Read →