Useful Jupyter Accessibility Resources
Useful Jupyter Accessibility Resources#
🔔 Looking for accessibility docs?
One of our goals is to collect information about accessibility and create documentation to empower the Jupyter community to help us make our software accessible. Please use this section to begin to aggregate relevant accessibility third party standards, guides, and documentation.
The World Wide Web Consortium (W3C) publishes a number of international recognized technical guidelines, like the Web Accessibility Initiative (WAI) and XHTML standards. These guidelines assure that a given website can be accessed and consumed by as many people as possible.
Accessible Rich Internet Applications (WAI-ARIA)#
Is important to remember that links, buttons and form elements are the only elements that can receive focus in HTML. Meaning that lists, paragraphs,
span, will never get focus from the keyboard making them not accessible to users that are not using a mouse. This is where WAI-ARIA provides web developers with techniques to enable keyboard users have a structure, making their websites more navigable. This guideline also include modules for Graphics and Digital Publishing.
ARIA is an additional layer to web content, not a required layer. Though ARIA is powerful, it is important to remember that misused ARIA can make a worse experience for assistive tech users, especially screen reader users. It is often warned that “No ARIA is better than Bad ARIA.” Doing relevant research before using ARIA and testing results with screen readers is especially wise here.
Web Content Accessibility Guidelines (WCAG)#
The WCAG is a technical standard that takes care of information shared through websites. This includes content like text, images and sounds, and code or markup that specify structure and presentation.
This standard is stable and does not change after it is published. The latest draft, WCAG 2.2, has 13 guidelines organized under four principles: perceivable, operable, understandable, and robust. Each guideline has a testable success criteria for conformance that can vary from A, AA, and AAA. Until WCAG 2.2 formally becomes a standards document, WCAG 2.1 remains the most up to date standard.
Many countries have laws that specify the ways in which they expect digital content to be accessible. Some of these laws require that software meet their accessibility guidelines to be used in specific places, like schools. For example, Section 508 compliance is important in the U.S.
Depending on the project and where in the world it is intended for use, there may be more specific accessibility resources.It’s worth noting that several digital accessibility laws globally do draw on the work of the W3C including WCAG.