This document provides an accessibility primer with links to resources about web accessibility. It discusses what accessibility is, color contrast, color blindness, skip navigation links, testing websites for accessibility issues, screen readers, common disabilities, mobile accessibility, HTML heading tags, alt text for images, selecting options with screen readers, and questions about analytics for assistive technology users. Key resources include WebAIM.org for accessibility knowledge and tools to evaluate color contrast, test websites, and learn about screen readers and mobile accessibility testing.
2. What is Accessibility?
Web accessibility is the inclusive practice of ensuring there are
no barriers that prevent interaction with, or access to, websites
on the World Wide Web by people with physical disabilities,
situational disabilities, and socio-economic restrictions on
bandwidth and speed. (from https://en.wikipedia.org/wiki/
Web_accessibility )
Plethora of knowledge at Web AIM
https://webaim.org/
3. Color Contrast
For proper legibility the contrast between foreground and
background should be 4.5:1 or higher.
https://webaim.org/resources/contrastchecker/
4. Color Blindness
There are MANY forms of color blindness. Do not use color
alone to indicate status (such as green for up/good and red for
down/bad). Use words and/or differentiating icons.
http://www.colourblindawareness.org/colour-blindness/types-of-
colour-blindness/
https://www.color-blindness.com/coblis-color-blindness-simulator/
5. Skip to Main Content
Users using assistive technology like a screen reader do not
always need to hear the navigation of a site before getting to the
page content. Give them an option to skip over listening to it go
straight to the main content
https://webaim.org/techniques/skipnav/
6. Test Your Website (few free trials)
Put your URL in and get a high level readout of accessibility
issues.
https://webaccessibility.com/
7. Screen Reader Samples
If you’ve never heard a screen reader (like Jaws) read content,
its enlightening (and fast!)
https://www.youtube.com/watch?v=dEbl5jvLKGQ
https://www.youtube.com/watch?v=q_ATY9gimOM
8. Information on Disabilities
• Attention Deficit Hyperactivity Disorder (ADHD)
• Learning Disabilities
• Mobility Disabilities
• Medical Disabilities
• Psychiatric Disabilities
• Traumatic Brain Injury (TBI) and Post-Traumatic Stress Disorder (PTSD)
• Visual Impairments
• Deaf and Hard of Hearing
• Concussion
• Autism Spectrum Disorders
https://www.mightybytes.com/blog/how-many-users-with-disabilities-on-
site/
https://www.rochester.edu/college/disability/faculty/common-
disabilities.html
10. Heading Tags
Headings communicate the organization of the content on the
page. Web browsers, plug-ins, and assistive technologies can
use them to provide in-page navigation.
https://www.w3.org/WAI/tutorials/page-structure/headings/
11. Alt Tags
ALT Tags are invisible descriptions of images which are read
aloud to blind users on a screen reader. Adding ALT text allows
authors to include images, but still provide the content in an
alternative text based format. See example below for what a
screen reader experiences when no ALT Text is used.
https://accessibility.psu.edu/images/alttext/
12. Select Boxes
Don’t use select boxes as jump nav or to refresh a page view. A
screen reader reads all the options and the onChange event
fires, so it is very jarring if you just want to hear the options..
Have an ‘activate’ button outside the select box to do the action.
13. Questions to Research…
Is there a way to implicitly know (from Google Analytics or
similar) how often a screen reader accesses your app/site? What
about keyboard only or other assistive technologies? Usually
they are not recorded in the browser User Agent data.