Download Quick reference guide for HiSoftware ()

Quick Reference Guide for HiSoftware
To audit websites for ADA compliance, go to http://webaudit.temple.edu (if you don’t have access,
have your Active Directory administrator contact Paul Paire.)
If you need to access the server from home, or from a WiFi network, please login to
http://cherryvpn.temple.edu first.
Scan settings
The following checkpoints are available when you create/edit a scan:
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 publically available video needs to be captioned.
Viewing Reports
Most people like to fix the issues page by page. (Note: visual checks need to be addressed too.)
Visual Checkpoints
To achieve WCAG 2.0 AA compliance, not everything can be checked by an automated scan (such as can
you 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.
Contrast
To manually check the contrast of items on a page, it is recommended you use one of the following
tools:


Juicy Studios Accessibility Toolbar (for Firefox)
The Paciello Group's Colour Contrast Analyser
Overrides
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.
Best Practices
Scan the pages that act as templates for your site (scan level 0), for example:
Fix all the errors and warnings you receive via a template scan, and then modify the scan to include a
small subset (change it to scan level 1 or 2) of the linked pages. Fix those issues, and eventually widen
the net to encompass your entire site.
Scanning your entire site without fixing the templates can result in an overwhelming number of failures,
warnings, and visual checks.