Policy - Challenger and WCAG Success Criteria

We follow the guidelines as put forth by the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines

Challenger makes reasonable efforts to follow the guidelines as put forth by the World Wide Web Consortium's (W3C) Web Content Accessibility Guidelines 2.1 (Level A) in accordance with section 508 of the Americans with Disabilities Act in order to provide accessible products and user experiences for all users. Accommodations to timed assignments can be provided by faculty through the custom exam creation process. 

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.

1.1.1 Non-text Content Level A

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.  Hide full description

  • Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Success Criterion 4.1.2 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.

Guideline 1.2 – Time-based Media

Provide alternatives for time-based media.

1.2.1 Audio-only and Video-only (Prerecorded) Level A

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:  Show full description

1.2.2 Captions (Prerecorded) Level A

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.

1.2.3 Audio Description or Media Alternative (Prerecorded) Level A

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.

Guideline 1.3 – Adaptable

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

1.3.1 Info and Relationships Level A

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

1.3.2 Meaningful Sequence Level A

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

1.3.3 Sensory Characteristics Level A

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.

Note 1: For requirements related to color, refer to Guideline 1.4.

Guideline 1.4 – Distinguishable

Make it easier for users to see and hear content including separating foreground from background.

1.4.1 Use of Color Level A

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Note 1: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.

1.4.2 Audio Control Level A

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.

Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Principle 2 – Operable

User interface components and navigation must be operable.

Guideline 2.1 – Keyboard Accessible

Make all functionality available from a keyboard.

2.1.1 Keyboard Level A

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.

Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

2.1.2 No Keyboard Trap Level A

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.

Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

2.1.4 Character Key Shortcuts Level A(Added in 2.1)

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:  Show full description

Guideline 2.2 – Enough Time

Provide users enough time to read and use content.

2.2.1 Timing Adjustable Level A

For each time limit that is set by the content, at least one of the following is true:  Show full description

2.2.2 Pause, Stop, Hide Level A

For moving, blinking, scrolling, or auto-updating information, all of the following are true:  Show full description

Guideline 2.3 – Seizures and Physical Reactions

Do not design content in a way that is known to cause seizures or physical reactions.

2.3.1 Three Flashes or Below Threshold Level A

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.

Note 1: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Guideline 2.4 – Navigable

Provide ways to help users navigate, find content, and determine where they are.

2.4.1 Bypass Blocks Level A

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

2.4.2 Page Titled Level A

Web pages have titles that describe topic or purpose.

2.4.3 Focus Order Level A

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.

2.4.4 Link Purpose (In Context) Level A

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.

Guideline 2.5 – Input Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

2.5.1 Pointer Gestures Level A(Added in 2.1)

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

2.5.2 Pointer Cancellation Level A(Added in 2.1)

For functionality that can be operated using a single pointer, at least one of the following is true:  Show full description

2.5.3 Label in Name Level A(Added in 2.1)

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

2.5.4 Motion Actuation Level A(Added in 2.1)

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:  Show full description

Principle 3 – Understandable

Information and the operation of the user interface must be understandable.

Guideline 3.1 – Readable

Make text content readable and understandable.

3.1.1 Language of Page Level A

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

Guideline 3.2 – Predictable

Make Web pages appear and operate in predictable ways.

3.2.1 On Focus Level A

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

3.2.2 On Input Level A

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.

Guideline 3.3 – Input Assistance

Help users avoid and correct mistakes.

3.3.1 Error Identification Level A

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

Labels or instructions are provided when content requires user input.

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.

4.1.1 Parsing Level A

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.

Note 1: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete.

4.1.2 Name, Role, Value Level A

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.

Note 1: 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.

Contacting Us

All comments, queries and requests relating to our policies and/or use of your information are welcomed and should be addressed as follows:

By mail:
Challenger Corporation
5100 Poplar Ave. Ste. 400
Memphis, TN 38137
USA

Need additional support?

If you are still having problems, you can request support from a live support representative.

Request Support

If your request is received when our offices are closed, a response will be provided the next available business day we are open.

We can also be contacted by phone at 800-676-0822, Option 2, during regular business hours (8 AM - 5 PM Central Time, Monday - Friday excepting holidays.)

Account Login
Product Website
Product Store