Comparison Table

UMN	Section 508	W3C
1.1 Introductory Screens — The initial screen-view of a Web page shall contain some text that describes the affiliation and purpose of the page.	No Standard	No Standard
1.2 Design Consistency — Use a consistent look and navigational scheme for all pages of a site. A method shall be provided that permits users to skip repetitive navigation controls and jump to the main content of a page.	(o) A method shall be provided that permits users to skip repetitive navigation links.	(Priority 2) 13.4 Use navigation mechanisms in a consistent manner. (Priority 3) 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. (Priority 3) 14.3 Create a style of presentation that is consistent across pages.
1.3 Document Length — Present large documents in smaller sub-units where natural and appropriate. Offer complete full-length versions for download.	No Standard	(Priority 2) 12.3 Divide large blocks of information into more manageable groups where natural and appropriate.
1.4 Frames — Avoid the use of frames. Frames shall be titled with text that facilitates frame identification and navigation. Use the HTML <noframes> element to point to an alternate page that does not use frames.	(i) Frames shall be titled with text that facilitates frame identification and navigation.	(Priority 1) 12.1 Title each frame to facilitate frame identification and navigation.
1.5 Browser Specific HTML Tags — Do not use HTML constructs (tags) that are specific to (and only supported by) one browser. Use current HTML version specifications.	No Standard	(Priority 2) 3.2 Create documents that validate to published formal grammars.
1.6 Cascading Style Sheets — Documents shall be organized so they are readable without requiring an associated style sheet.	(d) Documents shall be organized so they are readable without requiring an associated style sheet.	(Priority 1) 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
1.7 Scripts — Ensure that pages are usable when scripts, applets, or other programmatic objects are not supported or have been disabled. Provide equivalent information and/or functionality on an alternative accessible page, when direct access cannot be achieved.	(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.	(Priority 1) 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2) 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
2.1 Roll-over Controls — Do not use roll-over controls that LOAD A NEW PAGE OR OTHERWISE move the user from the current location. Avoid the use of THE "onChange" EVENT-HANDLER in a drop-down list. Include text descriptions and redundant links for pop-up information and menus.	No Standard	(Priority 2) 10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. (Priority 2) 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers.
2.2 Screen Refresh — Avoid the automatic refreshing of a page. A method for disabling the automatic refreshing of a page must be provided.	(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.	(Priority 2) 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
2.3 Timed Responses — Alert users when a timed response is required and provide one or more of the following options: A method for indicating that more time is needed. A method for the user to adjust the time interval. A non-time dependent alternative.	(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.	No Standard
3.1 Font (Face, Size and Color) — Do not use font face, size or color alone to convey information. Specify font sizes in relative rather than absolute units.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.	(Priority 1) 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. (Priority 2) 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.
3.2 Backgrounds and wallpaper — Do not use complex backgrounds or wallpaper that may interfere with the readability of overlying text. Do not use backgrounds or wallpaper to convey information.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.	(Priority 2 for images, Priority 3 for text) 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen.
3.3 Blinking Page Elements and Marquees — Avoid the use of blinking page elements and scrolling marquees. Blinking page elements and the refreshing of the screen to animate marquees shall do so at a frequency of less than twice a second (2 Hz) or greater than 55 times a second (55 Hz).	(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.	(Priority 1) 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. (Priority 2) 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).
3.4 Acronyms and Abbreviations — The first occurrence of an acronym on a page must be preceded by the full title to which the acronym refers. Avoid the use of acronyms and abbreviations in link text. Do not use acronyms and abbreviations in the alternative text for Images or other non-text elements.	No Standard	(Priority 3) 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs.
3.5 Bullets — Provide appropriate alternative text for graphical bullets. Use simple alternative text for graphical bullets — an asterisk (*), a single letter (A) or single number(1). Unless required to convey information visually depicted by a bullet, avoid alternative text that describes the bullet (e.g., "This is a small black ball").	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
3.6 List Tags — When bullets created using the <ul> list tag are important for comprehension of the document or numbered bullets created using the <ol> list tag are to be referenced elsewhere in the document, include additional mark-up that promotes accessibility.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).	(Priority 2) 3.6 Mark up lists and list items properly.
3.7 Heading Tags — Heading tags shall be used to convey structural information about an HTML document. Heading tags shall not be used to manipulate font size or other text attributes.	No Standard	(Priority 2) 3.5 Use header elements to convey document structure and use them according to specification.
4.1 Multiple Column Layout — Avoid the use of multiple-column layouts for non-tabular information. Do not use the <PRE> tag (preformatted) to layout tabular information. Include Row and column headers for data tables. Ensure that information in a multi-column format, whether static or dynamically generated, is accessible or provide an alternative means of acquiring the information.	(g) Row and column headers shall be identified for data tables. (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.	(Priority 1) 5.1 For data tables, identify row and column headers. (Priority 1) 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. (Priority 1) 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. (Priority 1) 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (Priority 2) 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. (Priority 2) 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). (Priority 3) 5.5 Provide summaries for tables. (Priority 3) 10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.
5.1 Alt Tags — Include alternative text for all graphics. Do not use acronyms and abbreviations in the alternative text for Images or other non-text elements.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
5.2 Non-link Graphics — Alternative text for images that convey information or otherwise contribute to the understanding of the page shall be clear, concise and informative. Where appropriate, use the alternative text for transparent graphics and other structural images to provide a description of subsequent information and controls on the page.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
5.3 Complex Images, Tables, and Charts — Provide accessible text descriptions for complex images, such as graphical tables and charts.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
5.4 Animations — Include alternative text for all animations. Alternative text for animations shall be clear, concise and informative. If an animation uses audio to convey information, a text equivalent of the audio portion shall be provided.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 1) 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (Priority 1) 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
6.1 Text Links — Avoid the use of single word links. Links shall be clear, descriptive and able to stand alone. Preference shall be given to vertical lists of well-spaced text links. Links listed horizontally or in a multiple column layout shall be visually distinct and separated by appropriate punctuation or graphics. Avoid enclosing text links in brackets, braces, parentheses or other punctuation.	No Standard	(Priority 2) 13.1 Clearly identify the target of each link. (Priority 3) 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
6.2 Mailto Links — Include the E-mail address in the text of a mailto link.	No Standard	No Standard
6.3 Graphical Links — Include clear, concise and informative alternative text for all non-text controls. Use buttons and icons that are 36pt by 36pt or larger.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 2) 13.1 Clearly identify the target of each link.
6.4 Image Maps — Include clear, concise and informative alternative text for each region of a client-side image map. Avoid the use of server-side image maps. Include alternative links for each active region of a server-side image map.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (e) Redundant text links shall be provided for each active region of a server-side image map. (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 1) 1.2 Provide redundant text links for each active region of a server-side image map. (Priority 1) 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. (Priority 2) 13.1 Clearly identify the target of each link. (Priority 3) 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map.
7.1 Forms — Do not use font styles, sizes, colors or other non-textual elements as the only means of indicating required fields. Indicate alternatives to completing online forms.	(g) Row and column headers shall be identified for data tables. (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.	(Priority 2) 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. (Priority 2) 12.4 Associate labels explicitly with their controls.
8.1 Multimedia — Multimedia presentations shall be accompanied by text and/or audio descriptions of visual content. Audio presentations shall be accompanied by text captioning. The equivalent accessible alternatives for a multimedia presentation (e.g., text captioning and/or audio description) shall be synchronized with the presentation. A link to the plug-in or applet required for a multimedia presentation shall be provided.	(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).	(Priority 1) 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 1) 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. (Priority 1) 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. (Priority 1) 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
9.1 File Formats, Applets, and Downloads — Include the following options for information presented in a proprietary file format: The information in an alternative accessible format. A link to the appropriate plug-in. A link to an accessibility plug-in or conversion site, if available. An alternative means of obtaining the information. When feasible, information to be down-loaded shall be made available in a variety of file types.	(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).	(Priority 1) 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. (Priority 3) 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.).
No Standard	No Standard	(Priority 1) 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
No Standard	No Standard	(Priority 1) 14.1 Use the clearest and simplest language appropriate for a site's content.
No Standard	(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.	(Priority 1) 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
No Standard	No Standard	(Priority 2) 3.1 When an appropriate markup language exists, use markup rather than images to convey information.
No Standard	No Standard	(Priority 2) 3.3 Use style sheets to control layout and presentation.
No Standard	No Standard	(Priority 2) 3.5 Use header elements to convey document structure and use them according to specification.
No Standard	No Standard	(Priority 2) 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
No Standard	No Standard	(Priority 2) 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
No Standard	No Standard	(Priority 2) 11.2 Avoid deprecated features of W3C technologies.
No Standard	No Standard	(Priority 2) 13.2 Provide metadata to add semantic information to pages and sites.
No Standard	No Standard	(Priority 2) 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
No Standard	No Standard	(Priority 2) 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.
No Standard	No Standard	(Priority 2) 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
No Standard	No Standard	(Priority 2) 6.4 For scripts and applets, ensure that event handlers are input device-independent.
No Standard	No Standard	(Priority 2) 7.3 Until user agents allow users to freeze moving content, avoid movement in pages.
No Standard	No Standard	(Priority 2) 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.
No Standard	No Standard	(Priority 2) 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner.
No Standard	No Standard	(Priority 3) 4.3 Identify the primary natural language of a document.
No Standard	No Standard	(Priority 3) 9.4 Create a logical tab order through links, form controls, and objects.
No Standard	No Standard	(Priority 3) 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.
No Standard	No Standard	(Priority 3) 13.5 Provide navigation bars to highlight and give access to the navigation mechanism.
No Standard	No Standard	(Priority 3) 13.7 If search functions are provided, enable different types of searches for different skill levels and preferences.
No Standard	No Standard	(Priority 3) 13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc.
No Standard	No Standard	(Priority 3) 13.9 Provide information about document collections (i.e., documents comprising multiple pages.).
No Standard	No Standard	(Priority 3) 13.10 Provide a means to skip over multi-line ASCII art.
No Standard	No Standard	(Priority 3) 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
No Standard	No Standard	(Priority 3) 5.6 Provide abbreviations for header labels.
No Standard	No Standard	(Priority 3) 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.