Accessibility (a11y)
Questions that need answering
-
If a form has a doesn't attempt submitting when the 'enter' key is pressed (non-standard response) as it would by default, should the user be alerted? If so, what's the best approach? -
Do screen readers/a11y tools utilize meta tags at all? If not, apply desc/keywords to nav buttons as well... could also aria-label for long hover/focuses? -
Why is it the developers responsibility to add "skip to" navigation, shouldn't the tool they are using to access the site be responsible for that? (I implemented it already lol) -
Should there be a 'footer to main' skip? (implemented 😇 )
Related links
- https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles
- https://adamsilver.io/articles/where-to-put-buttons-in-forms/
- https://www.gov.uk/service-manual/technology/designing-for-different-browsers-and-devices#browsers-to-test-in
- https://www.gov.uk/service-manual/technology/testing-with-assistive-technologies#what-to-test
Emojis
Don’t
- Don’t repeat emojis over and over;
- Don’t place emojis throughout a message;
- Don’t put a call to action after the emoji.
Do
- Do use one or two emojis if you like, most blind people get a kick out of the descriptions;
- Do put any important information before the emojis so we’ll be more likely to hear them;
- Do limit yourself to no more than three emojis per message.
Edited by Lorin Halpert