Accessibility
bananabay is committed to meeting WCAG 2.2 AA across the product experience. The practical standard is simple: the app should be usable without guessing how the interface is wired.
Accessibility issues are treated as product defects. Formal conformance claims wait for automated scans, keyboard testing, contrast and reflow review, and screen-reader smoke testing.
Current commitments
- work toward WCAG 2.2 AA across first-class routes and user workflows
- keep navigation reachable by keyboard
- use visible focus states and semantic page structure
- keep color contrast and motion choices practical
- fix accessibility bugs as product bugs, not decorative cleanup
Accessibility feedback can be sent through the contact page. Clear reproduction steps help get the fix landed without ceremony.