1. VENDOR TIPS ON ACCESSIBLE PROCUREMENT
Elizabeth Delfs, Esq. Vice President and Senior Counsel
Jonathan Thurston, Global Head, Accessible Products

2. Our Story here is a slice of our our story,
we are a portfolio company--disparate tech stacks and content dev streams

3. A story of change Three examples of what we are doing:
Product guidelines
Internal accessibility training
Embedding accessibility into our workflows

4. Pearson’s Accessibility Guidelines
Accessibility Guidelines for E-Learning
Select a topic below to open the numbered guidelines.
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 pointing device) & 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 trouble 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.
Pearson Accessibility Guidelines
share where these are posted? Pearson Accessibility Guidelines (
and who has access to them? not restricted
how often do they get updated? guidelines will be updated as industry evolves.
when do stakeholders use them? training, QA, development, UX
in what context?
training: awareness
QA validation
Dev: awareness
UX: awareness
how do we enforce them? QA

5. Accessibility Specialist Training

6. Born Accessible Products
Embedding into Pearson’s Workflows

7. Escalation

8. Accessibility Partnership
Add to slide

9. Questions & Stories from the Field

10. Appendix

11. Guideline 14 Rationale Form Field Labels Guideline 14 Details
Guideline 14: Associate every form element with a label.
Form Field Labels
Guideline 14 Details
Hide Rationale
Show HTML & JavaScript
Show Android Applications
Show iOS Applications
Show PDF in Acrobat
Show Flash
Show Flex
Show Testing HTML
Show Testing Mobile Applications
Show Testing PDF in Acrobat
Show Related Guidelines
Tie each user input control (e.g. text field, radio button, pull-down menu) to text that describes the purpose of the control, using conventions for the media type.
Rationale
When a form field lacks an explicit label, screen readers will try to figure out which onscreen text labels the field. Sometimes they can't find any appropriate text, in which case the screen reader speaks no label at all. And, sometimes, the screen reader guesses the wrong label.
The techniques for this guideline explain how to use markup and other technology features to explicitly associate text labels with corresponding form elements in a way that screen readers will recognize. Explicit labels ensure that screen reader users will understand which form elements are associated with which labels. This way, they can be confident that they are entering information using the correct form fields.
Also, in HTML and Flex, many browsers use explicit labels to give users easier mouse access to radio buttons and check boxes. Clicking anywhere on the label can select and de­select the form elements. This is particularly helpful for people with minor mobility or dexterity issues.
Guideline 15 : Write link text that tells users where the link goes.

12. Guideline 14 PDF in Acrobat
Guideline 14: Associate every form element with a label.
Form Field Labels
Guideline 14 Details
Show Rationale
Show HTML & JavaScript
Show Android Applications
Show iOS Applications
Hide PDF in Acrobat
Show Flash
Show Flex
Show Testing HTML
Show Testing Mobile Applications
Show Testing PDF in Acrobat
Show Related Guidelines
Tie each user input control (e.g. text field, radio button, pull-down menu) to text that describes the purpose of the control, using conventions for the media type.
PDF in Acrobat
Form fields within the PDF document allow people with visual impairments easier access to enter data. If there are form fields within the PDF document, Acrobat will display a prompt to highlight them.
If there are no form fields in the document, there is nothing further that needs to be done.
Interactive Form Fields
Creating accessible form fields to a PDF is a multi-step process.
The process is slightly different in each version of Acrobat. In Acrobat 9 Pro, do the following:
If there are no form fields in the document, use Advanced > Accessibility > Run Form Field Recognition to automatically detect form fields and to make them fillable. Using the form editor, add and edit fields as necessary.
For each form field in the document, edit the properties using the context menu for the form field and select Properties. Each form field needs an accessible name using the tooltip property.

13. Guideline 14 Related Guidelines
Guideline 14: Associate every form element with a label.
Form Field Labels
Guideline 14 Details
Show Rationale
Show HTML & JavaScript
Show Android Applications
Show iOS Applications
Show PDF in Acrobat
Show Flash
Show Flex
Show Testing HTML
Show Testing Mobile Applications
Show Testing PDF in Acrobat
Hide Related Guidelines
Tie each user input control (e.g. text field, radio button, pull-down menu) to text that describes the purpose of the control, using conventions for the media type.
Related Guidelines
508 Web § (n)
When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
WCAG 2.0 Level A Non-text Content
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.
Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 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 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.

14. Gatekeeper: UX Accessibility Checklist:
Guideline #
Y/N
Comments
9. Is there another visual indication of information conveyed through color? 27 No
10. I have verified that nothing important 28
n/a