Auditing your site for accessibility issues

Auditing your site for accessibility issues

Please review Manual checks when testing a website for accessibility for additional checking that should be performed..

Auditing with Compliance Sheriff

  1. Login to the server
  2. Create a scan
    1. Set the display name and base URL/Start Page
    2. Assign checkpoints
    3. Save the scan settings
  3. Run the scan
  4. Create a view
    1. Set the name and choose the scan
    2. Set your options
    3. Save the view
  5. Review the results
  6. Creating overrides for visual checks

Login to the server

Login to http://webaudit.temple.edu using your AccessNet credentials

If you don’t have access, contact your accessibility liaison, or submit a TUhelp ticket.

Create a scan

Click the Scan tab and click New

Click on Scans, then New to create a new Compliance Sherif Scan

Set the display name and base URL/Start Page

Set the display name (the name that will be displayed in the list of scans on the previous screen).  Then type in the base URL you want to scan.  By default everything after temple.edu/ will transfer to the ‘Start page’.

Set your base URL and indicate a Start page

It is strongly recommended that you scan template pages first, fix all the errors on the template pages before scanning your full site.  To scan the template pages add each one as a Start Page, and set the level to 0 so that it doesn’t crawl through your site.  The levels indicate how many levels of links it should crawl to check for accessibility issues. 

Add each of your template pages and set the level to 0 to scan your templates.

Assign checkpoints

Assign what types of checkpoints you want to scan.  Most times you’ll want to add the “Temple Web Standards – public facing web content” and maybe “Alt Text Quality Report”. 

Select the appropriate checkpoints

The choices for checkpoints are:

Alt Text Quality Report

One of the most common issues, particularly as sites are updated, is that Alt text is not added to images, or the alt-text is not of good quality.  This scan, like others, verifies that alt-text exists, and unlike other scans, checks the quality of it.  You may want to run this scan in addition to other scans.

Section 508 – use for checking vendor based content

Temple adheres to WCAG 2.0.  Vendors are only legally required to adhere to section 508.  Use this scan to check for 508 issues on a vendor hosted site, or a web application provided by a vendor.

Site Quality Checks

Use this to check for broken links, spelling errors (note: names often appear as spelling errors), and page load time.

Site Quality Checks – Link Validation (higher priority)

Use this to check for high priority broken links.

Site Quality Checks – Link Validation (lower priority)

Use this to check for lower priority broken links, such as broken bookmarks.

Temple University Accessibility Scan – Critical

Use this to check for critical accessibility issues that are "show stoppers" for individuals with disabilities.

Temple University Accessibility Scan – Severe

Use this to check for severe accessibility issues that are show stoppers for individuals with disabilities but will probably take you longer to fix.

Temple University Accessibility Scan – Important

Use this to check for important accessibility issues that are extremely important for individuals with disabilities.

Temple University Accessibility Scan – Moderate

Use this to check for moderate accessibility issues that need to be fixed.

Temple Web Standards – Authenticated web login (login required to view, i.e. Blackboard, TUPortal)

This scans for WCAG 2.0 AA compliance, with the exception of scanning for audio/video files.  These types of content might not need to be captioned or audio described, unless there is a request for it to be done.  Given that authentication is required, you may need to use a scripted scan.

Temple Web Standards – public facing web content

This scans for WCAG 2.0 AA compliance, including checking audio/video content for captions and audio descriptions.  Any publicly available video needs to be captioned.

 Save the scan settings

Once you’re done configuring you scan, save the settings

Save your scan settings

Run the scan

On the Scans tab click Run on the line for the scan you just created

Click on run to start your scan.

It may take several minutes for the scan to finish. 

Create a view

Click on the Views tab, and click New

Click on Views and then New

Set the name and choose the scan

Set the name and choose the scan you just created.  It is generally recommended that the name for the view include the name of the scan.  You may choose to create multiple views of the same scan (one which details the errors on a page by page basis, and based on checkpoint compliance.)

Enter a name and then select the scan you created above

Set your options

To view the issues page by page, choose table type “Page compliance”.  It’s also recommended that you view Visual checks as a fair number of compliance items require visual (manual) checks.

Set your view options as indicated above

Save the view

Click Save to save your new view

Review the results

Once your view has been saved and the scan has completed you can use the icons on the right to:

View your results

Preview the scan results

View a web page of the scan results

View a PDF of the scan results (note: the scan results can sometimes be fairly large, it may take a while before the PDF is created.)

 

Creating overrides for visual checks

The accessibility of some items can’t be checked by an automated scan (such as being able to access everything on the page via a keyboard only).  Items that require visual inspection will be denoted as "Visual Check."  These must be addressed in addition to the failed items.

 

 

Checkpoints starting with TU_###, and the description ends with "(with override.)"  Once you have visually inspected the page and verified that all of the items have been addressed and are not an issue, you can include <tu_###/> in the body of the page to have the checkpoint mark that page as passed.  For example, if your page is flagged for contrast issues (TU_G18), but you've verified there aren't any contrast issues on the page, add <tu_g18/> to the page and compliance sheriff will flag that page as a 'pass' for that particular checkpoint.