Comparison with Illinois Web Accessibility Standards 1.2 (& 1.8 Draft)

Comparison of Illinois Web Accessibility Standards and Best Practices Requirements

Functional Requirements	IWAS	Requirement Comparison
Standards
Support Web Standards	1.1	Same: Use valid, standard web programming code (1.1) Different: Does not specifically recommend avoidance of deprecated features.
Styling
Liquid Design for Content Reflow	2.1 2.2 17.3	Same: Avoid using images to display text (2.1) Same: Avoid using absolute sizes for fonts (2.2) Same: Minimize the need for horizontal scrolling (17.3)
Layout/Linearization	1.3 17.1 17.2	Same: Use style sheets for formatting whenever possible (1.3) Same: When using tables for layout, make sure that reading order is logical (17.1) Same: When using style sheets for layout, make sure that reading order is logical when style sheets are not supported (17.2)
Colors	3.1	Same: Do not convey information with color alone (3.1) Additional: Use contrasting foreground and background colors (3.2)
Fonts	1.3 2.1	Same: Use style sheets for formatting whenever possible (1.3) Same: Avoid using images to display text (2.1) Additional: Avoid using absolute sizes for fonts (2.2)
Navigation and Orientation
Unique Titles	1.4 (new)	Same: Provide meaningful page titles (1.4, new)
Headings	1.2 1.5 (new)	Same: Use appropriate markup to convey document structure (1.2) Same: Use headings to introduce sections and sub-sections, and use them in the correct order (1.5, new)
Menus and Navigation Bars	1.6 (new) 9.2	Same: Use lists to identify series of related items, including navigation menus (1.6, new) Same: Provide a means of skipping past repetitive navigation links (9.2) Different: Does not specifically recommend use of title attribute on lists
Forms	10.1 10.5 (new) 10.6 (new)	Same: Associate labels with all form fields (10.1) Same: When you can't use label, use title (10.5, new) Same: For groups of fields, use fieldsets, titles, or selects (10.6) Different: Does not recommend associating labels by "encapsulating" fields in label tags (note: this technique breaks the "click label to activate field" ability in Internet Explorer); recommends explicit association using the "for" attribute. Different: Does not specifically recommend use of tabindex to put non-form elements in the tab order (note: this technique is not valid HTML). Different: Does not recommend use of hidden labels on form fields in tables; recommends use of title attribute instead (10.5) Additional: Position labels as close as possible to form fields (10.2) Additional: Ensure that form instructions are readable (10.3) Additional: Make sure that form fields are in a logical tab order (10.4) Additional: Avoid using disabled fields (10.7, new) Additional: Ensure that text in form fields can be enlarged (10.8, new)
Language	2.3	Same: Specify the language of text (2.3)
Tabular Data Tables	11.1 11.3 (new) 11.4 (new)	Same: For simple data tables, identify headers for all columns and rows (11.1) Same: Mark up complex tables using id and headers (11.3, new) Same: Include a caption and/or summary for data tables (11.4, new) Different: Does not explicitly require captions (note: 508 comparison indicates that "Section 508 requires the caption element must be used", but it does not.) Additional: Simplify complex tables when possible (11.2)
Lists	1.2 1.6 (new)	Same: Use appropriate markup to convey document structure (1.2) Same: Use lists to identify series of related items, including navigation menus (1.6)
Links	9.1	Same: Make sure that links are understandable out of context (9.1) Different: Does not require redundant text links for client-side image maps; recommends provision of alternate text for each area in client-side image maps instead (5.1) Different: Does not require redundant text links for server-side image maps; recommends avoidance of server-side image maps instead (5.2) Additional: Avoid using small links (9.3) Additional: Do not rely on title attributes on links (9.4, new) Additional: Ensure that same-page links move keyboard focus as well as screen focus (9.6, new)
Accesskeys	9.5 (new)	Same: Provide keyboard shortcuts to important links and form fields that are used throughout a site (9.5, new)
Frames	12.1	Same: Provide meaningful names and page titles for all frames (12.1) Different: Does not specifically recommend avoidance of frames Additional: Avoid using empty, hidden, or non-essential frames (12.2)
Automation
Scripting	13.1 13.2 16.1	Same: Make sure that significant interactions can be performed with both keyboard and mouse (13.1) Same: Make sure that essential content and functionality are available when client-side scripts are not fully supported (13.2) Similar: Notify users of actions that will open a new window (16.1) Different: Does not prohibit opening of new windows. Additional: Avoid changing content at or above the user's focus (13.3, new) Additional: Avoid changing content or focus unexpectedly. (13.4, new) Additional: Use standard DOM techniques when creating or changing content. (13.5, new)
Keyboard	13.1	Same: Make sure that significant interactions can be performed with both keyboard and mouse (13.1)
Objects and Applets	14.1 14.2	Same: Use accessible applets or plug-ins whenever possible (14.1) Same: If an inaccessible applet or plut-in must be used, provide an accessible alternative that includes the same content and functionality (14.2) Different: Does not specifically require option to view audio and/or video in external media player.
Animations (Flicker)	8.1	Same: Avoid, flickering, blinking, and unnecessary animation (8.1)
Timed Responses	16.3	Same: Notify users of time limits and provide a means to extend time if needed (16.3)
Text Descriptions
Text Equivalents for Images, Pictures, Charts and Diagrams	4.1 4.2	Same: Provide "alternate text" for all images (4.1) Same: Provide full descriptions for graphs, diagrams, and other meaningful images (4.2) Additional: Provide alternate text for each area in client-side image maps (5.1)
Text Equivalents for Audio	6.1 6.2 7.1	Same: Do not convey information with sound alone (6.1) Same: Provide text transcripts for audio containing speech (6.2) Same: Provide synchronized captions for multimedia containing speech (7.1)
Non-W3C Technologies
Microsoft Office Documents	15.1	Similar: Provide accessible HTML or text versions of downloadable documents whenever possible (15.1)
Adobe PDF Documents	15.1	Similar: Provide accessible HTML or text versions of downloadable documents whenever possible (15.1)
Macromedia Flash	14.1 14.2	Similar: Use accessible applets or plug-ins whenever possible (14.1) Similar: If an inaccessible applet or plug-in must be used, provide an accessible alternative that includes the same content and functionality (14.2)

New/Modified IWAS Guidelines Added to Improve Alignment with Best Practices

• 1.4 (new) - Provide meaningful page titles.
• 1.5 (new) - Use headings to introduce sections, sub-sections, and use them in the correct order.
• 1.6 (new) - Use lists to identify series of related items, including navigation menus.
• 9.5 (new) - Provide keyboard shortcuts to important links and form fields that are used throughout a site.
• 10.5 (new) - When you can't use label, use title.
• 10.6 (new) - For groups of fields, use fieldsets, titles, or selects.
• 11.3 (new) - Mark-up complex tables using id and headers.
• 11.4 (new) - Include a caption and/or summary for data tables.

IWAS Guidelines Not Specifically Addressed in Best Practices

• 1.7 (new) - Identify abbreviations and acronyms.
• 2.4 - Avoid using "ASCII art."
• 3.2 - Use contrasting foreground and background colors.
• 5.1 - Provide alternate text for each area in client-side image maps.
• 5.2 - Avoid using server-side image maps.
• 7.2 - Provide audio descriptions for multimedia with significant video.
• 9.3 - Avoid using small images or text as links.
• 9.4 - Do not rely on title attributes on links.
• 9.6 - Ensure that same-page links move keyboard focus as well as screen focus.
• 10.2 - Position labels as close as possible to form fields.
• 10.3 - Ensure that form field instructions are readable.
• 10.4 - Make sure that form fields are in a logical tab order.
• 10.7 (new) - Avoid using disabled fields.
• 10.8 (new) - Ensure that text in form fields can be enlarged.
• 11.2 - Simplify complex data tables when possible.
• 12.2 - Avoid using hidden, empty, or non-essential frames.
• 13.3 (new) - Avoid changing content at or above the user's focus.
• 13.4 (new) - Avoid changing content or focus unexpectedly.
• 13.5 (new) - Use standard DOM techniques when creating or changing content.
• 15.2 - If a downloadable document cannot be provided in an accessible electronic format, provide information on how to request an alternate format.
• 16.2 - Do not automatically refresh the current page.
• 18.1 - Use the clearest, simplest, and most concise language appropriate for a page's subject matter.
• 19.1 - Use separate accessible versions only as a last resort.
• 20.1 - Provide contact information.
• 21.1 - Test for accessibility.