Section 508

1. Section 508 A loose interpretation by Elianna James

2. Overview • Section 508 is governed by Federal Acquisition Regulation (FAR). These laws affect procurement and use of EIT (Electronic Information Technology) • Standard is part of the Rehabilitation Act of 1973 (updated in 1998 in response to internet developments) • Covers federal employees and those seeking information or services from a Federal agency or department

3. What you need to know • Section 508 has a promised update also called a “refresh”. Probably will be finished in 2016. • The United States Access Board is in charge of this refresh • Refresh has taken years with no real end in sight • When refresh is finished the law should look a lot like WCAG (W3C)

4. What is WCAG? • WCAG (Web Content Accessibility Guidelines) is internationally used; developed over multiple years by many people using the W3C (world wide web consortia) process • WCAG 2.0 is the current version • Level A and Level AA are the goals to reach for website developers • There are many parallels between Section 508 and WCAG

5. What is included in the law? • Procurement . Also, development, maintenance and use of electronic and information technology (EIT) • Buy, lease, use EIT that everyone can access • Effort counts – try to get the best product. Document it. Get a waiver if all is not well.

6. VPAT • Voluntary Product Accessibility Template (VPAT) • Documentation from the software creator/ vendor explaining how well their product conforms to the Section 508 standard • ALWAYS ask for a VPAT when buying an EIT product • ALWAYS read the VPAT • Test against the VPAT. Trust but verify.

7. Does the VPAT make sense? • VPAT tracks to the Section 508 standards • Depending on the EIT involved some of the sections will not be relevant • Developer/ vendor declares individual standards, “Complied”, “Not complied” or “Not applicable” • Could use: “Success”, “Fail” or “Not applicable” • If the standard is mostly ok then it might say “Success with Exceptions”; then explain

8. Sample snippet of a VPAT

9. Ask Vendor more Questions • If the VPAT raises additional questions then ask. • Now. Before the sale is made. No time will be better.

10. 1194.21 Software applications and operating systems • Keyboard only use • Software will work with browser, OS (Operating System) and/or AT (Assistive Technology) turned on Example: browser in high contrast mode works • Focus shows for all screen elements • Name, state and status of all screen elements shall be made known to AT

11. 1194.21 -- two e) Label all identical bitmaps the same way so that AT can convey the same meaning to user no matter where they are in the application/ software. • Example: all printer icons are the same throughout the application • Example: if you use a book icon to mean “bookmark” it is always used for that meaning

12. 1194.21 -- three f) All text, including its attributes and caret location on a page should be available to AT g) User should be able to select contrast and colors without objection from program h) Where there is animation there is also another way to understand it i) Don’t use color coding as the only way to convey information

13. 1194.21 -- four j) User can adjust color and contrast settings within a wide range k) No flashing or blinking text/ objects with a flash or blink rate greater than 2Hz and lower than 55Hz l) Electronic forms allow people with AT to access information, fill out all field elements and do everything necessary to complete the form on their own

14. 1194.22 Web-based intranet and internet information and applications a) Alt text for every non-text element (picture, graphic, table, form) b) Multimedia presentations with equivalent alternatives should be synchronized c) Information should not be conveyed by color alone d) All web pages should be readable without a style sheet

15. 1194.22 -- two e) Server-side image maps should include redundant text links f) Client-side image maps are preferred over server-side image maps unless regions cannot be defined with available geometric shape g) Data tables should have row and column headers

16. 1194.22 -- three h) Any data table with two or more logical rows or column heads needs markup to make clear where data belongs i) Frames should be titled with individual and meaningful titles j) Pages should not flicker with frequencies greater than 2Hz or lower than 55 Hz k) Text only pages can be used to provide equivalent information

17. 1194.22 -- four l) All scripts run on pages should be sure to share information with AT m) When a plug-in or applet is necessary to access data on a page there is a link provided to download that plug-in n) Forms - all online forms should be accessible to AT for filling out all fields and submitting the forms

18. 1194.22 -- five o) Skip links provided p) When a timed response is required, user should be alerted and allowed to add more time

19. 1194.23 Telecommunications products • Text Telephones (TTYs) and similar products and the functions that they perform – convert acoustics to text for consumption by equipment accessible to people who are deaf or hard of hearing • Other sections of 1194.23 pertain to physical interfaces and controls where the purpose is to minimize the amount of strength or force it takes to activate and use them. Purpose is to allow access for those with compromised strength and mobility

20. 1194.23 Telecommunications products -- two • Not applicable to websites • For our purposes this part of Section 508 can be ignored, unless you are involved in purchase of a new phone system

21. 1194.24 Video and multimedia products • Training/informational video/multimedia productions should have open or closed captions IF speech or audio information is part of the original information • Training/ informational video/multimedia productions containing visual information should be audio described

22. 1194.24 -- two • Display or presentation of alt text or audio description should be user selectable

23. Don’t memorize • Understand how to comply to make content accessible • Stick to the basics: alt text, make written materials accessible to blind/ low vision and audio materials accessible to deaf/ HOH (Hard of Hearing) • Make sure people who use different input and output methods (keyboard only, Dragon Naturally Speaking, etc) can access your materials • Train all staff to sensitivity on the subject

24. 1194.25 Self contained, closed products • Products with embedded software which are difficult to attach or install AT on. Examples: information kiosks, copiers, printers, fax machines • May pertain to procurement, but not to websites and document development

25. 1194.26 Desktop and portable computers • Hardware used to access software. • Pertains to procurementof items like keyboards, mouse, desktops, laptops, touch screens (which must have some provision for recognition of functionality for non sighted persons)

26. 1194.31 Functional performance criteria Use these criteria to evaluate IF none of the 1194.21 – 1194.26 criteria seem to apply to the item you are evaluating. a) Provide at least one method of operating website and retrieving information that can be accessed by AT (Assistive Technology)

27. 1194.31 -- two • b) If user’s vision is less than 20/70 provide at least one way they can access the information (Examples: audio or enlarged print) • c)Provide at least one way for users who are deaf/ HOH (Hard of Hearing) to access information

28. 1194.31 -- three d) At least one mode of operation and information retrieval provided for these three conditions 1) Audio information important 2) Can be used without user speech 3) Fine motor control, reaching or strength not necessary

29. 1194.41 Information, documentation and support a) End users should have product support information available in alternative formats upon request. No extra charge allowed. b) Accessibility and compatibility features of products info should be available in alternative formats. No extra charge allowed. c) Support services for products available depending on communication needs of end users with disabilities

30. Coming up • Eventually Section 508 refresh will happen. Most current information suggests 2016 (public comments ended May 2015) • WCAG 2.0 Level A & AA will be rolled into that refresh. Be familiar with both. • The principles of accessibility are common to both

31. Resources for Developers • Section 508 – web accessibility • Section 508 – guide to the standards • WebAIM • WAVE toolbar for FF • WAT toolbar for IE • Comparison between Section 508 and WCAG 2.0

32. More resources • Steve Faulkner from The Paciello Group • Karl Groves and tenon.io • VPAT template • Accessing Higher Ground – Westminster, Nov 2015 • Powermapper: run websites against Section 508

33. Connect • Elianna James • ‘I Break Websites LLC’ • eliannaj@yahoo.com • 720-425-1001