Web Content Accessibility Guidelines compliance
The Web Content Accessibility Guidelines (WCAG), produced by the World Wide Web Consortium, are a set of standards designed to make web-based information more accessible to more people. In the words of the Consortium, WCAG 2.0 enables web content to be “ … accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these.” The Identity Cloud's Hosted Login product is fully compliant with WCAG 2.0 Level AA (the guidelines consist of three levels: A, AA, and AAA).
The following tables list the WCAG 2.0 guidelines, and indicate whether or not Hosted Login meets those specifications. Note that, in these tables, guidelines applicable only to WCAG 2.0 Level AAA are shown in gray. These guidelines are included solely for informational purposes, and are not meant to suggest that Hosted Login is Level AAA compliant.
Principle 1 – Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
| Guideline | Supported | Notes |
|---|---|---|
| 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. Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. Test: If non-text content is a test or exercise that would be invalid if presented intext, 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. | n/a | Hosted Login screens do not use non-text elements to convey information. |
Guideline 1.2 – Time-based Media
Provide alternatives for time-based media.
| Guideline | Supported | Notes |
|---|---|---|
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 1.2.4 Captions (Live) Captions are provided for all live audio content in synchronized media. | n/a | Hosted Login screens don’t use audio or video. |
| 1.2.5 Audio Description (Prerecorded) Audio description is provided for all prerecorded video content in synchronized media. | n/a | Hosted Login screens don’t use audio or video. |
| 1.2.6 Sign Language (Prerecorded) Sign language interpretation is provided for all prerecorded audio content in synchronized media. | n/a | Hosted Login screens don’t use audio or video. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 1.2.9 Audio-only (Live) An alternative for time-based media that presents equivalent information for live audio-only content is provided. | n/a | Hosted Login screens don’t use audio or video. |
Guideline 1.3 – Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
| Guideline | Supported | Notes |
|---|---|---|
| 1.3.1 Info and Relationships Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | n/a | Hosted Login does not use presentations of any kind. |
| 1.3.2 Meaningful Sequence When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | n/a | Hosted Login content is not sequenced. |
| 1.3.3 Sensory Characteristics Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. | n/a | Hosted Login screens do not use sensory characteristics to convey information. |
Guideline 1.4 – Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
| Guideline | Supported | Notes |
|---|---|---|
| 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. | ✓ | Hosted Login screen elements don't convey information by using color alone. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 1.4.3 Contrast (Minimum) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1. | ✓ | Hosted Login screens use black text on a white background. Using an online contrast testing tool, a set of Identity Cloud screens had an average contrast ratio of 9.73:1. |
| 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. | ✓ | Hosted Login screens can be resized to at least 500% with no loss of clarity. |
| 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. | n/a | Hosted Login screens use actual text rather than images of text when rendering screens. |
| 1.4.6 Contrast (Enhanced) The visual presentation of text and images of text has a contrast ratio of at least 7:1. | ✓ | As noted previously, informal testing suggests that Hosted Login screens have a contrast ratio of better than 9:1. |
| 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. | n/a | Hosted Login screens don’t use audio or video. |
| 1.4.8 Visual Presentation For the visual presentation of blocks of text, a mechanism is available to achieve the following: 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. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. | ||
| 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. | n/a | Hosted Login screens do not use images of text. |
Principle 2 – Operable
User interface components and navigation must be operable.
Guideline 2.1 – Keyboard Accessible
Make all functionality available from a keyboard.
| Guideline | Supported | Notes |
|---|---|---|
| 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 end points. | ✓ | |
| 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. | ✓ | Users can use the TAB key to move between elements on a Hosted Login screen. |
| 2.1.3 Keyboard (No Exception) All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. | n/a | Hosted Login doesn’t time keystrokes. |
Guideline 2.2 – Enough Time
Provide users enough time to read and use content.
| Guideline | Supported | Notes |
|---|---|---|
| 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; 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. | n/a | Time limits aren’t placed on Hosted Login screens. |
| 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. | n/a | Hosted Login screens do not use moving, blinking, scrolling, or auto-updating elements. |
| 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. | ||
| 2.2.4 Interruptions Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | ||
| 2.2.5 Re-authenticating When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. |
Guideline 2.3 – Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
| Guideline | Supported | Notes |
|---|---|---|
| 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. | n/a | Hosted Login screens don’t include flashing text, images, or other elements. |
| 2.3.2 Three Flashes Web pages do not contain anything that flashes more than three times in any one second period. | Not Applicable | Hosted Login screens don’t include flashing text, images, or other elements. |
Guideline 2.4 – Navigable
Provide ways to help users navigate, find content, and determine where they are.
| Guideline | Supported | Notes |
|---|---|---|
| 2.4.1 Bypass Blocks A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | n/a | Hosted Login content is not repeated on multiple screens. |
| 2.4.2 Page Titled Web pages have titles that describe topic or purpose. | ✓ | All Hosted Login screens have a title. |
| 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. | n/a | |
| 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. | ✓ | Hosted Login uses link text such as Sign up for an account as opposed to more-ambiguous text (such as Create). |
| 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. | n/a | |
| 2.4.6 Headings and Labels Headings and labels describe topic or purpose. | ✓ | |
| 2.4.7 Focus Visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | ✓ | Hosted Login screens indicate focus by using a flashing cursor and by changing element colors (e.g., changing the color of a button when the mouse hovers over it). |
| 2.4.8 Location Information about the user's location within a set of Web pages is available. | ||
| 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. | ||
| 2.4.10 Section Headings Section headings are used to organize the content. |
Principle 3 – Understandable
Information and the operation of the user interface must be understandable.
Guideline 3.1 – Readable
Make text content readable and understandable.
| Guideline | Supported | Notes |
|---|---|---|
| 3.1.1 Language of Page The default human language of each Web page can be programmatically determined. | ✓ | Hosted Login uses the HTML lang tag to indicate the screen language. |
| 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. | ✓ | All text elements on a Hosted Login screen use the same language (see 3.1.1 above). |
| 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. | ||
| 3.1.4 Abbreviations A mechanism for identifying the expanded form or meaning of abbreviations is available. | n/a | Hosted Login screens do not use abbreviations. |
| 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. | n/a | Informal testing suggests that Hosted Login screens, on average, have a Flesch-Kincaid reading level score of 9.3. This means that the screens should be easily understood by anyone with at least a ninth-grade education. |
| 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. |
Guideline 3.2 – Predictable
Make Web pages appear and operate in predictable ways.
| Guideline | Supported | Notes |
|---|---|---|
| 3.2.1 On Focus When any user interface component receives focus, it does not initiate a change of context. | ✓ | |
| 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. | ✓ | |
| 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. | ✓ | |
| 3.2.4 Consistent Identification Components that have the same functionality within a set of Web pages are identified consistently. | ✓ | |
| 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. | ✓ |
Guideline 3.3 – Input Assistance
Help users avoid and correct mistakes.
| Guideline | Supported | Notes |
|---|---|---|
| 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. | ✓ | |
| 3.3.2 Labels or Instructions Labels or instructions are provided when content requires user input. | ✓ | |
| 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. | ✓ | |
| 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: 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. | n/a | Akamai does not recommend using Hosted Login for managing legal or financial data. |
| 3.3.5 Help Context-sensitive help is available. | Although Hosted Login doesn't support context sensitive help, Hosted Login screens include a Visit our help center link that can be used to link to help information. | |
| 3.3.6 Error Prevention (All) For Web pages that require the user to submit information, 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. | ✓ |
Principle 4 – Robust
Content must be robust enough that it can be interpreted 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.
| Guideline | Supported | Notes |
|---|---|---|
| 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. | ✓ | Hosted Login uses HTML and standard HTML tagging to define and render screens. |
| 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. |
Updated almost 2 years ago