Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 8.59 KB

ACCESSIBILITY_REQS.md

File metadata and controls

72 lines (49 loc) · 8.59 KB
Raw

Accessibility

I can verify that the changes made by my PR meet all the following accessibility concerns:

Content structure

  • Content appears in a meaningful order WCAG on meaningful order
  • Heading and labels describe the relevant content WCAG on headings and labels
  • Heading and labels are each unique. Where that is not possible, there is enough context information that users can tell the difference between duplicated headings (think of this in the context of a document outline, where the user isn't reading the full text of the page but skimming through headings)
  • The information or behavior of the content is not dependent on visual/audio formatting WCAG on info and relationships
  • User agents and assistive technologies (AT) can parse all the content WCAG on parsing
  • AT can gather information about, activate (or set) and keep up to date on the status of user interface controls in the content WCAG on name, role, and value

Focus and keyboard access

Flashes, motion, animation

Audio and video

  • If audio plays for more than 3 seconds, users have a way to pause or stop that audio or adjust its volume WCA on audio control
  • Content is not dependent on audio/sensory info alone to convey information, indicate an action, prompt a response, or distinguish a visual element WCAG on sensory indicators
  • Pre-recorded media (anything not captured in real time, such as webcam feeds) have captions, audio descriptions, and a transcript WCAG on captions (pre-recorded)
  • Media captured in real time have captions WCAG on captions (live)

Text

  • Text can be resized without assistive technology to +200%, without losing content or functionality. Exceptions: captions and images of text WCAG on text resizing
  • Text-in-image is not relied upon to convey information. Exceptions: when the info is dependent upon the image format, such as logos or typography samples WCAG on images of text
  • The page language (English, for ex.) is set in metadata, and any exceptions to the main documentation language are noted using a lang attribute WCAG on page language and WCAG on language parts

Color

  • Content is not dependent on color alone to convey information, indicate an action, prompt a response, or distinguish a visual element WCAG on use of color
  • All text has a 4.5:1 color ratio against its background, tested via AxE extension or in a contrast checker. Exceptions: logos, "incidental" text (decorative text, text in an inactive element) WCAG on color contrast

Context

  • All non-text content has a text alternative WCAG on non-text content
  • The value of the page title is informative and specific to the current page WCAG on page titles
  • Link text, wherever possible, informs the user of where the link goes without having to rely on other items for context. No "read more" links, for example. WCAG on contextual links

Controls and inputs

  • Whenever a user has to input data or select something, there are sufficient instructions/labels to explain what's expected of the user (including any formatting they need to follow) WCAG on labels and instructions
  • Changing the value of an input doesn't change page context without first making the user aware of those impending changes (so you could write the instructions/label for an input that lets the user know that the page content will change in a particular way) WCAG on inputs and context

Errors

  • For automatically-detected errors on inputs: users are made aware of the error, there is text describing the error and suggestions on how to fix it WCAG on error identification WCAG on error suggestion
  • User input that results in a legal commitment, financial transaction, or modification to user-controllable data in data storage systems can be reversed, verified, or confirmed in case of errors WCAG on error prevention

Navigation

  • There are multiple ways to navigate to a page within a set of pages. This one requires a little bit more thoughtful interpretation, so check out WCAG for more information and examples on "multiple ways" WCAG on multiple ways
  • Navigational items that are repeated from page to page appear in a consistent order, unless the user has changed that order in some way WCAG on consistent navigation
  • Make it easy for users to identify and navigate through blocks of content, by identifying them visually and semantically WCAG on bypassing blocks
  • Provide controls so that users can jump over these blocks of content in the fewest steps possible (for example, if a block of content has lots of focusable items, consider a jump to skip over that block, or adding keyboard shortcuts)

Misc