Accessibility
Keyboard navigation, screen readers, color contrast, ARIA — making the app usable by everyone.
Why we need this / what value this brings
Inaccessible UI excludes real users and is disproportionately cheap to fix early compared to retrofitting later.
When to use this
From the start on any new interactive component, especially the highest-stakes flow (booking).
How to use or implement this
Use semantic HTML and ARIA attributes by default, and test keyboard navigation on the booking flow specifically.
Research questions
- Has an accessibility pass ever been done on the booking flow specifically (the highest-stakes interaction)?
Empty folder — drop notes, links, and findings here as you research.