Pearson Accessibility Template
Version 3
October 2011
Requirements (For Design, Development and QA)
Follow the Web Accessibility Guidelines for Digital Learning Products during development and record what was done to meet each guideline in the table below. These guidelines mirror industry standards and so should be familiar.
In some cases, industry standards allow exceptions to the rules where compliance would be difficult or impossible. These exceptions:
· would be silent (not apparent to customers causing unpleasant surprises in class)
· could easily be misunderstood to apply where they do not
Because of this, the Pearson Guidelines do not include exceptions that would allow a significant issue for some users. If you are not sure how to meet a guideline for your particular product, or if you suspect your product meets an exception, contact . We will either offer solutions or provide you with language for your document on how the feature meets an exception.
Accomplishments
Pearson Guideline / Product-specific Requirements(if any)
(Editors or Product Managers complete this section) / Description of Accomplishment /
1 – Accessible Technologies / <Consider accessibility when first exploring a UI technology for your product>
2 – Time Limits: User Options / <Choose a method for allowing some students to have more time>
3 – Timed Tests: Instructor Options
4 – Sensible Reading Order
5 - Findable Dynamically-Added Content
6 – Keyboard Access / <Usually this is a coding issue and the same UI can be keyboard accessible. Choose a second method for highly mouse-centered activities such as drag & drop and select x/y coordinates. Will there be a separate set of buttons? Will the same buttons function differently for keyboard users? Will there be a screen overlay? A separate view that uses standard form controls? >
7 – Keyboard Access: Visibility
8 – Keyboard Access: Instructions
9 – Keyboard Access: In-Page Navigation
10 – Continuity of User's Place
11 – Page Element Roles (Semantic Markup)
12 - No Information through Text Formatting Alone
13 – Same info without style sheets
14 – Form Field Labels
15 – Meaningful Link Text
16 – Human Language
17 – Titles
18 – Sensory Independent Instructions
19 – Valid Markup & Spelling
20 – UI Controls & Screen Readers
21 – Encoded Text
22 – Text Resize / <How will the user be able to resize the text to at least 200% without assistive technology? Browser options? Built-in features? Separate view with text-reflow for eBook-like products?>
23 – No Flashing / Flickering
24 – Ability to Stop On-Screen Motion
25 – Still View of Moving Text / <How can the user access the content while it is not moving? Pause/Rewind buttons, separate view?>
26 – Contrast for Text Readability / <Should the default view be designed to have enough contrast, or will there be a high-contrast view? Or both?>
27 – No Reliance on Color Coding
28 – Color Contrast in Key Images
29 – Images or Animations that Provide Information
30 – Images that Label Active Elements
31 – Alternatives for Visual Elements in Multimedia / <Should all important visual information be provided in the standard voice over? Or will there be a separate audio track? Or a separate version of the video?>
32 – Decorative Elements
33 – Hidden Elements
34 – Let Users Control Audio
35 – Audio Foreground/Background Contrast
36 – Transcripts for Audio
37 – Captions
38 – Consistent Content Identifiers / <If different versions of this product will be used in the same classroom, how will students and instructors refer to page numbers/chapter sections for easy communication?>
39 - Alternatives for Non-text User Content / <If the application allows users to upload or create non-text content, how will they be able to provide text alternatives?>
40 – Publishing Options & Security / <If security options prevent screen reader access to the text, how will screen reader users be accommodated? Detect screen reader presence and open access? Separate player download? Special user access code through DSS office? Work with AT vendors to open access to just those screen readers?>
41 – Add-ons
42 – Document Accessibility