Introduction

This document provides instructions on how to handle accessibility issues organized by priority. For more information, read Issue priority.

Navigation

1. Log in to your Web Governance account.
2. Select the domain that you want to work with.
3. Expand the left menu bar if the options are not visible.
4. Click Prioritized Pages.
5. Click the number in the Notifications column.
6. Click Accessibility in the mini window.

Landing page

• An Export button
• The
  Accessibility
  Compliance Level of your domain
• Tabs
  • All levels: Shows issues for all WCAG accessibility levels
  • Level A: Shows level A WCAG accessibility issues
  • Level AA: Shows level AA WCAG accessibiity issues
• Right panel: Displays in-depth information about the highlighted issue and possible actions you can take
  • Graduation cap icon
  • Tabs: Pending or Ignored
  • Ignore all issues
  • Ignore check
  • Mark check as fixed
  • Fast Track
  • Ignore
  • Mark as fixed

User actions

• Export: Click Export (a download icon) at the top of the page. For more information and full instructions, read How to do an Export.
• Tabs: Click a tab to display only the selected compliance level.
• Right panel: 
  • Graduation cap icon: Click to navigate to the Accessibility Guide article on the issue for instructions on how to fix it.
  • Tabs: Pending or Ignored: Select a tab to filter the results.
  • Ignore all issues: Click to ignore all instances of this issue. This option instructs the scan to ignore all instances of this issue.
  • Ignore check: Click to instruct the scan to ignore this check. Issues that fail this check are not flagged in the future.
  • Mark check as fixed: Click to mark the check as fixed. Use this option after you have fixed the issue in the HTML code everwhere that it occurs.
  • Fast Track: Click to navigate to the Fast Track view of this issue. For more information, read How to handle accessibility issues with Fast Track.
  • Ignore: Click to ignore this instance of this issue.
  • Mark as fixed: Click to mark this issue as fixed. Use this option after you have fixed this instance of the issue in the HTML code.

Handle accessibility issues with Prioritized Pages