Part 8, Chapter 20: Manual Exhibit 8-20-J

Text equivalent

(a.1)  Are ALT tags provided for every image?

(a.2)  Are ALT tags provided for every hotspot on an image map and the map as a whole?

(a.3)  Are ALT tags provided for every animated image?

(a.4)  Are ALT tags provided for every applet?

(a.5)  Are ALT tags provided for Programmatic objects?

(a.6)  Are null (alt="") ALT tags provided for Images used as list bullets?

(a.7)   Are null ALT tags provided for Images used as spacers?

(a.8)  Are ALT tags provided for every image-type button in forms?

(a.9)  Do audio files have transcripts?

(a.10)  Do video files have synchronized captions?

(a.11)  If flash is used does each user selectable element have an alternate tag?

(b.1)  If there is a video presentation on your web page, does the auditory, text equivalent (captioning) or other alternatives synchronize with the video?

(b.2)  Is the auditory or text equivalent descriptions accurate and adequate?

(b.3)  Is a link to any player or plug-in that is required to render multimedia provided?

(c.1)  Does the page avoid using color to convey information (e.g. Click on the red link to proceed.)?

(c.2)  Do images with text in them use contrasting colors so that the text is easily readable?

(d.1)  Can the page content be viewed without style sheets (e.g., does the content still appears)?

(d.2) Does the reading order of the page still make sense without style sheets?
To test:  Disable style sheets in your browser's preferences, and see if all the information is still available and in a logical order.

(e.1)  If possible, has the server-side image map been converted to a client-side image map?

(e.2)  If a server-side image map is used are redundant text links provided for every active region on the server-side image map?

(f.1)  Are client-side image maps being used instead of server-side except where the region(s) cannot be defined with an available geometric shape?

(f.2)  Is appropriate alternative text provided for images as well as each map hot spots?

(g.1)  Are all column and row headers identified using the th instead of the td tag in data tables?

(g.2) Is a unique id attribute associated with each th element and its corresponding td cells?

(g.3)  Is the scope or the headers and id attributes used for row and column header cells?

(g.4)  Does the text in the summary attribute accurately describe the related table data?

(g.5)  Is the th tag not used to achieve formatting (i.e., to bold text)?

(g.6)  Is the pre tag not used to create a tabular layout of text?

(g.7)  Are table header not used in decorative or layout tables?

(h.1)  Are data cells and header cells associated for data tables that have two or more logical levels of row or column headers?

(h.2)  Are all column and row headers identified using the th instead of the td tag in data tables?

(h.3)  Is a unique id attribute associated with each th element cell?

(h.4)  Is the scope or the headers and id attributes used for row and column header cells?

(h.5)  Does the text in the summary attribute accurately describe the related table data?

(h.6)  Is the th tag not used to achieve formatting (i.e., to bold text)?

(h.7)  Is the pre tag not used to create a tabular layout of text?

(h.8)  Are table header not used in decorative or layout tables?

Frames are not allowed on the ihs.gov domain.  (IHS & HHS requirement)

(j.1)  Does the page avoid using blinking text and/or images?

(j.2)  Does the page avoid using effects that cause the screen to "flicker" as pages are loaded?

(j.3)  Are screen items which flash, blink or flicker set at a rate of less than twice a second or more than 55 times a second?  (Hertz (Hz)is a cycle per second)

(k.1)  Reference the HHS 508 checklist below.

(k.2)  Are all pages accessible?

(l.1)  Is information provided by the script with functional text readable by assistive technology when pages utilize scripting languages to display content or to create interface elements?

(l.2)  Are accessible alternatives provided for scripts and applets that are inaccessible with assistive technologies (e.g. noscript tags)?

(m.1)  If a page uses plug-ins, applets, etc. is a link to that plug-in or applet provided to interpret the page content?
NOTE:  IHS approved plug-ins.

(m.2)  Does the plug-in or applet comply with the Section 508 standards listed in 1194.21(a) through (l)?
(Reference the IHS Section 508 36 CFR Part 1194.21 "Software Applications and Operating Systems Standards" checklist)

(n.1)  For all form controls implicitly associated with labels, are the labels properly positioned?

(n.2)  Can you navigate and follow links and forms with the keyboard?

(n.3)  Can the form be used with assistive technologies?

Is there a way to skip over a group of links (e.g. the header, page navigation, and footer)?

(p.1.)  Is the user alerted when a timed response is required and given sufficient time to indicate more time is required?

(p.2)  Does the page avoid automatic redirects, automatic refreshing, etc?

(1)  Document file name does not contain spaces or special characters and is no more than 20 characters.

(2)  Document properties for Author, Title, Company, Keywords, and Language are properly filled out.

(3)  Document has been formatted using style elements (proper headers, bullets, etc.).

(4)  All edits have been accepted, comments removed, and track changes and formatting marks turned OFF.

(5)  Color is not used to convey important information, e.g., "See red text below."

(6)  All images have alternative text descriptions (Images used only for decoration have null alt tags: alt="").

(7)  All charts and graphs have either an alternative text description or provide a description in the text immediately below the chart or graph.

(8)  All tables read from left to right, top to bottom, and provide a description immediately below the table.

(9)  All hyperlinks are active and use the full Web address, e.g., http://www.hhs.gov/Exit Disclaimer: You Are Leaving www.ihs.gov .

(10)  Document has been reviewed in Print Preview for a final visual check.

(1)  Document file name does not contain spaces or special characters and is no more than 20 characters.

(2)  Document properties for Title, Author, Keywords, and Language are properly filled out.

(3)  If the edit function of Acrobat was used, all Comment and Markup items must be deleted.

(4)  A visual check has been done to ensure no hidden data from Word or other applications used to create the original document is present.

(5)  All images and/or non-text elements have alternative text descriptions.

(6)  All charts and graphs have either an alternative text description or provide a description in the text immediately below the chart/graph.

(7)  Files of 10 pages or more have bookmarks.

(8)  Color is not used to convey important information, e.g., "See red text below."

(7)  Data tables identify row and column headers.

(8)  Data cells in tables are associated with row and column headers.

(9)  All tables read from left to right and top to bottom.

(10)  All hyperlinks are active and use the full Web address, e.g., http://www.hhs.gov/Exit Disclaimer: You Are Leaving www.ihs.gov  (not simply www.hhs.gov).

(11)  Pages with multi-column text, tables, or call-out boxes have been checked for correct reading order using the Acrobat Pro 'Read Aloud' function.

(12)  All needed accessibility tags have been added and a full Accessibility Report has been run in Adobe Acrobat Professional 8 or higher showing no errors are present.

(13)  A separate text-only version has been provided when there is no other way to make the content accessible.  (Example:  An organizational chart must have a text- only version.)

Notes:

1.  If content will be available as html, it is not required that the accompanying PDF file be 508 accessible.

2.  A PDF created by scanning a paper document in TIFF or another image format is not 508-compliant.  A text-only version must be provided.

3.  PDF forms require a specialized accessibility review because they present an additional degree of complexity.

(1)  Provide a one-sentence description of content to be used for the html file context.

(2)  Document file name does not contain spaces or special characters and is no more than 20 characters.

(3)  All video, animation, etc., files are captioned with captioning synchronized to the actions and dialogue.

(4)  All audio files have accompanying transcripts.

(5)  Graphics, animations, movies, or other objects avoid strobing, flickering, or flashing effects.

(6)  A text-only version is provided when there is no other way to make the content accessible.  (Example:  An animation must have a text equivalent.)

(1)  Document file name does not contain spaces or special characters and is no more than 20 characters.

(2)  If frames are used, each frame includes a title that describes the frame's purpose or content.

3)  Documents are readable without an associated style sheet.

(4)  All images and/or non-text elements have alternative text descriptions:

(4.1)  Alt tags should be limited in length

(4.2)  Longer descriptions should use the longdesc tag.

(4.3)  Images used only for decoration or spacing have null alt tags.

(5)  All charts and graphs have either an alternative text description or provide a description in the text immediately below the chart/graph.  Descriptions in the text must be referenced in the alt tag.

(6)  Image maps use appropriate alternative text and are rendered on the user-side.

(7)  Color is not used to convey important information, e.g., "See red text below."

(8)  Color contrast is sufficient and color combinations used are distinguishable to those with color-blindness.

(9)  Data tables identify row and column headers.

(10)  Data cells in tables are associated with row and column headers.

(11)  Graphics, animations, movies, or other objects avoid strobing, flickering, or flashing effects.

(12)  Scripts include text and keyboard access, and the Web page functions properly when the scripts are disabled.  (Examples:  images used in navigation scripts have alt tags and "onClick" commands are accompanied by "onkeypress.")

(13) When electronic forms are designed to be completed online:

(13.1)  Use the LABEL and ID elements when form controls are text input fields.

(13.2)  Make dynamic HTML scripting keyboard accessible.

(13.3)  Use Title attributes.

(13.4)  Include special instructions within FIELD labels.

(13. 5)  Create form fields in logical tab order.

(13.6)  Render buttons in HTML rather than as images.

(14)  A Skip Navigation link is provided with any repetitive navigation.

(15)  The user has control over the timing of content changes.

(16)  Font size is under user control.

(17)  All linked files are 508-compliant or a second link to an equivalent alternative HTML or text-only version is provided.

(18)  A link to a download is provided for all viewers, players, and plug-ins. (Example: Adobe Acrobat Reader, Windows Media Player, PowerPoint.)

(19)  File format and size of non-HTML linked files are provided.

(20)  A text-only version is provided when there is no other way to make the content accessible.  (Example:  A flow chart must have a text equivalent.)