Leading Accessibility Initiatives In Open Source Library Software

Button Size  

• Larger buttons are easier to see for people with low vision.
• A larger hit target helps people whose mouse movements are imprecise.
• Large buttons stand out from the surrounding text. For people with cognitive disabilities, it’s easier to decide what to press if the buttons are larger.

Captions & Transcripts

• Audio and video content must have captions or transcripts for those who are Deaf or hard of hearing.
• Captions are also helpful for people with auditory processing issues, ADHD, and other sensory input disorders that make it difficult to focus on two modes of communication at once.
• Captions make it possible for everyone to watch videos in noisy environments like airports, bars, and buses.

Color Contrast

• Good color contrast helps people with low vision, who often struggle to read text with subtle colors.
• Strong contrast helps people distinguish links and buttons from the surrounding text.
• Too much contrast may create a visually loud design for people with some sensory disorders.
• Forced colors and Windows High Contrast modes may require fine-tuning images and borders.

Focus Outlines

• Focused elements should have a bold outline to help keyboard and switch button users stay oriented.
• Outlines can be different depending whether the element was focused using a keyboard or mouse.
• People who are interrupted can pick up where they left off more easily when focused form fields have bold outlines.

Form Labels

• Screen reader users need labels associated with every form field so they know what to enter.
• Labels provide a larger hit target for people with mobility issues. Clicking anywhere in the label area will place keyboard focus on the associated form field.
• Using persistent, visible labels helps people remember what to enter into each field. 

Headings & Landmarks

• Screen readers give users a menu of landmarks and headings that can be used to skim the page.
• Multiple landmarks with the same role, like navigation, should have distinct names via ARIA labels.
• Visually distinctive headings prevent confusion and help people stay oriented.

Keyboard Controls

• Screen reader users do not use mouse pointers. Every interactive element has to be operable using the keyboard. 
• People whose mouse movements are imprecise may also find it easier to navigate forms and menus using the keyboard.
• Buttons can be pressed using Space or Enter keys.

Link & Button Names

• Multiple links or buttons with the same accessible name can be distinguished from one another with ARIA descriptions.
• Icon buttons should have tooltips to help clarify the icons’ meaning.
• Accessible names should match the visible text or tooltip so speech recognition users can dictate their choices accurately.

Semantic HTML  

• Different tags have implicit roles that are announced to screen readers.
• The role tells the user which keyboard or switch button actions they can use. Incorrect roles can prevent users from accomplishing their tasks.
• Users with memory or attention deficit issues may forget how custom widgets work if they differ from standard HTML controls.

Plain Language  

• Screen reader users listen at very high speeds–unless they have to slow down when they encounter unfamiliar words.
• Jargon can be difficult for sign language interpreters to convey.
• Plain language helps make labels and instructions clear to early career professionals and language learners as well as those with cognitive disabilities.

Text Alternatives

• Images and icons should have text equivalents for screen reader users using alt attributes or visually hidden text.
• Decorative images should be hidden from screen readers.

About WCAG

• The Web Content Accessibility Guidelines are the basis of all web accessibility laws around the world.
• While laws may specify a version, it’s best to use the most recent version of WCAG.
• Level AA compliance is required for public institutions in the US and Canada.
• WCAG 3, the next major version, will introduce guidelines for cognitive accessibility.

• Web Content Accessibility Guidelines (WCAG) v2
• Web Content Accessibility Guidelines (WCAG) v3 Working Draft
• Evergreen Developers Accessibility Guide

• equinoxEDU: Resource Library
  • View our training videos and check back-- more videos are added regularly!
• equinoxEDU: Events
  • Learn more about our upcoming events and find resources related to past events.