Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Conformance statement A-level for SharePoint Server 2013

Published: May 7, 2013

Summary: Conformance statement A-level for SharePoint Server 2013 in regards to Web Content Accessibility Guidelines 2.0 (http://www.w3.org/TR/WCAG20/).

Applies to:  SharePoint Server 2013 

Level A 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 below.

  • Controls, Input

    If non-text content is a control or accepts user input, then it has a name that describes its purpose.

    Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.

  • Time-Based Media

    If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content.

    Refer to Guideline 1.2 for additional requirements for media.

  • Test

    If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.

  • Sensory

    If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.

  • CAPTCHA

    If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.

  • 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.

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

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

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.

Not Applicable

Level A 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

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. 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

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

    The user is allowed to turn off the time limit before encountering it.

  • 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.

  • 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.

  • 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.

  • Essential Exception

    The time limit is essential and extending it would invalidate the activity.

  • 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.

  • 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

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

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

Level A 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

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

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

3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input.

Supported

Level A 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: If markup languages implement content, 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 that scripts generate), the name and role can be programmatically determined. States, properties, and values that can be set by the user can be programmatically set. Notification of changes to these items is available to user agents, including assistive technologies.

note Note:

This success criterion is primarily for web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

Supported

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. AT products that are compatible with all the rely-upon-technologies are expected to be functional with the product.

This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT.

Revised 05/07/2013.

Microsoft regularly updates its websites and provides new information about the accessibility of products as that information becomes available.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.