2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)This applies to native apps by replacing “Web pages” with “screens”. Requirements (Web only) A “Skip to content” link is provided, allowing users to move the keyboard focus directly to the main content area; The “Skip to…

2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)This applies to native apps by replacing “Web pages” with “Screens”. Requirements Each page has a title that is unique within the app/website. Each page has a title that indicates its topic or purpose. Why is it important? This ensures that people…

2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)This applies to native apps by replacing “Web page” with “screen”. Requirements When navigated sequentially using a keyboard, interactive elements should receive focus following a…

2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Requirements Why is it important? This ensures that screen…

2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Requirements Ensure that each page can be found and navigated to in more than one ways. In addition…

2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) Requirements Make sure that elements that are identified as headings in code describe the purpose or topic of the content that follows; Make sure that elements that are identified as labels in code indicate the purpose of the input fields/components that they…

2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Requirements Why is it important? Sighted keyboard and switch device users track where they are on a page/screen as they navigate through focusable elements, similar to using a remote control with a TV…

2.5.1 Pointer Gestures: All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. (Level A) Requirements If a feature requires the user of several fingers at the same time, make sure that the user interface offers…

2.5.2 Pointer Cancellation: For functionality that can be operated using a single pointer, at least one of the following is true: (Level A) No Down-Event: The down-event of the pointer is not used to execute any part of the function; Abort or Undo: Completion of the function is on the up-event, and a mechanism is…

2.5.3 Label in Name: For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)A best practice is to have the text of the label at the start of the name. Requirements Every interactive component must have a name that assistive technologies…