Accessibility Report Template

Use the checkboxes for tracking; mark off problems as you review and repair your pages.

Summary

Pages Checked: 1
Found 56 problems in 1 pages

Page About Us.htm

Found 56 Problems

Priority 1

WCAG 1.1

1. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 18
   
2. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 20
   
3. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 22
   
4. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 24
   
5. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 25
   
6. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 27
   
7. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 27
   
8. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 27
   
9. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
   Line 27
   
10. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
    Line 27
    
11. Error: Image is missing a text equivalent (either an alt="X" or longdesc="X"). Consider brief alternative text that describes the information that the image conveys. You can use the picture properties dialog to add alternative text.
    Line 27
    
12. Warning: Consider using <noscript> to provide an alternative description of <script> content.
    Line 5
    
13. Warning: Consider using <noscript> to provide an alternative description of <script> content.
    Line 12
    

WCAG 5.1

1. Warning: If this is a data table, please add header rows and/or columns using <th>.
   Line 14
   
2. Warning: If this is a data table, please add header rows and/or columns using <th>.
   Line 20
   

WCAG 5.2

1. Warning: If this is a complex data table containing two or more levels of header rows or columns, identify structural rows. Consider using <thead>, <tfoot> for repetitive headers and footers; <tbody> for grouping rows; <col> and <colgroup> for grouping columns; and label the TABLE elements with "scope", "axis", and "headers".
   Line 20
   

WCAG 6.1

1. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 15
   
2. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
3. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
4. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
5. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
6. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
7. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
8. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   
9. Warning: If you are using style sheets, verify that this document can be read with style sheets turned off.
   Line 20
   

WCAG 6.3

1. Warning: Be sure this page is usable when programmatic objects are turned off or not supported. If not, provide alternative text that describes the information that the element conveys.
   Line 5
   
2. Warning: Be sure this page is usable when programmatic objects are turned off or not supported. If not, provide alternative text that describes the information that the element conveys.
   Line 12
   

WCAG 8.1

1. Warning: Verify that programmatic elements are accessible using assistive technology.
   Line 5
   
2. Warning: Verify that programmatic elements are accessible using assistive technology.
   Line 12
   

Priority 2

WCAG 5.3

1. Warning: If this table is used for layout, make sure it makes sense when linearized. Otherwise, provide a linearized version or use cascading style sheets for structure and positioning.
   Line 14
   
2. Warning: If this table is used for layout, make sure it makes sense when linearized. Otherwise, provide a linearized version or use cascading style sheets for structure and positioning.
   Line 20
   

WCAG 5.4

1. Warning: If this table is used for layout, do not use a structural format for visual formatting. For example, do not use <th> to display cell contents as centered and bold.
   Line 14
   
2. Warning: If this table is used for layout, do not use a structural format for visual formatting. For example, do not use <th> to display cell contents as centered and bold.
   Line 20
   

WCAG 7.3

1. Warning: Avoid moving content or allow users to control the movement.
   Line 5
   
2. Warning: Avoid moving content or allow users to control the movement.
   Line 12
   

WCAG 9.2

1. Warning: Verify that any element with its own user interface is device-independent.
   Line 5
   
2. Warning: Verify that any element with its own user interface is device-independent.
   Line 12
   

WCAG 9.3

1. Warning: Be sure this event handler is device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown". Event handlers that rely on mouse coordinates prevent device indepedence and should not be used.
   Line 17
   
2. Warning: Be sure this event handler is device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown". Event handlers that rely on mouse coordinates prevent device indepedence and should not be used.
   Line 17
   
3. Warning: Be sure this event handler is device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown". Event handlers that rely on mouse coordinates prevent device indepedence and should not be used.
   Line 21
   
4. Warning: Be sure this event handler is device-independent. If use of this event handler is required for the essential information or use of this page: consider limiting event handlers to device indpendent handlers such as: "onfocus", "onblur" and "onselect". If you must use device-dependent attributes provide a keyboard alternate, for example for "onmousedown" also specify "onkeydown". Event handlers that rely on mouse coordinates prevent device indepedence and should not be used.
   Line 21
   

WCAG 11.2

1. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 14
   
2. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
3. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
4. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
5. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
6. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
7. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
8. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   
9. Warning: This line contains an element that is deprecated, which means that it might eventually be removed from official HTML specifications. It is recommended to avoid deprecated elements. Some examples of good substitutions are: Use <object> instead of <applet>; use <div> with the "align" attribute instead of <center>; use <ul> instead of <dir> or <menu>.
   Line 20
   

WCAG 12.3

1. Warning: Large blocks of information should be grouped so they are more manageable. If this is a large data table consider describing its content using <caption>.
   Line 14
   
2. Warning: Large blocks of information should be grouped so they are more manageable. If this is a large data table consider describing its content using <caption>.
   Line 20
   

Section 508

508, 1194.22(l)

1. Warning: If you use ;<script>, ;<object>, ;<embed> or ;<applet>, ensure that the important information conveyed by these is readable using assistive devices.
   Line 5
   
2. Warning: If you use ;<script>, ;<object>, ;<embed> or ;<applet>, ensure that the important information conveyed by these is readable using assistive devices.
   Line 12
   

508, 1194.22(m)

1. Warning: If this page requires an applet, plug-in or other application on the client in order to convey important information, be sure you provide a link to a fully accessible plug-in or applet.
   Line 5
   
2. Warning: If this page requires an applet, plug-in or other application on the client in order to convey important information, be sure you provide a link to a fully accessible plug-in or applet.
   Line 12
   

Manual Check

The following are a list of potential accessibility problems that cannot be detected by the checking tool. Please review your pages for any of the below problems.

Priority 1

If you use ASCII art, be sure to include alternate equivalent text, using <abbr> with the "title" attribute. Also provide a link to skip over the ASCII figure. (WCAG 1.1)

Synchronize alternatives, captions, or auditory descriptions with time-based multimedia tracks. (WCAG 1.4)

Be sure not to convey information using color alone. Use context or markup as well. (WCAG 2.1)

Identify language changes in the document. For instance, use "lang" or "xml:lang" to identify a language change. (WCAG 4.1)

Be sure that equivalents for dynamic content are updated whenever content is updated. (WCAG 6.2)

Avoid causing screen flicker. Where unavoidable, allow users to control flickering. Four to 59 flashes per second should be avoided as should quick changes from light to dark. (WCAG 7.1)

If you are unable to make an accessible page, create an alternative page that is accessible, provides the same utility and is updated as frequently as the inaccessible page. Note: this should be considered only as a "last resort". (WCAG 11.4)

Use the clearest and simplest language appropriate for this content. (WCAG 14.1)

Priority 2

Be sure that foreground and background colors for images provide sufficient contrast for low-vision users and for use with black and white screens. (WCAG 2.2)

Use markup rather than images to convey information where possible. Examples: use MathML to markup mathematical equations; use style sheets to format text and control layout. (WCAG 3.1)

Be sure to include a document type declaration. This will enable browsers and assistive devices to interpret your content correctly. (WCAG 3.2)

Be sure that you are using style sheets to control layout and presentation. (WCAG 3.3)

Consider using relative values rather than absolute values, for example use a percentage value rather than pixel value. (WCAG 3.4)

Be sure that dynamic content is accessible, or provide an alternative presentation. For example, if you use <frame>, include a <noframes> option; note also that server-side scripts may be more accessible than client-side scripts. (WCAG 6.5)

Do not create automatically refreshing pages. (WCAG 7.4)

Provide the ability to stop this redirect or configure the server to perform redirects. (WCAG 7.5)

Allow users to turn off spawned windows. Do not cause pop-ups. Do not change the current window without informing users. (WCAG 10.1)

Use the latest W3C technologies. For example, MathML for mathematical equations; HTML, XHTML, XML for structured documents; CSS and XSL to define style sheets; XSLT to create style transformations. (WCAG 11.1)

Web sites and pages should provide semantic information and orientation. Using good meta data can provide orientation information about the site to the user. Helpful tags: <title>, <address>, <meta>, <!doctype>, <link>. Use <ol>, <ul> and cascading style sheets to provide contextual clues in lists. Provide navigation bars, site maps and search features to assist as well. (WCAG 13.2)

Web sites and pages should provide layout information. Consider using site maps and tables of contents. (WCAG 13.3)

Use of navigation should be consistent throughout your Web site. For example, navigation should appear in the same location on all pages. (WCAG 13.4)

Section 508

Where navigation links are repeated, provide a method for the user to skip these repetitive links. (508, 1194.22(o))

If a time-based response is required of the user, provide an alert allowing the user to request more time. (508, 1194.22(p))