Accessibility and Compliance

Created by Cole LaFrance, Modified on Thu, 02 Jun 2016 at 10:49 AM by Cole LaFrance

Accessibility Guideline Compliance

Digital Deployment Standard Model

What We Test and How

Section 508 and WCAG 2.0 Level AA - deals with the biggest and most common barriers for disabled users
http://achecker.ca/checker/index.php
W3C Markup Validity
https://validator.w3.org/
Multiple browsers and operating systems to verify design is correctly rendered.
https://crossbrowsertesting.com/

How to Report Accessibility Issues

Report issues by submitting a support ticket to support@digitaldeployment.com

More information about the SLA at www.digitaldeployment.com/sla

WCAG 2.0 Compliance Details

The requirements listed below align with the WCAG 2.0 AA standard for web content.

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.

Alternative text and captions are easily added using the CMS. Content authors are responsible for content compliance.

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.

To meet this requirement a transcript for each piece of video/audio should be included in the post. This will ensure that content is available for accessibility tools like a screen reader. Content authors are responsible for content compliance.

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.

We encourage the use of YouTube or Vimeo for quick and easy addition of video to the CMS and both services allow captioning.

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.

Content authors are responsible for the content and third-party video hosting like YouTube or Vimeo would provide the tools to adhere to this guideline.

Content authors would need to include audio description of the video content in the synchronized media. The audio description would provide information about actions, characters, scene changes, and on-screen text that are important and not described or spoken in the main sound track. It would read something like a screenplay or book.

1.2.4 Captions (Live)

Captions are provided for all live audio content in synchronized media.

No live audio solution is a part of the CMS but a third party solution could be embedded. Accessibility dependant on third party solution.

1.2.5 Audio Description (Prerecorded)

Audio description is provided for all prerecorded video content in synchronized media.

Meeting this requirement will be the responsibility of content authors.

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Relationships between different pieces of content are indicated as are post-type labels. If information and relationships do not appear to be clear content authors should add a text description.

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Using the CMS content authors can use different headers (<h1> through <h6>) or ordered lists to express the sequence of content. Content is easily formatted using the built-in WYSIWYG editor.

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.

When designing the website we avoid relying solely on sensory characteristics of components. Content authors will also be responsible for adhering to this guideline.

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.

When designing the website we avoid using color as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

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.

We strongly discourage the use of video or audio that starts automatically and is not a default in the CMS.

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.

When designing the website we design the text to be easy to read. Content authors need to also follow these guidelines.

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.

If requested, we can include a tool to scale text size. Additionally, all modern browsers have zoom capabilities built in.

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.

Content authors can provide alternative descriptions of images using the tools provided by the CMS. Content authors will need to follow these guidelines when adding images. All UI elements that use images will have accompanying text.

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.

The navigation menu and other page elements are navigable using the keyboard.

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.

We adhere to this guideline.

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 spacebar"), 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.

An automatically advancing carousel of content and/or images will pause when an input device is interacting with them. Photo galleries also have a timed advancement but have tools to pause and navigate the content.

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.

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.

No website elements flash as described. Content authors will need to follow these guidelines.

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Website navigation is repeated throughout the website and can be bypassed by a user using a screen-reader.

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.

A post’s title or navigation term’s overview function as the title. Content authors are responsible for them.

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.

We adhere to this guideline.

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.

Content authors have the ability to manage link text in order to follow this guideline.

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.

Users can access a post through navigation, site search, or contextually through related posts and pods.

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

Content authors are responsible for the accuracy of headings and labels. Our production team does do quality reviews of the content before a website goes live.

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

We adhere to this guideline.

3.1.1 Language of Page

The default human language of each Web page can be programmatically determined.

The default language can be set for the whole website. If requested we can configure your website so that the language can be set for each navigation term.

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.

If you were identifying parts of a page with different languages, the lang attribute would need to be manually added using the editor.

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.

We adhere to this guideline.

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.

We adhere to this guideline.

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.

We adhere to this guideline. The only exception would be microsites. If a navigation term is indicated as the root of a microsite the navigation will change relative to the root.

3.2.4 Consistent Identification

Components that have the same functionality within a set of Web pages are identified consistently.

We adhere to this guideline and content authors should as well.

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.

Website login, webforms, and content entry indicate the item of issue.

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

Content authors can add labels or instructions for each field of a webform.

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.

Suggestions or corrections for search queries when Apache Solr (optional) is being used to enhance site search.

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.

Authenticated users can review, edit, and delete their webform submissions. Unauthenticated users can not review, edit, or delete their submissions. Additionally, authenticated users can save a draft of a webform and finish it later.

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.

We adhere to this guideline.

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.

We adhere to this guideline.