Try two status-message examples. Learn when status or alert fits, why insertion timing matters and which checks still need a screen reader.
Try an error summary and a live region in two interactive forms. Check focus, error messages, corrections and repeated submission, with clear testing limits.
Lighthouse scores 100 for accessibility, but axe finds issues? Compare rules, versions and page states, then try tested examples to fix the specific problems.
Understand non-text contrast with good and bad examples of input borders, check marks and icons. Learn what to check on your website and what scans can miss.
Test cookie banner accessibility across keyboard, focus and settings. Follow a practical checklist and reproduce a measured dialog naming failure and fix.
BFSG and medical practices: who is affected? What applies to websites and appointment booking? A practical guide on accessibility, telephone assistance, and patient communication.
How agencies use navable to audit faster and more consistently and guide clients through the BFSG. Pre-audits, dev-ready fix prompts & shareable reports.
The BFSG has been in effect since June 2025. This updated checklist shows what businesses need to check now – from WCAG 2.1 AA and EN 301 549 to documentation and ongoing monitoring. Updated June 2026.
Many accessibility issues only appear on mobile devices. Learn why multi-device audits are essential and how navable scans desktop, tablet, and mobile simultaneously.
navable MCP v0.2 adds Pa11y/HTMLCS as an optional second scan engine alongside axe-core. Cross-confirmed findings, server-side deduplication, and higher confidence WCAG audits — all running locally in your IDE.
axe-core scans and structured fix plans for AI coding agents: setup, technical findings and the limits of automated testing.
Learn how to fix WCAG 1.1.1 with practical alt text examples, decorative image handling, and simple code patterns for BFSG-oriented website accessibility.
How to build an accessible feedback channel under the BFSG: keyboard access, accessible names, contrast requirements, and when a modal is actually needed. Includes a quick technical checklist.
Maintain an accessibility statement after changes: test, document, revise the draft and approve it for publication.
Install the navable Widget in WordPress, register your domain and check the integration. Includes troubleshooting steps and the limits of the plugin.
Learn when you can rely on §17 BFSG and what documentation is required. Concrete criteria, practical examples, and a step-by-step guide for using the disproportionate burden exception in effect since June 28, 2025.
Accessibility color contrast made practical: contrast checker WCAG, website/web contrast checker tips, UX best practices, plus BFSG/EAA context.
The micro-enterprise exception (§ 3 para. 3 BFSG) is often misunderstood as a blanket exemption. A technical analysis of the distinction between service and product liability for online retailers.
Check BFSG scope: covered offerings, microenterprises, transition rules and practical next steps for your assessment.
Check your source code with the free Axe Accessibility Linter for VS Code. Learn which issues it detects and which browser and manual checks you still need.
What an accessibility widget offers for fonts, contrast and reading preferences, and which barriers need audits, manual checks and fixes in your source code.
Federal public bodies publish a statement under BGG and BITV 2.0. The BFSG effective date does not establish this duty.
Test accessible HTML forms with examples of labels, unique IDs and autocomplete. Compare browser names and scanner findings, then check your form step by step.
Check link text, button names, contrast and keyboard access. Use this checklist to make navigation understandable and usable for people with disabilities.
Check image alternatives, captions, audio descriptions and PDF structure. Use this checklist to prepare media for people with different disabilities on your site.
Check whether pop-ups can be closed with a keyboard and captchas offer alternative ways to proceed. Use the checklist to find barriers and plan manual tests.
Check font size, text resizing, spacing and contrast. Learn which WCAG criteria apply and which layout values are recommendations for readable website text.
Check menus, headings, skip links and keyboard paths. Use this checklist to find common barriers in your website navigation and page structure, then plan fixes.
Check headings, image alternatives, form names and focus with a screen reader. Use these examples to find specific barriers that prevent people using your website.