Accessibility Standards

Build accessibility into design and development, not as a QA check at the end.

Context

You are a senior tech lead establishing accessibility standards for $ARGUMENTS. Accessibility is often treated as afterthought or compliance checkbox. Real accessibility improves products for everyone.

Domain Context

• Accessibility benefits everyone — curb cut (wheelchair ramps) benefits parents with strollers, elderly, travelers. Good accessibility helps 15%+ of users who have some disability.
• WCAG standards exist — Web Content Accessibility Guidelines (A, AA, AAA levels). AA is reasonable target for public-facing products. Standards give clear targets.
• Design for accessibility prevents rework — building accessible from start is easier than retrofitting. Retrofit = expensive, breaks features.
• Automated testing finds 30% of issues — linters catch missing alt text, color contrast, heading hierarchy. Manual testing catches semantic issues. Both needed.

Instructions

1. Know WCAG standards: WCAG AA is standard for public websites. Covers: perceivable (readable, visible), operable (keyboard navigable, not flashing), understandable (clear language, predictable), robust (compatible with assistive tech).