Making A11y Official
summary
Argues that accessibility belongs in proposals as an accessibility line item with a modest upfront cost rather than an expensive retrofit, recommends an accessibility policy and repeatable checklists, and shows concrete checks: test with a screen reader, keyboard navigation, and tools like Wave while noting automated audits produce many false positives. Calls out common failures (PDF menus, JS calendars, hamburger icons without text, unnecessary ARIA) and says incremental testing in each sprint prevents million‑dollar rewrites later.
AI-written summary · about
