W3C

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

W3C Working Draft, 14 January 2008

Table of Contents

Introduction

Incomplete draft: This document is a draft and is not complete. Particularly, the section WCAG 2.0 and MWBP Together is only an outline; WCAG 1.0 to MWBP is only partly filled out. It is subject to major changes and is therefore not intended for implementation. It is provided for review and feedback only. Please send feedback to both wai-eo-editors@w3.org and public-bpwg@w3.org.

This page is part of a suite of related documents. Please refer to the “How to Use These Documents” section for more information.

It describes how different Mobile Web Best Practices (MWBPs) help improve the experience for users with disabilities and how compliance with these BPs can help comply with the Web Content Accessibility Guidelines 1.0 (WCAG). For content that already complies with MWBP, it outlines what may need to be done to comply with all of WCAG (Extending from MWBP to WCAG 1.0).

By improving usability, all BPs help improve accessibility. This section describes the specific accessibility benefits and the ways in which some relate directly to the Web Content Accessibility Guidelines 1.0.

As described in this section, many Mobile Web BPs have the added benefit of partial or complete compliance with certain WCAG 1.0 checkpoints. However, the accessibility guidelines are often more detailed or describe a different aspect of the same concept. It should not be assumed that following any BP will ensure accessibility. To ensure accessibility it is important to always consult the Web Content Accessibility Guidelines.

Each BP is covered to answer the following questions:

Extending from MWBP to WCAG 1.0

This section provides guidance on the “upgrade path” from MWBP to accessibility through WCAG 1.0 compliance. What follows is a summary of the detailed information for each BP that follows it. For each of the WCAG 1.0 priorities there are three possible levels of effort required, labelled for simplicity with keywords (nothing, something, everything):

To summarize, if your content already complies with MWBP, to achieve compliance with WCAG 1.0, you need to do the following:

For Priority 1

Nothing: content already complies with these checkpoints:

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

Everything: start from scratch to comply with these checkpoints:

[Not evaluated yet]. When reviewing the document the following list should be ignored. During document editing, it contains CPs, SCs or BPs not yet evaluated. It is progressively reduced as items are studied and moved to the “something”, “nothing” and “everything” lists. It will not appear in the finished document.

For Priority 2

Nothing: content already complies with these checkpoints:

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

Everything: start from scratch to comply with these checkpoints:

[Not evaluated yet]. When reviewing the document the following list should be ignored. During document editing, it contains CPs, SCs or BPs not yet evaluated. It is progressively reduced as items are studied and moved to the “something”, “nothing” and “everything” lists. It will not appear in the finished document.

For Priority 3

Nothing: content already complies with these checkpoints:

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

Everything: start from scratch to comply with these checkpoints:

[Not evaluated yet]. When reviewing the document the following list should be ignored. During document editing, it contains CPs, SCs or BPs not yet evaluated. It is progressively reduced as items are studied and moved to the “something”, “nothing” and “everything” lists. It will not appear in the finished document.

Individual Mobile Web Best Practices Compared

This section examines in turn each of the Mobile Web Best Practices where there is a relationship to the Web Content Accessibility Guidelines. Those that are believed to have no relationship are listed seperately. Two main aspects are considered for each BP, “How does it help especially users with disabilities?” and “Does it give me WCAG compliance?” which are introduced in a general way below.

How does it help especially users with disabilities?

Describes how the BP helps users with disabilities above and beyond the benefit to the general user in the mobile context. Users with disabilities benefit from the Mobile Web Best Practices like any other user. This paragraph focuses on the added benefits for their special needs of users with different disabilities. Best Practices that have no specific benefit for users with disabilities beyond that experienced by the general user in the mobile context is marked [no added benefit]. Explanations of the benefits are given in the corresponding section “Individual Mobile Web Best Practices Compared” of the accompanying document From Mobile Web Best Practices 1.0 to Web Content Accessibility Guidelines 2.0 under the section on each BP.

Does it give me WCAG compliance?

Many Web sites wish to ensure that their content is both mobile aware and accessible to users with disabilities by complying with both the MWBPs and Web Content Accessibility Guidelines (WCAG). For a site that complies with the MWBP it is useful to know how much has already been achieved towards accessibility, and how much more could be achieved for little extra effort.

Many BPs correspond directly to WCAG 1.0 checkpoints and in these cases complying with one automatically gives compliance with the other, with no extra effort. For example, [USE_OF_COLOR] ensures compliance with WCAG 1.0 checkpoint 2.1, “Ensure that all information conveyed with color is also available without color, for example from context or markup” with no added effort.

With other BPs, a little extra effort or simply considering a more diverse range of user needs can achieve compliance with WCAG 1.0 checkpoint. For example, [COLOR_CONTRAST] is intended to help mobile users with monochrome displays or in poor lighting conditions. By considering also the needs of users with colour deficits (colour blindness) the same BP makes content accessible to more users and ensures compliance with WCAG 1.0 checkpoint “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”.

Other BPs prohibit the use of features that can cause accessibility barriers. Complying with these BPs ensures that some WCAG checkpoints simply do not apply. For example, [NO_FRAMES], by excluding the use of frames, means that it is not necessary to comply with WCAG 1.0 checkpoint 12.1, “Title each frame to facilitate frame identification and navigation”.

List of Best Practices Described

Below is a list of the BPs described in detail. There follows a list of BPs believed to have no relationship to WCAG.

The following BPs are believed to have no added accessibility benefit and no relation to any WCAG provision, and are listed below for completeness:

[ACCESS_KEYS] Assign access keys to links in navigational menus and frequently accessed functionality

How does ACCESS_KEYS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Providing that access keys are also defined as necessary for form controls (not made explicit in the BP but apparently implicit in “frequently accessed functionality”), this BP also ensures compliance with checkpoint 9.5,“Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls”. If it is not apparent from the content or shown by the device, provide a summary of access keys used in content on a separate page. Perhaps warn that access key assignments may be changed by the user agent (to prevent conflicts) in ways the author cannot predict.

Back to Best Practices list.

[AUTO_REFRESH] Do not create periodically auto-refreshing pages, unless you have informed the user and provided a means of stopping it

How does AUTO_REFRESH help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: A related checkpoint is 7.4, “Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages”. At the time of writing, some user agents allow the user to disable auto-refresh, but others do not. If auto-refresh is used (under the provision of the BP to inform the user and provide a means to deactivate it) the checkpoint is not complied with (WCAG requires that the user agent be used to turn it off, while the BP requires the content to do it). However, if auto-refresh is not used at all, this does ensure compliance with the checkpoint.

Back to Best Practices list.

[AVOID_FREE_TEXT] Avoid free text entry where possible.

How does AVOID_FREE_TEXT help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[BACKGROUND_IMAGE_READABILITY] When using background images make sure that content remains readable on the device

How does BACKGROUND_IMAGE_READABILITY help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No. However it helps achieve compliance with checkpoint 6.1, Organize documents so they may be read without style sheets and 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 as described in COLOR_CONTRAST.

Back to Best Practices list.

[BALANCE] Take into account the trade-off between having too many links on a page and asking the user to follow too many links to reach what they are looking for

How does BALANCE help especially users with disabilities?

Does it give me WCAG compliance?: No.

Back to Best Practices list.

[CENTRAL_MEANING] Ensure that material that is central to the meaning of the page precedes material that is not.

How does CENTRAL_MEANING help especially users with disabilities?

Does it give me WCAG compliance?: For WCAG 1.0, this BP corresponds to 12.3, “Place distinguishing information at the beginning of headings, paragraphs, lists, etc.”. However, where the checkpoint is described as applicable to paragraphs, in the mobile context these units of content are often the complete page. It also relates to the spirit of WCAG 1.0 checkpoint 12.3, “Divide large blocks of information into more manageable groups where natural and appropriate”, although, like [PAGE_SIZE_USABLE], in a way not explicitly contemplated in the guidelines. This WCAG checkpoint is much broader in scope than the BP.

Back to Best Practices list.

[CLARITY] Use clear and simple language

How does CLARITY help especially users with disabilities?

Does it give me WCAG compliance?: This BP goes some of the way to ensuring compliance with 14.1, “Use the clearest and simplest language appropriate for a site's content”, although the BP is concerned primarily with context of use, which was not contemplated in WCAG 1.0. WCAG emphasizes writing style and thematic content in all contexts. It also covers (in the explanation) 13.8 “Place distinguishing information at the beginning of headings, paragraphs, lists, etc.”

Back to Best Practices list.

[COLOR_CONTRAST] Ensure that foreground and background color combinations provide sufficient contrast

How does COLOR_CONTRAST help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No. However, it may ensure (using additional criteria) compliance with WCAG 1.0 checkpoint 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. Note that WCAG 2.0 suggests a Contrast Ratio and the size of text to which the ratio applies.

Back to Best Practices list.

[CONTROL_LABELLING] Label all form controls appropriately and explicitly associate labels with form controls

How does CONTROL_LABELLING help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 12.4, “Associate labels explicitly with their controls” with no further effort.

Back to Best Practices list.

[CONTROL_POSITION] Position labels so they lay out properly in relation to the form controls they refer to

How does CONTROL_POSITION help especially users with disabilities?

Does it give me WCAG compliance?: This BP corresponds to WCAG 1.0 checkpoint 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”. While the BP is concerned with reflowing and adapting content, WCAG is concerned to enable screen readers to determine the association in the absence of an explicit association in markup. However, this association of form labels with their controls by position for correct interpretation by screen readers is a convention, not fully described in W3C recommendations (WCAG 1.0 describes positioning of text input and list boxes but not checkboxes and radio buttons). The description in the BP is not adequate for accessibility purposes, and following the BP does not ensure compliance with the WCAG 1.0 checkpoint.

Tip: Use explicitly associated labels (refer to [CONTROL_LABELLING]), but if you can not, then avoid nesting the control inside the label element as it is not supported in an accessible way by most user agents.

[DEFAULT_INPUT_MODE] Specify a default text entry mode, language and/or input format, if the device is known to support it

How does DEFAULT_INPUT_MODE help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[ERROR_MESSAGES] Provide informative error messages and a means of navigating away from an error message back to useful information

How does ERROR_MESSAGES help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No, but it is related to checkpoint 13.4, “Use navigation mechanisms in a consistent manner” in that the BP encourages provision of consistent navigation in error pages.

Back to Best Practices list.

[FONTS] Do not rely on support of font related styling

How does FONTS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No, but it goes some of the way to complying with checkpoint 6.1, “Organize documents so they may be read without style sheets”. As the font elements described by the BP are deprecated in recent versions of HTML, it also goes some way to meeting WCAG 1.0 checkpoint 11.2, “Avoid deprecated features of W3C technologies”.

Back to Best Practices list.

[GRAPHICS_FOR_SPACING] Do not use graphics for spacing

How does GRAPHICS_FOR_SPACING help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No, but if you do use images for spacing that goes against WCAG 1.0 checkpoint 3.1, “When an appropriate markup language exists, use markup rather than images to convey information” and 3.3, “Use style sheets to control layout and presentation”.

Back to Best Practices list.

[IMAGE_MAPS] Do not use image maps unless you know the device supports them effectively

Comment: The references section for this BP is misleading: “This relates to WCAG 1.2 and 9.1”. It relates to these checkpoints but not in the way covered by the BP.

How does IMAGE_MAPS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: If image maps are used, this BP does not give compliance with any WCAG provision. If image maps are not used at all, then it is unnecessary to provide the text alternatives for them required by checkpoint 1.1 “Provide a text equivalent for every non-text element” or the keyboard shortcuts for them required by 9.5, “Provide keyboard shortcuts to important links (including those in client-side image maps), ...”; checkpoints 1.2, “Provide redundant text links for each active region of a server-side image map” and 9.1, “Provide client-side image maps instead of server-side image maps...” do not apply.

Back to Best Practices list.

How does LINK_TARGET_ID help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Partially. This BP goes some way to ensuring compliance with checkpoint13.1,“Clearly identify the target of each link”. However, to ensure accessibility it is important to understand that the user may read (or hear) the links in a page as part of a list of links without surrounding contextual information. For this reason it is important that the link text not lose its meaning when readout of context. Refer to WCAG 1.0 HTML Techniques: Link text gives more information.

Back to Best Practices list.

[MEASURES] Do not use pixel measures and do not use absolute units in markup language attribute values and style sheet property values

How does MEASURES help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 3.4, “Use relative rather than absolute units in markup language attribute values and style sheet property values” with no further effort.

Back to Best Practices list.

[MINIMIZE_KEYSTROKES] Keep the number of keystrokes to a minimum

How does MINIMIZE_KEYSTROKES help especially users with disabilities?

Does it give me WCAG compliance?: The intention of this BP is the use of keyboard shortcuts (referred to confusingly as “navigation keys”). If this is done, then this BP ensures compliance with WCAG 1.0 checkpoint 9.5, “Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls”. However, when complying with the BP it is important to be aware that WCAG is more explicit in what it applies to than is the BP (which specifies only “items”).

Back to Best Practices list.

How does NAVBAR help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: This BP deals with an aspect not considered in WCAG. However, conceptually identifying the navigation mechanisms will ultimately help content designers understand and provide the functionality needed. For WCAG 1.0, it will help compliance with checkpoints 13.5, “Provide navigation bars to highlight and give access to the navigation mechanism” and 13.6, “Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group”.

Back to Best Practices list.

How does NAVIGATION help especially users with disabilities?

Does it give me WCAG compliance?: For WCAG 1.0, complying with this BP also ensures compliance with checkpoint 13.4,“Use navigation mechanisms in a consistent manner”, but considering the aspects covered in WCAG 1.0 Core Techniques: Navigation will clarify what is needed for all users. For WCAG 2.0, it goes some way to ensuring compliance with 3.2.3 “Consistent Navigation”, although WCAG is more detailed and specific (“same relative order”) than the MWBP (“same navigation”).

Back to Best Practices list.

[NO_FRAMES] Do not use frames

How does NO_FRAMES help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures that checkpoints 12.1, “Title each frame to facilitate frame identification and navigation” and 12.2, “Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone” do not apply to the content.

Back to Best Practices list.

[NON-TEXT_ALTERNATIVES] Provide a text equivalent for every non-text element

How does NON-TEXT_ALTERNATIVES help especially users with disabilities?

Does it give me WCAG compliance?: Providing a text equivalent for every non-text element ensures compliance with WCAG 1.0 checkpoint 1.1 “Provide a text equivalent for every non-text element”. However, it is important to remember that non-text content is more than just images. The tests suggested in the BPs may not lead to adequately accessible content. Avoiding CSS image replacement and pictures of words implies using text and markup, thus avoiding the need for text alternatives and the accessibility problems caused by these techniques. This aspect of the BP goes some way to complying with WCAG 1.0 checkpoint 3.1, “When an appropriate markup language exists, use markup rather than images to convey information”.

Tip: Using the alt and longdesc attributes adequately is not always a simple matter and the BPs provide no further guidance. Refer to WCAG 1.0 HTML techniques Short text equivalents for images (“alt-text”) and Long descriptions of images for further guidance.

Comment: Longdesc support in mobile devices?? have added a tip, as it the following workaround isn't actually described in the BP (but should be).

Tip: As stated in the BP, if the user agent is not known to support the longdesc attribute of the img element (and additionally, until assistive technology is known to support it adequately), do rely on it. Provide in addition a separate [D] link adjacent to the image. Refer to WCAG 1.0 HTML technique Invisible d-links (note that this technique should not be considered deprecated in the mobile context, which was not anticipated when the techniques were written).

Back to Best Practices list.

[OBJECTS_OR_SCRIPT] Do not rely on embedded objects or script

How does OBJECTS_OR_SCRIPT help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 6.3 “Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported...”, but be sure to follow the further guidance given in WCAG 1.0 and accompanying techniques. Using onclick for script rather than onkey and onmouse event handlers helps ensure compliance with WCAG 1.0 checkpoint 6.4, “For scripts and applets, ensure that event handlers are input device-independent”.

Back to Best Practices list.

[PAGE_SIZE_USABLE] Divide pages into usable but limited size portions

How does PAGE_SIZE_USABLE help especially users with disabilities?

Does it give me WCAG compliance?: No, but this BP goes some way toward complying with WCAG 1.0 checkpoint 12.3, “Divide large blocks of information into more manageable groups where natural and appropriate”. However the WCAG checkpoint is much broader in scope, covering all usage contexts.

Back to Best Practices list.

[PAGE_TITLE] Provide a short but descriptive page title

How does PAGE_TITLE help especially users with disabilities?

Does it give me WCAG compliance?: This BP goes some of the way to compliance with WCAG 1.0 checkpoint 13.2, “Provide metadata to add semantic information to pages and sites”.

Back to Best Practices list.

[POP_UPS] Do not cause pop-ups or other windows to appear and do not change the current window without informing the user

How does POP_UPS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 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” (by avoiding the problem: the BP is more restrictive).

Back to Best Practices list.

[PROVIDE_DEFAULTS] Provide pre-selected default values where possible

How does PROVIDE_DEFAULTS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Partially. If default values are used for all text controls this ensures compliance with checkpoint 10.4 “Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas”. However, there is debate about the need for such text, as user agents do now handle empty input boxes correctly.

Back to Best Practices list.

[REDIRECTION] Do not use markup to redirect pages automatically. Instead, configure the server to perform redirects by means of HTTP 3xx codes

How does REDIRECTION help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 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”.

Back to Best Practices list.

[SCROLLING] Limit scrolling to one direction, unless secondary scrolling cannot be avoided.

How does SCROLLING help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[STRUCTURE] Use features of the markup language to indicate logical document structure

How does STRUCTURE help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 3.5, “Use header elements to convey document structure and use them according to specification” with no further effort. If content is structured using section headings this will help towards achieving compliance with checkpoint 6.1, “Organize documents so they may be read without style sheets”.

Tip: Although the BP has a generic title covering all structural elements, it only mentions section headings. Using other commonly-accepted structural elements not mentioned in the BP can improve usability for mobile users as well as accessibility. These elements include lists, quotations and citations, table markup, and semantic aspects like emphasis.

Back to Best Practices list.

[STYLE_SHEETS_SUPPORT] Organize documents so that if necessary they may be read without style sheets

How does STYLE_SHEETS_SUPPORT help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 6.1, “Organize documents so they may be read without style sheets” with no further effort. The BP recognizes that style sheets may not be supported and that users may turn them off. However, it is important to remember that some users (for example, non-visual) may simply not perceive (see) their effect.

Back to Best Practices list.

[STYLE_SHEETS_USE] Use style sheets to control layout and presentation, unless the device is known not to support them

How does STYLE_SHEETS_USE help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 3.3, “Use style sheets to control layout and presentation” with no further effort.

Back to Best Practices list.

[TAB_ORDER] Create a logical order through links, form controls and objects

How does TAB_ORDER help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensure compliance with checkpoint 9.4, “Create a logical tab order through links, form controls, and objects” with no further effort.

Back to Best Practices list.

[TABLES_ALTERNATIVES] Where possible, use an alternative to tabular presentation

How does TABLES_ALTERNATIVES help especially users with disabilities?

Comment: Check on the implications of this. Tables may be easier to use (less verbose) for screen reader users, if the browser and screen reader support them.

Does it give me WCAG 1.0 compliance?: No, but if tables are not used then the checkpoints under Guideline 5, “Create tables that transform gracefully” do not apply.

Back to Best Practices list.

[TABLES_LAYOUT] Do not use tables for layout

How does TABLES_LAYOUT help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No, but if tables are not used for layout, then content complies with checkpoint 5.3, “Do not use tables for layout unless the table makes sense when linearized”. In that case 5.4, “If a table is used for layout, do not use any structural markup for the purpose of visual formatting”, does not apply.

Back to Best Practices list.

[TABLES_NESTED] Do not use nested tables

How does TABLES_NESTED help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[TABLES_SUPPORT] Do not use tables unless the device is known to support them

How does TABLES_SUPPORT help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No, but if tables are not used in any adaptation of the content served, then the checkpoints under Guideline 5, “Create tables that transform gracefully” does not apply. It goes some way to ensuring compliance with WCAG 1.0 checkpoint 3.3, “Use style sheets to control layout and presentation”.

Back to Best Practices list.

[TESTING] Carry out testing on actual devices as well as emulators

How does TESTING help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Tip: You can improve accessibility when performing testing by involving users with a range of abilities (not only evaluation and development staff). Refer to the WAI resource “Involving Users in Web Accessibility Evaluation” for more information.

Back to Best Practices list.

[THEMATIC_CONSISTENCY] Ensure that content provided by accessing a URI yields a thematically coherent experience when accessed from different devices

How does THEMATIC_CONSISTENCY help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[URIS] Keep the URIs of site entry points short

How does URIS help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: No.

Back to Best Practices list.

[USE_OF_COLOR] Ensure that information conveyed with color is also available without color.

How does USE_OF_COLOR help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: Yes, this BP ensures compliance with checkpoint 2.1, “Ensure that all information conveyed with color is also available without color, for example from context or markup” with no added effort. However, it is important to taken into account that unlike the MWBP, the accessibility guidelines specify the ways that color may be used.

Back to Best Practices list.

[VALID_MARKUP] Create documents that validate to published formal grammars

How does VALID_MARKUP help especially users with disabilities?

Does it give me WCAG 1.0 compliance?: This BP ensures compliance with checkpoint 3.2, “Create documents that validate to published formal grammars” with no further effort. If the markup is the most recent version of a W3C recommendation it also helps to ensure compliance with WCAG 1.0 checkpoint 11.1, “Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported”. It helps with compliance with 11.2, “Avoid deprecated features of W3C technologies”.

Back to Best Practices list.