Digital A11y

reading order

Understanding SC 1.3.2 Meaningful Sequence

Last Modified on by 2 Comments

1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)

This success criterion requires that content presented on the page must be meaningful during navigation to all users. Users navigate content from left to right & assistive technology users such as screen reader users depend on the accessibility tree & DOM structure to let them know how the content is presented on the page. It is a best practice to match the DOM order & visual order. Writing clean HTML & then managing the design with CSS is the best way to preserve the meaning of content which is logical & intuitive.

Example That Fails This SC

Please use a screen reader to understand this example.

List of fruits

  • Cricket
  • Hockey
  • Chess

List of sports

  • Apple
  • Bananna
  • Orange

In the above example, “List of fruits” is visually followed by its related content & “List of sports” is followed by its content. But in reality this is not the case, if you observe the DOM “List of Fruits” is followed by content of “List of sports” & vice versa. Using CSS the reading order is changed visually but for an assistive technology user this content will be confusing & is not logical/intuitive. As a result the above content fails this checkpoint.

Points to Remember

  • Make sure that content presented on the page is logical & intuitive.
  • Write HTML first & then manage design with CSS.
  • Make sure visual order matches the DOM order.
  • Use headings, lists, paragraphs etc to mark your content.
  • Make sure your users can differentiate the navigation menus from main content.

The best way to check this success criterion is to invest in a screen reader like NVDA or by checking if content is making sense by disabling the style sheets.

Continue reading Understanding SC 1.3.2 Meaningful Sequence

Understanding SC 2.4.3 Focus Order

Last Modified on by Leave a Comment

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)

Intent of this Success Criterion

The intent of this Success Criterion is to ensure that when users navigate sequentially through content, they encounter information in an order that is consistent with the meaning of the content and can be operated from the keyboard. This helps the users to construct  a mental model of the content thereby reduces confusion.

Different logical orders

Based on the arrangement of the content, there may be different logical orders that would convey the relationships. For example, when traversing within a table, the order of elements could be determined either by column to column or row to row. One of these will pass this criterion but a mixture of this would fail.

Who benefits?

  • People with motor disabilities who use keyboard would need a logical and usable focus order

People who have reading disorders would need a logical focus order as if the focus jumps or is lost, they would be disoriented

  • People who are blind and who rely on screen reader and keyboard would benefit out of a logical order as if the focus jumps unexpectedly, they would be confused
  • People with low vision who rely on magnifiers would benefit out of this criterion as a logical order would prevent improper association of contents during magnification.

Examples

  1. In a login page, when the focus is forcefully set on the first field, then the subsequent tabs must take the users to the next form controls and then to the next section below or beside the form depending on the logical order of the page. The focus must not jump to the header after the last element of the form.
  2. When a modal opens:
    • The focus is set on the modal (first element)
    • The focus is trapped within the modal (cycles between the elements inside the modal)
    • The focus is returned to the element that triggered the modal
  • On a page with megamenu wit submenus:
  • The users encounter only one tab focus for the entire menu
  • The users use right/left arrow keys to navigate between main menus
  • The users use down/up arrow keys to expand/ a main menu and navigate down the submenus.

 

Points to ponder

  • Avoid using tabindex values that are >1 to manage focus order as they may supersede logical tab order
  • Align the focus order with the reading order as much as possible in order to maintain a logical and intuitive navigation of the content. Too much deviation would put a lot of users with disabilities into confusion

References

Understanding Success Criterion 2.4.3

Continue reading Understanding SC 2.4.3 Focus Order