WCAG Operable:2.1 - Keyboard operation and navigation - Result 2. Page areas are not efficiently skippable

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Finding from the audit attached to Epic -this may have been done by the previous accessibility work, please confirm:

      • In addition to headings, side areas offer a possibility for structural navigation
      • If not all areas of the application are semantically marked as such, they cannot be accessed directly by screen reader or keyboard users (via browser add-on)
      • The breadcrumb and the sidebar are to be marked as navigation areas with the element.
      • To distinguish between the two navigation areas, a meaningful aria label must be assigned, which makes it clear which navigation area is involved. The main content area is to be marked with the element.

            Assignee:
            Unassigned
            Reporter:
            Cristina Pizzagalli
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: