From Mobile Web Best Practices 1.0
to Web Content Accessibility Guidelines 1.0

Nothing: content already complies with these checkpoints:

• 1.1 (Priority 1) Provide a text equivalent for every non-text element (e.g., via “alt”, “longdesc”, or in element content)…, covered by NON-TEXT_ALTERNATIVES and possibly covered by IMAGE_MAPS.
• 2.1 (Priority 1) Ensure that all information conveyed with color is also available without color, for example from context or markup, covered by USE_OF_COLOR.
• 6.1 (Priority 1) Organize documents so they may be read without style sheets, covered by STYLE_SHEETS_SUPPORT and partially covered by FONTS.
• 6.3  (Priority 1) Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported…, covered by OBJECTS_OR_SCRIPT.
• 3.2 (Priority 2) Create documents that validate to published formal grammars, covered by VALID_MARKUP.
• 3.3 (Priority 2) Use style sheets to control layout and presentation, covered by STYLE_SHEETS_USE.
• 3.4 (Priority 2) Use relative rather than absolute units in markup language attribute values and style sheet property values, covered by MEASURES.
• 3.5 (Priority 2) Use header elements to convey document structure and use them according to specification, covered by STRUCTURE.
• 7.5 (Priority 2) 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, covered by REDIRECTION.
• 10.1 (Priority 2) 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, covered by POP_UPS.
• 12.4 (Priority 2) Associate labels explicitly with their controls, covered by CONTROL_LABELLING.
• 13.4 (Priority 2) Use navigation mechanisms in a consistent manner, covered by NAVIGATION.
• 9.4 (Priority 3) Create a logical tab order through links, form controls, and objects, covered by TAB_ORDER.
• 9.5 (Priority 3) Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls, covered by ACCESS_KEYS, possibly partially covered by IMAGE_MAPS and possibly partially covered by MINIMIZE_KEYSTROKES.
• 10.4 (Priority 3) Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas, covered by PROVIDE_DEFAULTS.
• 13.8 (Priority 3) Place distinguishing information at the beginning of headings, paragraphs, lists, etc., covered by CLARITY.

Something: more effort of some kind or a check, to comply with these checkpoints:

• 1.2 (Priority 1) Provide redundant text links for each active region of a server-side image map, partially covered by NON-TEXT_ALTERNATIVES and possibly covered by IMAGE_MAPS.
• 5.1 (Priority 1) For data tables, identify row and column headers, possibly covered by TABLES_SUPPORT and TABLES_ALTERNATIVES.
• 5.2 (Priority 1) For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells, possibly covered by TABLES_SUPPORT, TABLES_NESTED and TABLES_ALTERNATIVES.
• 6.2 (Priority 1) Ensure that equivalents for dynamic content are updated when the dynamic content changes, possibly partially covered by OBJECTS_OR_SCRIPT.
• 9.1 (Priority 1) Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape, possibly covered by IMAGE_MAPS.
• 12.1 (Priority 1) Title each frame to facilitate frame identification and navigation, possibly covered by NO_FRAMES.
• 14.1 (Priority 1) Use the clearest and simplest language appropriate for a site's content, partially covered by CLARITY.
• 2.2 (Priority 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 (for images), partially covered by COLOR_CONTRAST and BACKGROUND_IMAGE_READABILITY.
• 3.1 (Priority 2) When an appropriate markup language exists, use markup rather than images to convey information, possibly partially covered by NON-TEXT_ALTERNATIVES and GRAPHICS_FOR_SPACING.
• 5.3 (Priority 2) Do not use tables for layout unless the table makes sense when linearized, possibly covered by TABLES_LAYOUT, TABLES_SUPPORT and TABLES_ALTERNATIVES.
• 5.4 (Priority 2) If a table is used for layout, do not use any structural markup for the purpose of visual formatting possibly covered by TABLES_LAYOUT, TABLES_SUPPORT and TABLES_ALTERNATIVES.
• 7.4 (Priority 2) Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages, possibly covered by AUTO_REFRESH.
• 10.2 (Priority 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, partially covered by CONTROL_POSITION.
• 11.1 (Priority 2) Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported, possibly partially covered by VALID_MARKUP.
• 11.2 (Priority 2) Avoid deprecated features of W3C technologies possibly partially covered by VALID_MARKUP and partially covered by FONTS.
• 12.2 (Priority 2) Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone, possibly covered by NO_FRAMES.
• 12.3 (Priority 2) Divide large blocks of information into more manageable groups where natural and appropriate, partially covered by PAGE_SIZE_USABLE.
• 13.1 (Priority 2) Clearly identify the target of each link, partially covered by LINK_TARGET_ID.
• 13.2 (Priority 2) Provide metadata to add semantic information to pages and sites, partially covered by PAGE_TITLE.
• 1.5 (Priority 3) 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, possibly covered by IMAGE_MAPS and NON-TEXT_ALTERNATIVES.
• 2.2 (Priority 3) 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 (for images), partially covered by COLOR_CONTRAST
• 5.5 (Priority 3) Provide summaries for tables, possibly covered by TABLES_SUPPORT and TABLES_ALTERNATIVES.
• 5.6 (Priority 3) Provide abbreviations for header labels, possibly covered by TABLES_SUPPORT and TABLES_ALTERNATIVES.
• 10.3 (Priority 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, possibly partially covered TABLES_ALTERNATIVES.
• 13.5 (Priority 3) Provide navigation bars to highlight and give access to the navigation mechanism, possibly NAVBAR.
• 13.6 (Priority 3) Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group, possibly NAVBAR and partially possibly CENTRAL_MEANING.

Everything: start from scratch to comply with these checkpoints:

• 1.3 (Priority 1) 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.
• 1.4 (Priority 1) 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.
• 4.1 (Priority 1) Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
• 7.1 (Priority 1) Until user agents allow users to control flickering, avoid causing the screen to flicker.
• 8.1 (Priority 1) Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies (priority 1 if functionality is important and not presented elsewhere).
• 11.4 (Priority 1) 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.
• 3.6 (Priority 2) Mark up lists and list items properly.
• 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
• 6.4 (Priority 2) For scripts and applets, ensure that event handlers are input device-independent.
• 6.5 (Priority 2) Ensure that dynamic content is accessible or provide an alternative presentation or page.
• 7.2 (Priority 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).
• 7.3 (Priority 2) Until user agents allow users to freeze moving content, avoid movement in pages.
• 8.1 (Priority 2) Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies (priority 1 if functionality is important and not presented elsewhere).
• 9.2 (Priority 2) Ensure that any element that has its own interface can be operated in a device-independent manner.
• 9.3 (Priority 2) For scripts, specify logical event handlers rather than device-dependent event handlers.
• 13.3 (Priority 2) Provide information about the general layout of a site (e.g., a site map or table of contents).
• 4.2 (Priority 3) Specify the expansion of each abbreviation or acronym in a document where it first occurs.
• 4.3 (Priority 3) Identify the primary natural language of a document.
• 10.5 (Priority 3) Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
• 11.3 (Priority 3) Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)
• 13.7 (Priority 3) If search functions are provided, enable different types of searches for different skill levels and preferences.
• 13.9 (Priority 3) Provide information about document collections (i.e., documents comprising multiple pages.).
• 13.10 (Priority 3) Provide a means to skip over multi-line ASCII art.
• 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.
• 14.3 (Priority 3) Create a style of presentation that is consistent across pages.