Accessibility

The Accessibility Check will check the page's HTML for any issues that conflict with accessibility standards. When run, Accessibility Check will show (at maximum) a list of known problems, likely problems, and potential problems. To view the list of problems, you can click the Show Results link under the Accessibility Check button.

Performing an Accessibility Check 

There are several ways to perform an Accessibility Check:

  1. Navigate to the Pages list view by selecting Content > Pages from the global navigation bar.
  2. Hover on the target page's row and select Page Check from the Review menu to display the Page Check modal. Additionally, selecting Publish from the Publish menu to display the Final Check modal will also provide the ability to perform an Accessibility Check.
  3. Click the Accessibility button to run the check. If desired, click Show Results once the check has completed to view results of the check.

You can also perform an Accessibility Check from the Page Actions toolbar:

  1. Navigate to the Pages list view by selecting Content > Pages from the global navigation bar and select the page to be edited. Additionally, selecting the page from the File Navigation sidebar also displays a view with the Page Actions toolbar included.
  2. Click the Page Check button in the Page Actions toolbar to display the Page Check modal. Additionally, clicking the Publish button displays the Final Check modal.
    Page check modal
  3. Click the Accessibility button to run the check. If desired, click Show Results once the check has completed to view results of the check.
    Page check modal Accessibility

Accessibility Check Results

When you click Show Results after an Accessibility Check has been performed, the Accessibility Check Results modal is displayed. This modal displays a list view of all known problems, as well as potential or likely issues. Each item displayed in the Accessibility Check Results modal includes reference to the exact line in which the errors are found, including the source code and an explanation of the problem.

Each problem will contain the exact location of the error in the source code, the name of the issue, a snippet of offending code, and a suggested repair. Clicking the error name will bring up a page containing more in-depth information.

  • Known Problems: Problems that have been verified as broken or creating an error. These problems are identified by the red icon next to each list item. If available, a helper message may appear with each list item, helping you identify a solution to repairing the problem.
  • Likely Problems: Items that the OU Campus system identifies as most likely being an error, but is required to be reviewed by a you to designate if the problem is real or not.
  • Potential Problems: Similar to Likely Problems in that they are not verified, but the system has identified code which may or may not cause errors and should be reviewed by you.

Note: You should focus on Known Problems since the others are often associated with styling of script code that is reviewed by Web Communications.