The University of Texas at Austin

Accessibility Scanning and Assessments

Scanning Standard used in WorldSpace and FireEyes

In compliance with state and federal law, WorldSpace is configured to use the Section 508 and Quality standards below.

Additionally, we have created custom rules to help Web Publishers and Developers comply with university Web Publishing Guidelines; also listed below.

Quality Rules

  • Quality Rules
    • Check for broken links
    • Check for spelling
  • UT Austin Custom Rules
    • Home Page Link Check
    • Web Privacy Policy Link Check
    • Web Accessibility Policy Link Check

Accessibility Rules

  • PDF - Analyze PDF Content
  • Paragraph A - Equivalent alternatives for non-text elements
    • Check SCRIPT elements for valid equivalents where necessary (Report once per page)
    • Check INPUT elements of type="image" for valid "alt" attribute
    • Check OBJECT for text equivalents
    • Check applet elements for valid html equivalent (H35)
    • Check area elements for valid alt attribute (H24)
    • Verify text equivalents exist for linked / embedded audio files (H46)
    • Verify that text equivalents are provided for ASCIIArt, emoticons and leetspeak (H86)
    • Ensure that active image links have an alt
    • Ensure that formatting images have an alt
    • Ensure that image alt texts are valid
    • Ensure that image alt texts inside lists are not redundant with the announcements made by the AT
    • Ensure that images have an alt attribute
    • Ensure that informational images have an alt
    • Verify that valid img element long descriptions are provided for complex images larger than your specified threshold in height and width (H45)
    • Verify auditory description for the visual track of multimedia exists (G78)
  • Paragraph B - synchronized and equivalent alternatives for multimedia
    • Check SMIL files for synchronized media flag (SM11, SM12)
    • Check WebVTT or TTML files for synchronized media
    • Verify that multimedia content has synchronized equivalents (G93)
  • Paragraph C
    • Use HTML structure to determine color usage
    • Check if foreground and background colors provide sufficient contrast
  • Paragraph E - Redundant text links for each active region of a server side image map
  • Paragraph F - Detect server-side image maps and convert to client-side image maps
  • Paragraph G - Check for missing row and column headers for data tables (H43, H51, H63)
  • Paragraph I - Check if frame titles are used to facilitate frame identification and navigation (H64)
  • Paragraph J - Screen Flicker in range of 2 - 55 Hz
  • Paragraph L - Check SCRIPT elements for valid equivalents where necessary (Report once per page)
  • Paragraph M - Check if programmatic elements are directly accessible and required plug-ins are available
  • Paragraph N - Electronic Forms
    • Check for "accesskey" attribute
    • Check for valid default values for SELECT elements
    • Check to see if instructions and cues exist in the form
    • Detect change in page context with no indication
    • Check that each fieldset has a legend element that includes a valid (non-empty and non-blank) description (H71)
    • Identify forms elements that need to be grouped (H71)
    • Check for explicit label association with form controls (H44, H65)

Last updated October 30, 2014 @ 9:33 am

We Can Help

Get help from an expert:

* ITS Help and Service Desk

* Call us at 512-475-9400

* Submit a help request online

We also have a walk-in service in the first floor lobby of the Flawn Academic Center (FAC). Stop by and let us help you!