En 301 549 Accessibility Declaration of Conformance

EN 301 549 Accessibility Declaration of Conformance
Date: 2 August 2017
Name of Product: Microsoft Authenticator
Description of Product: The Microsoft Authenticator lets you quickly and securely verify your identity online, for all of your accounts.
Platform: iOS, Android, Windows Mobile (8, 10)
Product Build: iOS - 5.3.5 or higher; Android - 6.1 or higher; Windows Mobile - 6.0.19 or higher.
Accessibility Website: Enterprise Disability Answer Desk
For assistance with this report, please email us.
Section 1 Scope
This EN 301 549 Product Accessibility Conformance specifies the functional accessibility requirements applicable to Microsoft ICT products and services.
Section 2 References
EN 301 549 References
Section 3 Definitions and abbreviations
EN 301 549 Definitions and abbreviations
Section 4 Functional Statements
EN 301 549 Functional Statements
Functional Accessibility Requirements Section 5 Generic Requirements
This section does not apply to Microsoft Authenticator.
Section 6 ICT with two-way voice communication
This section does not apply to Microsoft Authenticator.
Section 7 ICT with video capabilities
This section does not apply to Microsoft Authenticator.
This section does not apply to Microsoft Authenticator.
Section 9 Web
This section does not apply to Microsoft Authenticator.
Section 10 Non-web documents
This section does not apply to Microsoft Authenticator.
Section 11 Software
Criteria
Supporting Features
Remarks and Explanations
11.2.1.1 Non-text content (screen reading supported)
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in WCAG 2.0 Table 1.1.1.
Supported
11.2.1.2 Audio-only and video-only (pre-recorded)
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, it shall satisfy the Success Criterion in Table 11.2: Audio-only and video-only (pre-recorded):
For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:
Pre-recorded Audio-only: An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content.
Pre-recorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for pre-recorded video-only content.
Not Applicable
11.2.1.3 Captions (pre-recorded)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.3: Captions (pre-recorded):
Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
Not Applicable
11.2.1.4 Audio description or media alternative (pre-recorded)
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.4: Audio description or media alternative (pre-recorded:
An alternative for time-based media or audio description of the pre-recorded 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
11.2.1.5 Captions (live)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.5. Captions (live):
Captions are provided for all live audio content in synchronized media.
Not Applicable
11.2.1.6 Audio description (pre-recorded)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.6: Audio description (pre-recorded):
Audio description is provided for all pre-recorded video content in synchronized media.
Not Applicable
11.2.1.7 Info and relationships
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.7: Info and relationships:
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Supported
11.2.1.8 Meaningful sequence
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.8: Meaningful sequence:
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
Supported
11.2.1.9 Sensory characteristics
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.9: 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
11.2.1.10 Use of colour
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.10: Use of colour:
Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Supported
11.2.1.11 Audio control
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.11: Audio control:
If any audio in a software 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.
Not Applicable
11.2.1.12 Contrast (minimum)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.12: 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
11.2.1.13 Resize text
Where ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the Success Criterion in Table 11.13: 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
11.2.1.14 Images of text
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.14: 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.
Not Applicable
Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the Success Criterion in Table 11.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
11.2.1.16 No keyboard trap
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.16: No keyboard trap:
If keyboard focus can be moved to a component of the software 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
11.2.1.17 Timing adjustable
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.17: Timing adjustable:
For each time limit that is set by the software, at least one of the following is true:
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; 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.
Not Applicable
11.2.1.18 Pause, stop, hide
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.18: 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
11.2.1.19 Three flashes or below threshold
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.19: Three flashes or below threshold:
Software does 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
11.2.1.22 Focus order
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.22: Focus order:
If software 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
11.2.1.23 Link purpose (in context)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.23: 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
11.2.1.25 Headings and labels
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.25: Headings and labels:
Headings and labels describe topic or purpose.
Supported
11.2.1.26 Focus visible
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in 11.26: Focus visible:
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Supported
11.2.1.27 Language of software
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.27: Language of software:
The default human language of software can be programmatically determined.
Supported
11.2.1.29 On focus
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.29: On focus:
When any component receives focus, it does not initiate a change of context.
Supported
11.2.1.30 On input
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.30: 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
Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.33: 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
11.2.1.34 Labels or instructions
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.34: Labels or instructions:
Labels or instructions are provided when content requires user input.
Supported
11.2.1.35 Error suggestion
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.35: 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
11.2.1.36 Error prevention (legal, financial, data)
Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.36: Error prevention (legal, financial, data):
For software 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:
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.
Supported
11.2.1.37 Parsing
Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.37: Parsing:
For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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
11.2.1.38 Name, role, value
Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.38: 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
11.2.2.1 – 11.2.2.38
Not Applicable
Closed Functionality
11.3.2.1 Platform accessibility service support for software that provides a user interface
Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.
Platform software should support requirements 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.
Not Applicable
11.3.2.2 Platform accessibility service support for assistive technologies
Platform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.
Platform software should support the requirements of clauses 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirement are not applicable.
Not Applicable
11.3.2.3 Use of accessibility services
Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.3.2.5 to 11.3.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.
See sections 11.3.2.5 through 11.3.2.17
11.3.2.4 Assistive technology
Where the ICT is assistive technology it shall use the documented platform accessibility services.
Page of
|