Bobby Accessibility Summary Report

Bobby Approved status

These web pages do not contain any Priority 1 accessibility errors that Bobby can detect. However, certain items require human judgment; these are listed below. Please review these items; if none of these apply to your site, it qualifies for Bobby Approved status.

User checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby Approval requires that none of them apply to your site. Please review these 6 item(s):

Items sorted by priority

This section presents all items found for the pages tested. Items are grouped by the three priority levels assigned by the W3C: Priority 1 (high), Priority 2 (moderate), and Priority 3 (low). It may be most practical to address items in that order in so you can achieve baseline access as quickly as possible. Note that some items are not fully detectable by Bobby and may not be issues on your site; follow the link for each item for more information.

[Priority 1 (high)] If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship.
[Priority 1 (high)] Be sure pages are readable and usable if style sheets are ignored.
[Priority 1 (high)] If you use color to convey information, make sure the information is also represented another way.
[Priority 1 (high)] For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns.
[Priority 1 (high)] Provide alternative content for each SCRIPT that conveys important information or functionality.
[Priority 1 (high)] If an image conveys important information beyond what is its alternative text, provide an extended description.
[Priority 2 (moderate)] Check that the foreground and background colors contrast sufficiently with each other.
[Priority 2 (moderate)] If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening.
[Priority 2 (moderate)] Avoid using movement in images where possible.
[Priority 2 (moderate)] Avoid use of deprecated language features if possible.
[Priority 2 (moderate)] Avoid using tables to format text documents in columns unless the table can be linearized.
[Priority 2 (moderate)] Style sheets should be used to control layout and presentation wherever possible.
[Priority 2 (moderate)] Add a descriptive title to links when needed.
[Priority 2 (moderate)] Make sure event handlers do not require use of a mouse.
[Priority 2 (moderate)] Use relative sizing and positioning (% values) rather than absolute (pixels).
[Priority 3 (low)] Identify the language of the text.
[Priority 3 (low)] Provide abbreviations for long row or column labels.
[Priority 3 (low)] Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns.
[Priority 3 (low)] Provide a summary and caption for tables.
[Priority 3 (low)] Consider adding keyboard shortcuts to frequently used links.
[Priority 3 (low)] Specify a logical tab order among form controls, links and objects.

Items sorted by Ease to Fix

This section sorts items based on how easy it is to fix them. This is a subjective determination by CAST on these guidelines as a whole, not based on the analysis of your pages. Possible values are Easy, Moderate, or Hard.

[Easy] For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns.
[Easy] Avoid using movement in images where possible.
[Easy] Check that the foreground and background colors contrast sufficiently with each other.
[Easy] Provide abbreviations for long row or column labels.
[Easy] Add a descriptive title to links when needed.
[Moderate] If you use color to convey information, make sure the information is also represented another way.
[Moderate] Identify the language of the text.
[Moderate] If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening.
[Moderate] Consider adding keyboard shortcuts to frequently used links.
[Moderate] If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship.
[Moderate] Make sure event handlers do not require use of a mouse.
[Moderate] Provide alternative content for each SCRIPT that conveys important information or functionality.
[Moderate] Specify a logical tab order among form controls, links and objects.
[Moderate] If an image conveys important information beyond what is its alternative text, provide an extended description.
[Moderate] Be sure pages are readable and usable if style sheets are ignored.
[Moderate] Avoid use of deprecated language features if possible.
[Moderate] Use relative sizing and positioning (% values) rather than absolute (pixels).
[Moderate] Style sheets should be used to control layout and presentation wherever possible.
[Moderate] Provide a summary and caption for tables.
[Hard] Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns.
[Hard] Avoid using tables to format text documents in columns unless the table can be linearized.

Page index for each item

If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Be sure pages are readable and usable if style sheets are ignored.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

For tables not used for layout (for example, a spreadsheet), identify headers for the table rows and columns.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Make sure event handlers do not require use of a mouse.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Consider adding keyboard shortcuts to frequently used links.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

If scripts create pop-up windows or change the active window, ensure that the user is aware this is happening.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Check that the foreground and background colors contrast sufficiently with each other.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Add a descriptive title to links when needed.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Style sheets should be used to control layout and presentation wherever possible.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Provide a summary and caption for tables.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Provide abbreviations for long row or column labels.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Identify the language of the text.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Provide alternative content for each SCRIPT that conveys important information or functionality.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

If you use color to convey information, make sure the information is also represented another way.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

If an image conveys important information beyond what is its alternative text, provide an extended description.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Specify a logical tab order among form controls, links and objects.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Avoid using movement in images where possible.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Use relative sizing and positioning (% values) rather than absolute (pixels).

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Avoid using tables to format text documents in columns unless the table can be linearized.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html

Avoid use of deprecated language features if possible.

http://thunder.nsstc.nasa.gov/error/pagenotfound.html