BBC Mobile Accessibility Standards and Guidelines
Comparison between "BBC Mobile Accessibility Standards and Guidelines" and W3C-WAI's WCAG 2.0/UAAG 2.0
Jan Richards, 7 March 2014
References:
BBC Mobile Accessibility Standards and Guidelines (Draft ver. 0.7): http://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile
WCAG 2.0 (Full Recommendation): http://www.w3.org/TR/WCAG/
UAAG 2.0 (May 2013 Public Working Draft): http://www.w3.org/TR/2013/WD-UAAG20-20130523/
Comparison:
Legend:
@Issue: A flagged issue.
@None: There are no matching success criteria.
@@: Issues with the BBC wording
BBC: Editorial
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Note: The UAAG 2.0 column will only be filled out in cases where either WCAG 2.0 does not apply or where compliance with WCAG 2.0 might involve only user agent action (e.g. relying on browser zoom to perform font-resizing).
Consistent labelling should be used across websites and native applications as well as within websites and applications
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
The language of a page or app must be specified
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A)
Changes in language must be specified.
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)
BBC: Design
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Information conveyed with colour must also be identifiable from context or mark-up
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
The colour of text and background content must have sufficient contrast
1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA) …
1.4.6 Contrast (Enhanced): The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: (Level AAA) …
Content must still be readable when styling is unsupported or removed
@This SC covers the idea:
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
When focused, all actionable and focusable elements must have a visible state change
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A) … - active keyboard focus …
Links and other actionable elements must be clearly distinguishable
@None: Usability – once the means to distinguish are chosen, then accessibility requirements apply (e.g. 1.4.1 Use of Color)
1.3.1 Highlighted Items: The user can specify that the following classes be highlighted so that each is uniquely distinguished: (Level A) … - recognized enabled input elements (distinguished from disabled elements) …
Touch targets must be large enough to touch accurately
@Addressed indirectly via 1.4.4 Resize Text.
An inactive space of should be provided around active elements
@Not addressed
Where zoom is supported on the platform it must not be suppressed
@Addressed indirectly via 1.4.4 Resize Text.
Consistent components should be used
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
BBC: Images
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Images of text should be avoided
1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA) …
1.4.9 Images of Text (No Exception): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA) …
Informational background images must have a visible alternative
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A) …
BBC: Text Equivalents
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Alternatives should briefly describe the editorial intent or purpose of the image, object, or element
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A) …
Decorative images must be hidden from assitive technology
1.1.1 Non-text Content: … (Level A) - Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology. …
Tooltips must not repeat link text or other alternatives
@Not addressed
Changes of state must be communicated visually and audibly
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) …
Elements must have accessibility properties set appropriately
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Visual formatting alone must not be used to convey meaning
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)
BBC: Structure
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
All pages or screens must be uniquely and clearly identifiable
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)
When supported by the platform pages must provide a logical and hierarchical heading structure
2.4.10 Section Headings: Section headings are used to organize the content. (Level AAA) …
Controls, objects and grouped interface elements must be represented as a single accessible component
@While technically covered by the following SCs, I think WCAG2’s guidance docs could be more clear on this:
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A)
Containers should be used to describe page structure
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
BBC: Links
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Link and navigation text must uniquely describe the target or function of the link or item
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
2.4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA)
Links to alternative formats must indicate that an alternative is opening
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
Repeated links to the same resource must be contained within the same link
Reflects WCAG2 technique H2 (http://www.w3.org/TR/WCAG20-TECHS/H2)
BBC: Forms
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
All form controls must have labels
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) …
Labels must be placed close to the controls, and be laid out appropriately
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)
A default input mode must be indicated
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
@Note: BBC doc has some good HTML techniques.
Controls, elements, and objects must be properly grouped
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
BBC: Notifications
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Where necessary screen reader accessible instructions should be provided to supplement visual cues
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)
3.3.5 Help: Context-sensitive help is available. (Level AAA)
Changes of state must be communicated visually and audibly
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
Audio only cues must be accompanied by a visual cues
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A) - Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. …
Standard operating system alerts must be used where available
@Not addressed
5.1.3 Implement Accessibility Features of platform: If the user agent contains non-web-based user interfaces, then those user interfaces follow user interface accessibility guidelines for the platform. (Level A)
Clear error messages must be provided
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A)
Assistance for correcting errors should be provided
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA)
BBC: Navigation
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
BBC: Focus
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
All active elements must be focusable and inactive elements must not be focusable
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A) …
2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A)
There must be no keyboard trap
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)
Content order must be logical
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
Actionable content must be navigable in a meaningful sequence
2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)
Focus or context must not automatically change on user input
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
Touch events must only be triggered when touch is removed from a control
@None: Touch interface technique for:
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A)
2.1.4 Separate Selection from Activation: The user can specify that focus and selection can be moved without causing further changes in focus, selection, or the state of controls, by either the user agent or author content. (Level A)
Alternative inputs must be supported
2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA)
BBC: Scripts and dynamic content
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
All functionality must be available without the use of JavaScript
@None: This was in WCAG1, but removed for WCAG2 since many uses of Javascript can be considered accessibility supported.
Updating media or animated content must have a pause, stop or hide control
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A) - Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and - Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Automatic page refreshes must not be used
3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)
A method must be provided to extend, change or turn off a time limit when a timed response is required
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) - Turn off: The user is allowed to turn off the time limit before encountering it; or - Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or - Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times …
BBC: Audio and video
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Subtitles and audio description must be provided on all long form content such as TV programmes available for catch up
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA)
Transcripts or equivalent textual content should be provided for long form AV content
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)
Audio must not play automatically unless the user is made aware this is happening or a pause/stop button is provided
@Issue: WCAG2 addresses control, but not auto-play:
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)
2.11.1 Time-Based Media Load-Only: The user can override the play on load of recognized time-based media content such that the content is not played until explicit user request. (Level A)
Metadata should be provided for media
@This could be considered a technique for:
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)
BBC: Recommendations
Similar WCAG 2.0 SCs
Similar UAAG 2.0 SCs
Offer a core accessible website
@None: Usability.
Link mobile and desktop sites
@None: Usability.
Use progressive enhancement
@None: Usability.
Minimise text fields
@None: Usability.
Other WCAG 2.0 Success Criteria and their relevance to Mobile Accessibility:
See also http://www.w3.org/TR/wcag2ict/
WCAG 2.0 SCs
Applicable to Mobile Applications
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA)
Yes
1.2.6 Sign Language (Prerecorded): Sign language interpretation is provided for all prerecorded audio content in synchronized media. (Level AAA)
Yes
1.2.7 Extended Audio Description (Prerecorded): Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. (Level AAA)
Yes
1.2.8 Media Alternative (Prerecorded): An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. (Level AAA)
Yes
1.2.9 Audio-only (Live): An alternative for time-based media that presents equivalent information for live audio-only content is provided. (Level AAA)
Yes
1.4.7 Low or No Background Audio: For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: (Level AAA)
No Background: The audio does not contain background sounds.
Turn Off: The background sounds can be turned off.
20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content.
Yes
1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA)
Foreground and background colors can be selected by the user.
Width is no more than 80 characters or glyphs (40 if CJK).
Text is not justified (aligned to both the left and the right margins).
Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
…
Yes – though the 80 character list item might not be as relevant.
2.2.3 No Timing: Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA)
Yes
2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA)
Yes
2.2.5 Re-authenticating: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA)
Yes
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
Yes – keyboard. switch users still need this mechanism.
2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA)
Yes
2.4.8 Location: Information about the user's location within a set of Web pages is available. (Level AAA)
Yes (i.e., location in a complicated app)
3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA)
Yes
3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA)
Yes
3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA)
Yes
3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA)
Yes
3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA)
Reversible: Submissions are reversible.
Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Yes
3.3.6 Error Prevention (All): For Web pages that require the user to submit information, at least one of the following is true: (Level AAA)
Reversible: Submissions are reversible.
Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
Yes
4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.
Applicable to mobile web, but not to native apps that are coded rather than marked up.