...
...These lists have WCAG 2.0 Success Criteria numbers linked to the Addressing WCAG 2.0 Success Criteria section below, and MWBP Best Practices linked to the Accessibility aspects of Mobile Web Best Practices section below.
Nothing, content that complies with MWBP already complies with these success criteria:
Something, more effort is need or a check is needed to comply with these success criteria:
Everything, these success criteria are not related to a MWBP:
... The WCAG 2.0 Success Criteria numbers are linked to the corresponding section of the WCAG 2.0 Quick Reference...
[below cover WCAG 2.0 SC in numerical order.
QUESTION: Should this section include only the ones in the "Something" category in order to keep this section short & focused? Or, should it list all SC so that people can use this as a comprehensive list???]
WCAG 2.0: "All non-text content has a text alternative that presents equivalent information, except for the situations listed below..."
[@@ short instructions on what is needed for WCAG 2.0 in relation to what is already done for MWBP. links to related MWBPs in the Accessibility aspects of Mobile Web Best Practices section @@]
WCAG 2.0: "All live audio-only content has a text alternative"
[@@ short instructions on what is needed for WCAG 2.0 in relation to what is already done for MWBP. links to related MWBPs in the Accessibility aspects of Mobile Web Best Practices section @@]
WCAG 2.0: "Captions are provided for prerecorded synchronized media, except if the synchronized media is an alternative to text and is clearly labeled as such."
[@@ short instructions on what is needed for WCAG 2.0 in relation to what is already done for MWBP. links to related MWBPs in the Accessibility aspects of Mobile Web Best Practices section @@]
...
...
...
...
List of Best Practices Described BelowBelow is a list of the BPs described in detail in this section. Each name is a link to the detailed description that follows. |
List of Best Practices not Related to WCAG 2.0The following BPs are believed to have no added accessibility benefit and no relation to any WCAG provision, and are listed below for completeness:
|
How does it enhance accessibility to users with disabilities?: Some users, for example those with motor disability, are unable to use a mouse even when the context of use allows one. These persons often use only a keyboard or a device that emulates a keyboard. This situation parallels that of all users of mobile devices as these are not usually equipped with a mouse. They also also help people with visual disabilities who can not see the screen well and for those with short-term memory loss or cognitive limitations. Access keys may be helpful for all keyboard users. They are especially (perhaps only) useful when the browser allows the user to discover the keys that are assigned (some do, some don't).
Does help meet any WCAG 2.0 success criteria? No, but it corresponds to an advisory technique for SC 2.4.1 Bypass Blocks.
How does it enhance accessibility to users with disabilities?: The BP mentions that “Auto-refreshing pages are widely recognized as presenting accessibility problems” but does not explain why. Auto-refresh is especially confusing to users of screen readers. When a page is refreshed a screen reader may begin reading the updated content again from the beginning, causing confusion and preventing the user from ever reading the whole page. It is also a barrier for users of screen magnification, and those with cognitive and reading disabilities. Providing a means to stop auto-refresh may help these users if they are aware of it.
Does help meet any WCAG 2.0 success criteria? possibly.
A related success criterion 3.2.5, “Change on Request” requires that refresh be started only by user request, but this BP concerns using auto-refresh started automatically and stopped by user request. If auto-refresh is used compliance is not necessarily achieved. However, if auto-refresh is not used at all, this does ensure compliance with the success criterion.
Refer to 3.2.5 Change on Request, coverage at level AAA.
...
...
...