danalexilewis
commented
7 years ago Definitely think should aim to conform to aria. Though maybe we can do an MVP of it? Something like resizable text via using ems for all text sizes.
I was excited about typography.js for design and wonder if it will help by making our text easily adjustable for impaired vision.
I would also love to have multi language support from the get go. Ie if we work out how it works now and document it then we can start implementing it into components and it wont feel hard or that we are double handling things.
After this I would prioritise in order:
- basic keyboard navigation - tabbing
- high contrast mode
- 2 other colour modes for colour blindness
- advanced keyboard navigation - arrows?
- screen reader (honestly I think this is basically a different site - ie we don't try to take what we are doing and make it work for screen readers and instead build an app for screen readers with consultation)
ahdinosaur
what should our approach be with accessibility?
i wonder if we should enforce some guidelines on whether our code, especially our dumb (storybook) react components, are "done".
for example, some aspects of accessibility for each component:
some general patterns:
what do y'all think our approach should be here?