Loading ...

WCAG 2.0 Compliance | Communifire Documentation

Home » communifire documentation » Wiki » Documentation » Compliance » WCAG 2.0 Compliance
Communifire Documentation  Wiki
Public Space
Activity Stream Content
Version 8

WCAG 2.0 Compliance

0 
 /5
0 (0votes)

Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content 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. Following these guidelines will also often make your Web content more usable to users in general.

WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents.

WCAG 2.0 Layers of Guidance

The individuals and organizations that use WCAG vary widely and include web designers and developers, policy makers, purchasing agents, teachers, and students. In order to meet the varying needs of this audience, several layers of guidance are provided including overall principles, general guidelines, testable success criteria and a rich collection of sufficient techniques, advisory techniques, and documented common failures with examples, resource links and code.

  • Principles - At the top are four principles that provide the foundation for Web accessibility: perceivable, operable, understandable, and robust.

  • Guidelines - Under the principles are guidelines. The 12 guidelines provide the basic goals that authors should work toward in order to make content more accessible to users with different disabilities. The guidelines are not testable, but provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques.

  • Success Criteria - For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification, purchasing, regulation, and contractual agreements. In order to meet the needs of different groups and different situations, three levels of conformance are defined: A (lowest), AA, and AAA (highest).

  • Sufficient and Advisory Techniques - For each of the guidelines and success criteria in the WCAG 2.0 document itself, the working group has also documented a wide variety of techniques. The techniques are informative and fall into two categories: those that are sufficient for meeting the success criteria and those that are advisory. The advisory techniques go beyond what is required by the individual success criteria and allow authors to better address the guidelines. Some advisory techniques address accessibility barriers that are not covered by the testable success criteria. Where common failures are known, these are also documented.

 

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

Criteria Recommendations Supporting Feature
1.1.1 Nontext Content
  • All images, form image buttons, and image map hot spots have appropriate, equivalent alternative text.
  • Images that do not convey content, are decorative, or with content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. All linked images have descriptive alternative text.
  • Equivalent alternatives to complex images are provided in context or on a separate (linked and/or referenced via longdesc) page.
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

Guideline 1.2 Time-based Media: Provide alternatives for time-based media

Criteria Recommendations Supporting Feature
1.2.1 Prerecorded Audio-only and Video-only
  • A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.).
  • A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track).
 This feature is supported by Communifire in 508 and WCAG 2.0.
1.2.2 Captions (Prerecorded)
  • Synchronized captions are provided for non-live, web-based video (YouTube videos, etc.)
 YouTube videos which have synchronized captions can be shared on Communifire.
1.2.3 Audio Description or Media Alternative (Prerecorded)
  • A descriptive text transcript OR audio description audio track is provided for non-live, web-based video
 Not Applicable
1.2.4 Captions (Live)
  • Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)
 Not Applicable
1.2.5 Audio Description (Prerecorded)
  • Audio descriptions are provided for all video content NOTE: Only required if the video conveys content visually that is not available in the default audio track.
 Not Applicable
1.2.6 Sign Language (Prerecorded)
  • A sign language video is provided for all media content that contains audio.
 Not Applicable
1.2.7 Extended Audio Description (Prerecorded)
  • When an audio description track cannot be added to video due to audio timing (e.g., no pauses in the audio), an alternative version of the video with pauses that allow audio descriptions is provided.
 Not Applicable
1.2.8 Media Alternative (Prerecorded)
  • A descriptive text transcript is provided for all pre-recorded media that has a video track.
 Not Applicable
1.2.9 Audio-only (Live)
  • A descriptive text transcript (e.g., the script of the live audio) is provided for all live content that has audio.
 Not Applicable

 

Guideline 1.3 Adaptable: Create content that can be presented in different ways (e.g., simpler layout) without losing information or structure

Criteria Recommendations Supporting Feature
1.3.1 Info and Relationships
  • Tables are used for tabular data. Headings, where necessary, are used to associate data cells with headers. Data table captions and summaries are used where appropriate.
  • Text labels are associated with form input elements. Related form elements are grouped with fieldset/legend.
 Not Applicable
1.3.2 Meaningful Sequence
  • The reading and navigation order (determined by code order) is logical and intuitive.
 Not Applicable
1.3.3 Sensory Characteristics
  • Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column").
  • Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue.").
 Not Applicable

 

Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background

Criteria Recommendations Supporting Feature
1.4.1 Use of Color
  • Color is not used as the sole method of conveying content or distinguishing visual elements.
  • Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus.
 This feature is supported by Communifire in 508 and WCAG 2.0.
1.4.2 Audio Control
  • A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.
 Not Applicable
1.4.3 Contrast (Minimum)
  • Text and images of text have a contrast ratio of at least 4.5:1.
  • Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) bold has a contrast ratio of at least 3:1.
 Not Applicable
1.4.4 Resize text
  • The page is readable and functional when the text size is doubled.
 Not Applicable
1.4.5 Images of Text
  • If the same visual presentation can be made using text alone, an image is not used to present that text.
 Not Applicable
1.4.6 Contrast (Enhanced)
  • Text and images of text have a contrast ratio of at least 7:1. Large text - at least 18 point (typically 24px) or 14 point (typically 18.66px) bold has a contrast ratio of at least 4.5:1.
 This feature is supported by Communifire in 508 and WCAG 2.0.
1.4.7 Low or No Background Audio
  • Audio of speech has no or very low background noise so the speech is easily distinguished.
 Not Applicable
1.4.8 Visual Presentation

Blocks of text over one sentence in length:

  • Are no more than 80 characters wide.
  • Are NOT fully justified (aligned to both the left and the right margins).
  • Have adequate line spacing (at least 1/2 the height of the text) and paragraph spacing (1.5 times line spacing).
  • Have a specified foreground and background color. These can be applied to specific elements or to the page as a whole using CSS (and thus inherited by all other elements).
  • Do NOT require horizontal scrolling when the text size is doubled.
 Not Applicable
1.4.9 Images of Text (No Exception)
  • Text is used within an image only for decoration (image does not convey content) OR when the information cannot be presented with text alone.
 Not Applicable

 

Principle 2: Operable - User interface components and navigation must be operable.

Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard

Criteria Recommendations Supporting Feature
2.1.1 Keyboard
  • All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing).
  • Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.1.2 No Keyboard Trap (Level
  • Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.1.3 Keyboard (No Exception)
  • All page functionality is available using the keyboard.
 Partially Supported (Some sections of Communifire do not support it. For example: Admin Section)

 

Guideline 2.2 Enough Time: Provide users enough time to read and use content

Criteria Recommendations Supporting Feature
2.2.1 Timing Adjustable
  • If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.2.2 Pause, Stop, Hide
  • Automatically moving, blinking, or scrolling content that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 5 seconds.
  • Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates.
 Not Applicable
2.2.3 No Timing
  • The content and functionality has no time limits or constraints.
 Not Applicable
2.2.4 Interruptions
  • Interruptions (alerts, page updates, etc.) can be postponed or suppressed by the user.
 Not Applicable
2.2.5 Reauthenticating
  • If an authentication session expires, the user can re-authenticate and continue the activity without losing any data from the current page.
 Not Applicable

 

Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures

Criteria Recommendations Supporting Feature
2.3.1 Three Flashes or Below Threshold
  • No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.3.2 Three Flashes
  • No page content flashes more than 3 times per second.
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are

Criteria Recommendations Supporting Feature
2.4.1 Bypass Blocks
  • A link is provided to skip navigation and other page elements that are repeated across web pages.
  • If a page has a proper heading structure, this may be considered a sufficient technique instead of a "Skip to main content" link. Note that navigating by headings is not yet supported in all browsers.
  • If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.4.2 Page Titled
  • The web page has a descriptive and informative page title.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.4.3 Focus Order
  • The navigation order of links, form elements, etc. is logical and intuitive.
 Not Applicable
2.4.4 Link Purpose (In Context)
  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and it's context (e.g., surrounding paragraph, list item, table cell, or table headers).
  • Links (or form image buttons) with the same text that go to different locations are readily distinguishable.
 Not Applicable
2.4.5 Multiple Ways
  • Multiple ways are available to find other web pages on the site - at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages.
 This feature is supported by Communifire in 508 and WCAG 2.0. (Search is supported)
2.4.6 Headings and Labels
  • Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., "More Details") or label text (e.g., "First Name") unless the structure provides adequate differentiation between them.
 Not Applicable
2.4.7 Focus Visible
  • It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are).
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.4.8 Location
  • If a web page is part of a sequence of pages or within a complex site structure, an indication of the current page location is provided, for example, through breadcrumbs or specifying the current step in a sequence (e.g., "Step 2 of 5 - Shipping Address").
 Not Applicable
2.4.9 Link Purpose (Link Only)
  • The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone.
  • There are no links (or form image buttons) with the same text that go to different locations.
 This feature is supported by Communifire in 508 and WCAG 2.0.
2.4.10 Section Headings
  • Beyond providing an overall document structure, individual sections of content are designated using headings, where appropriate.
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

Principle 3: Understandable - Information and the operation of user interface must be understandable.

Guideline 3.1 Readable: Make text content readable and understandable

Criteria Recommendations Supporting Feature
3.1.1 Language of Page
  • The language of the page is identified using the HTML lang attribute (<html lang="en">, for example).
 Not Applicable
3.1.2 Language of Parts
  • When appropriate, the language of sections of content that are a different language are identified, for example, by using the lang attribute (<blockquote lang="es")>
 Not Applicable
3.1.3 Unusual Words
  • Words that may be ambiguous, unknown, or used in a very specific way are defined through adjacent text, a definition list, a glossary, or other suitable method.
 Not Applicable
3.1.4 Abbreviations
  • Expansions for abbreviations are provided by expanding or explaining the definition the first time it is used, using the element, or linking to a definition or glossary. NOTE: WCAG
 Not Applicable
3.1.5 Reading Level
  • A more understandable alternative is provided for content that is more advanced than can be reasonably read by a person with roughly 9 years of primary education.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.1.6 Pronunciation
  • If the pronunciation of a word is vital to understanding that word, its pronunciation is provided immediately following the word or via a link or glossary.
 Not Applicable

 

Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways

Criteria Recommendations Supporting Feature
3.2.1 On Focus
  • When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.2.2 On Input
  • When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.2.3 Consistent Navigation
  • Navigation links that are repeated on web pages do not change order when navigating through the site.
 Not Applicable
3.2.4 Consistent Identification
  • Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.2.5 Change on Request
  • Substantial changes to the page, the spawning of pop-up windows, uncontrolled changes of keyboard focus, or any other change that could confuse or disorient the user must be initiated by the user. Alternatively, the user is provided an option to disable such changes.
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes

Criteria Recommendations Supporting Feature
3.3.1 Error Identification
  • Required form elements or form elements that require a specific format, value, or length provide this information within the element's label.
  • If utilized, form validation cues and errors (client-side or server-side) alert users to errors in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.3.2 Labels or Instructions
  • Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.
 This feature is supported by Communifire in 508 and WCAG 2.0.
3.3.3 Error Suggestion
  • If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner.
 Not Applicable
3.3.4 Error Prevention (Legal, Financial, Data)
  • If the user can change or delete legal, financial, or test data, the changes/deletions are reversible, verified, or confirmed.
 Not Applicable
3.3.5 Help
  • Provide instructions and cues in context to help in form completion and submission.
 Not Applicable
3.3.6 Error Prevention (All)
  • If the user can submit information, the submission is reversible, verified, or confirmed.
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

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 Recommendations Supporting Feature
4.1.1 Parsing
  • Significant HTML/XHTML validation/parsing errors are avoided.
This feature is supported by Communifire in 508 and WCAG 2.0.
4.1.2 Name, Role, Value
  • Markup is used in a way that facilitates accessibility. This includes following the HTML/XHTML specifications and using forms, form labels, frame titles, etc. appropriately
 This feature is supported by Communifire in 508 and WCAG 2.0.

 

This document is based on Web Content Accessibility Guidelines (WCAG) 2.0 published by W3C.

Wiki Index

Pages

Intranet Software