Pearson Accessibility Requirements

Version 3

October 2011

Requirements (For Design, Development and QA)

Follow the Web Accessibility Guidelines for Digital Learning Products during development:

·  Guideline 1: Choose technologies (e.g. HTML vs. Flash) with accessibility in mind.

·  Guidelines 2-3: Make time limits adjustable.

·  Guideline 4: Check the order that content is read in screen readers & correct any issues.

·  Guideline 5: Make sure screen reader users can find dynamic additions to the screen.

·  Guidelines 6-8: Check keyboard access (access without a mouse) & correct any issues.

·  Guideline 9: Support navigation within the page.

·  Guideline 10: Do not change the user's location on the screen unexpectedly.

·  Guidelines 11-13: Use semantic markup, text formatting, and CSS for their intended purposes.

·  Guideline 14: Associate every form element with a label.

·  Guideline 15: Write link text that tells users where the link goes.

·  Guideline 16: Specify the human language (e.g. Arabic, Chinese, English) of text.

·  Guideline 17: Write page and frame titles that give the purpose of the page or the frame.

·  Guideline 18: Consider all users while writing instructions for user interfaces.

·  Guideline 19: Use properly nested markup tags & correct spelling.

·  Guideline 20: Make sure screen readers can speak info about controls (e.g. "checkbox, selected").

·  Guidelines 21-22: Use text that users can adjust (e.g. change size, change color).

·  Guidelines 23-25: Do not use motion known to cause seizures, migraines, or difficulty reading/focusing.

·  Guideline 26: Make sure text has good foreground/background contrast.

·  Guidelines 27-28: Design with color blind users in mind.

·  Guidelines 29-31: Provide alternatives for visuals that provide info (images, video & animation).

·  Guidelines 32-33: Keep decorative images & irrelevant hidden content silent in screen readers.

·  Guidelines 34-35: Make sure audio won't interfere with other audio, including screen reader speech.

·  Guidelines 36-37: Provide alternatives for sounds that provide info (audio files, podcasts, video).

·  Guideline 38: Ensure that alternatives (e.g. transcripts, eBooks) mirror source materials.

·  Guideline 39: Allow & encourage accessibility in content provided by users.

·  Guidelines 40-41: Use accessible publishing options (e.g. PDF settings, Flash import scripts).

·  Guideline 42: Document your product's accessibility.