Better Accessibility
by Default
Better Accessibility
Reasons to Care
-
Legal requirements
-
Limited staff or budget
-
Inclusive culture is a priority
- More users, more profit
Accessibility is...
Accessibility is
hard to get right.
Accessibility is emotional.
Accessibility is
easy to ignore.
Accessibility is
everyone's
responsibility.
Leadership
Copy Editors
UX Designers
Visual Designers
Developers
QA Testers
Leadership
- vocalize accessibility as a priority
- provide budget
- create an inclusive work environment
Content Managers
- ensure that the content uses clear language
- do not permit "dark horse" marketing techniques
- consistent phrasing
- img alt text
UX Designers
- logical workflows
- simplified user experience
- clear context and purpose
Visual Designers
- adequate color contrast
- Large enough font sizes - and think about zoom!
- Look at animation & scrolling expectations
- Is that interactive element large enough?
QA Testers
- Personas are your friend!
- Keyboard-only user
- Different types of color-blindness
- Test for ignore-colors!
- Learn about visible focus vs screen reader focus
Developers
You do not require permission to write accessible code.
Respect the Holy Trinity
HTML
JS
CSS
-
38 Success Criteria
-
Screen readers
- Keyboard navigation
Learn Your Tools
Addon Support
-
ember-a11y
-
ember-a11y-testing
-
ember-cli-template-lint
-
ember-a11y-landmarks
- ember-component-helper
Thank you!
melaniersumner
- Melanie Sumner
https://github.com/MelSumner
Better Accessibility
By Melanie Sumner
Better Accessibility
(Formerly "Accessible by Default: The Layered Workflow")
