W3c web Content Accessibility Guidelines (wcag) 0 Conformance Statement

W3C Web Content Accessibility Guidelines (WCAG) 2.0 Conformance Statement
Date: 5/2/2017
Name of Product: Microsoft Windows 10 Creators Update (Mobile)
Description of Product: Microsoft Windows 10 Mobile Creators Update is the latest version of the Windows 10 operating system for mobile devices. This conformance statement includes:
This includes components included with Windows 10 such as the Start menu, lock screen, utility applications, Movies & TV, Notifications & Actions, Microsoft Edge, Microsoft Store, and Settings.
This conformance statement does not include certain pre-installed apps that are frequently updated outside of normal Windows Update channels (e.g., updateable apps via the Microsoft Store), such as Cortana, Outlook Email, Outlook Calendar, Microsoft Groove, and Skype, many of which maintain separate conformance statements that can be requested from eDAD or viewed at WCAG 2.0 Reports for Microsoft Products.
Windows 10 PC/Client is covered in a separate conformance statement.
Platform: Windows
Product Build: 1703
Product ID: 1703.15063 - mobile
Accessibility website: Microsoft Accessibility
Accessibility contact for more information: Enterprise Disability Answer Desk (eDAD)
For assistance with this report or finding one for another product, please email us.
WCAG 2.0 Conformance Requirements
Criteria
|
1. Conformance Level
|
2. Full pages
|
3. Complete processes
|
4. Only Accessibility-Supported Ways of Using Technologies
|
5. Non-Interference
|
Web Content Accessibility Guidelines (WCAG) 2.0
Principle 1: Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
Guideline 1.1 Text Alternatives
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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 in Table 11.1: Non-text content.
|
Supported
|
|
Guideline 1.2 Time-based Media
Provide alternatives for time-based media.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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:
• Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
• Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
|
Not Applicable
|
|
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.
|
Not Applicable
|
|
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.
|
Not Applicable
|
|
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media.
|
Not Applicable
|
|
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media.
|
Not Applicable
|
|
Guideline 1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
|
Supported
|
|
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
|
Supported With Exceptions
|
The Narrator user receiving a reminder or notification will be able to explore portions of the screen unrelated to the reminder or notification and may be confused by unexpected objects appearing in the order. This can be worked-around by exploring hierarchically via Narrator's left/right swiping command in item navigation mode.
|
1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.
|
Supported
|
|
Guideline 1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
|
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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.
|
Supported
|
|
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.
|
Supported
|
|
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:
• Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
• Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
• Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
|
Supported
|
|
1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.
|
Supported With Exceptions
|
Text scaling is not supported within the onscreen keyboard.
|
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:
• Customizable: The image of text can be visually customized to the user's requirements;
• Essential: A particular presentation of text is essential to the information being conveyed.
|
Supported
|
|
Principle 2: Operable
User interface components and navigation must be operable.
Guideline 2.1 Keyboard Accessible
Make all functionality available from a keyboard.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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.
|
Supported With Exceptions
|
Within Keyboard settings, the external (Bluetooth) keyboard user will be unable to scroll the "Learn more" information.
The keyboard user will be unable to quickly adjust snooze time and press the snooze button for notifications shown in the action center; the work-around is shift-tab back after setting the snooze interval and then tab back to put focus on the snooze interval combo box before using the arrow keys to access the buttons.
|
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.
|
Supported With Exceptions
|
External (Bluetooth) keyboard user tabbing in Settings / work access sign-in can get stuck and will need to resort to touch to recover and complete sign-in.
| Guideline 2.2 Enough Time
Provide users enough time to read and use content.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true:
• Turn off: User is allowed to turn off 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; or
• Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
• Essential Exception: The time limit is essential and extending it would invalidate the activity; or
• 20 Hour Exception: The time limit is longer than 20 hours.
|
Supported
|
|
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true:
• 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.
|
Supported With Exceptions
|
Animations in Start tiles cannot be globally disabled.
|
Guideline 2.3 Seizures
Do not design content in a way that is known to cause seizures.
|
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.
|
Supported
|
|
Guideline 2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
|
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
|
Supported
|
|
2.4.2 Page Titled: Web pages have titles that describe topic or purpose.
|
Supported
|
|
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.
|
Supported With Exceptions
|
In the setup configuration wizard, the Narrator user will not automatically hear the name of the "Get going fast" page because default focus is set on the wrong element. However, by exploring the page, the user can hear the page title.
|
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.
|
Supported
|
|
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.
|
Supported
|
|
2.4.6 Headings and Labels: Headings and labels describe topic or purpose.
|
Supported
|
|
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
|
Supported With Exceptions
|
On Lumia phones, legacy settings within Extra are not accessible with external (Bluetooth) keyboards.
|
Principle 3: Understandable
Information and the operation of user interface must be understandable.
Guideline 3.1 Readable
Make text content readable and understandable.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined.
|
Supported
|
|
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.
|
Supported
|
|
Guideline 3.2 Predictable
Make Web pages appear and operate in predictable ways.
|
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context.
|
Supported
|
|
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
|
Supported
|
|
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.
|
Supported
|
|
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently.
|
Supported
|
|
Guideline 3.3 Input Assistance
Help users avoid and correct mistakes.
|
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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.
|
Supported With Exceptions
|
Narrator user will not automatically hear if Microsoft account sign-in credentials were provided incorrectly and will have to explore the screen to discover the error.
|
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input.
|
Supported
|
|
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.
|
Supported
|
|
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:
1. Reversible: Submissions are reversible.
2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
|
Supported
|
|
Principle 4: Robust
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Guideline 4.1 Compatible
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria
|
Supporting Feature
|
Remarks and Explanations
|
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.
|
Supported
|
|
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.
|
Supported With Exceptions
|
The Narrator user who uses dictation will be unable to quickly move to another text box because focus will have been set to the soft keyboard. The user will need to close the soft keyboard by pressing the back button once before moving to the text box of interest.
On dual-SIM devices, the phone and messaging Start tiles will read out under Narrator with extra text that suggests no SIM is present but will complete with a correct indication of the SIM in use.
Upon reaching the Microsoft account sign-in page during the setup configuration wizard, the focus is set immediately on the username entry field, thereby passing the title text which explains that the user needs to sign in to their Microsoft account. To work-around, the user explores to the previous title element, which explains the actions required on this page.
Some Lumia-specific legacy settings have non-unique or missing accessible names under Narrator. And when the Narrator user joins the Insider Preview program via Settings and configures the Microsoft account to use, the user will hear extra meaningless text on the target button before finally hearing appropriate text for adding a Microsoft account.
|
Disclaimer
© 2017 Microsoft Corporation. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Microsoft cannot guarantee the accuracy of any information presented after the date of publication.
Microsoft regularly updates its websites and provides new information about the accessibility of products as that information becomes available.
Customization of the product voids this conformance statement from Microsoft. Customers may make independent conformance statements if they have conducted due diligence to meet all relevant requirements for their customization.
Please consult with Assistive Technology (AT) vendors for compatibility specifications of specific AT products.
This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.
Page of
|