Integrating methods for users to skip repetitive navigation

Section 508 and WCAG require that long lists of navigation components must be able to be skipped by users depending on screen readers. This is so the user is not forced to listen to the announcement of navigation components on every page that is displayed.

There are a number of ways to achieve this within your titles. You can:

The first of these options is the preferred method, and is used widely within accessible content. Users of screen readers should be accustomed to accessing information in this way. Use the following steps to implement this solution:

  1. Create a button, hyperlink or other clickable object and ensure it is the first object that will be announced to the user on every page he/she visits. Consider using a transparent button. Since this functionality is meant entirely for users relying on screen readers, an invisible button will be hidden from view for users that are not relying on screen readers.

  2. Ensure the object you created in step 1 has an appropriate ALT tag. Examples of labels that are typically used for this kind of functionality are Skip to Main and Skip to Content.

  3. Add an additional object to the pages of your title that is announced just before the main content on each page, but after navigation components would typically be announced. This again requires careful object ordering in the Title Explorer.

    See also: Using the Title Explorer to configure object layering and reading order

  4. Configure the action on the object you created in step 1 with the following:

    On:

    Mouse Click

    Action:

    Go To

    Target:

    Current Page

    Scroll To

    <select the object created in step 3>

See also: Adding an action

Knowledge Base | Training | Support
© Copyright eLearning Brothers 2021