RampWEB

Section 508 Testing Roadmap

NOTE: The purpose of the toolbar is to provide a tool that can assist you in the manual process of checking for Federal Section 508 compliance of Web sites and Web applications. This tool is not meant to certify or guarantee compliance but simply to help you in the evaluation process. Learn more about RampWEB's Section 508 compliance certification.

Testing Process

Template Pages

Most sites today are based on one or more template pages. These template pages defined the look and feel, navigation structure, and general layout of the pages. By making sure that these pages are Section 508 compliant, you are more than half way there to ensuring your site is web accessible.

Validate

  • Does your HTML code and CSS validate?
    Use the W3C validators located under the validate menu.
  • Is the correct spelling used?
    Correct spelling is necessary for talking browsers, screen readers, and any other reading device used to voice the content of the page. Test for correct spelling using the W3C spell checker under the validate menu.

Section 508 Tests

  • Is the page readable without the stylesheet?
    Text only browsers, PDA devices, and other limited devices may not use the stylesheets. Ensure that the page is in the correct reading order and that all information is still available.
  • What does the page look like in grayscale? Is all the information still available?
    If color was used on the page that presents information and is not just for visual effect, then it may be missing information if only viewed in grayscale. For example , if red was used to show required fields, then the page will no longer show that information and we have an accessibility problem. Also you will need to verify that there is sufficient contrast between the colors used in background and foreground colors to ensure readability. Use the toolbar to show the page in greyscale and verify that all the information is readable and that color is not important on the page.
  • What is the reading order of the page?
    Does it make sense, if you were not looking at it but instead listening to it linearly?
  • Is there sufficient color difference/contrast ratio between the colors chosen on the page?
  • If you resize the browser, does the page rescale? What if you magnify the page, is the content still readable? What if you are looking at it in a text-only browser?
  • Is there ways to skip over navigational items?
  • Do all images have an alternative text defined?

Page Information

  • Is the doctype defined?
  • For the site audience is the download speed acceptable?

Internationalization

  • Based on the current target audience is the page readable?
  • Has the language been specified?

Every Page

Validate

  • Does your code validate?
  • Is the correct spelling used?
  • Are all links correct?

Section 508 Tests

  • What does the page look like in grayscale? Is all the information still available? For example, if red was used to show required fields, then the page will no longer show that information and we have an accessibility problem.
  • Is there sufficient color difference/contrast ratio between the colors chosen on the page or within the images?
  • Is there ways to skip over navigational items?
  • Are all HTML elements marked up with the appropriate semantic markup?
  • Do all images have an alternative text defined?
  • Are the data table headers defined?
  • Do the forms have the appropriate labels defined?
  • Are all scripts keyboard accessible?
  • Are the applets and plug-ins accessible? Is there a link to the the accessible version of the viewer or player?
  • Are frames are used, are they accessible?

Internationalization

  • Based on the current target audience is the page readable?
  • Has the language of the document been specified?
  • If there are changes in language on the page, has the language been specified?