Stephen Bouikidis, Avoiding the Target Trap: Creating Accessible Section 508 Compliant Content


Published on

Published in: Technology, Design
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Stephen Bouikidis, Avoiding the Target Trap: Creating Accessible Section 508 Compliant Content

  1. 1. Welcome Stephen Bouikidis Executive Vice President NetReach
  2. 2. Today’s Topics • Key Elements of Section 508 • Who Needs to Comply • Legal Implications of 508 • Useful Resources
  3. 3. Key Elements of Section 508
  4. 4. Enacted in the 1998 Workforce Reinvestment Act to provide accessible content to people with disabilities
  5. 5. Priorities (W3C) • [Priority 1] – A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents. • [Priority 2] – A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents. • [Priority 3] – A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.
  6. 6. Websites must satisfy the following 16 specific items for web accessibility
  7. 7. 1. Offer Text Equivalents A text equivalent for every non-text element shall be provided (e.g., “alt”, “longdesc”)
  8. 8. 2. Present Synchronized Multimedia Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
  9. 9. 3. Remain Independent of Color Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. For example, use a “strong” tag as well as color to convey emphasis of a word or phrase.
  10. 10. 4. Stay Independent of Style Sheets Documents shall be organized so they are readable without requiring an associated style sheet. For example, do not replace structural elements of HTML like headings, paragraphs and lists.
  11. 11. 5. Provide redundant links for server-side maps Redundant text links shall be provided for each active region of a server-side image map.
  12. 12. 6. Use client-side image maps Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
  13. 13. 7. Label row and column headers Row and column headers shall be identified for data tables.
  14. 14. 8. Use the headers attribute in complex tables Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
  15. 15. 9. Supply Frame Titles (attributes and elements) Frames shall be titled with text that facilitates frame identification and navigation. NOTE: Use of frames is not advisable. Impacts on the usability of the site and can often create confusion.
  16. 16. 10. Reduce Flicker Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2Hz and lower than 55 Hz.
  17. 17. 11. Offer a text-only alternative (LAST Resort) A text-only page, with equivalent information or functionality, shall be provided to make a Web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
  18. 18. 12. Write accessible scripts When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology. E.g.- hidden content exposed with JavaScript, such as a mouse over. If turned off, is there an alternative way to link?
  19. 19. 13. Specify Accessible Applets and Plug-ins When a Web page requires that an applet, plug- in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21 (a)(1-11). E.g.-include a link to the plug-in such as Adobe Acrobat.
  20. 20. 14. Design Accessible Forms When electronic forms are designed to be completed online, 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.
  21. 21. 15. Offer Skip Navigation A method shall be provided that permits users to skip repetitive navigation links.
  22. 22. 16. Alert Users to Timed Responses When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
  23. 23. Who Needs to Comply?
  24. 24. • Any US Federal Website (.GOV) • Any vendor who provides information to federal sites
  25. 25. Section 508 does not apply to: • The private sector* • Agencies or establishments using federal funds * currently being challenged
  26. 26. Legal Implications of 508 Target, AOL, Southwest Airlines, Ramada, B&N,
  27. 27. Who Should Comply?
  28. 28. Everyone* * If you know what’s good for you
  29. 29. 9 Good Reasons to Make your Websites Compliant
  30. 30. • You could be non- • It enhances corporate compliant with various image and brand laws. • It reduces corporate risk • It’s the right thing to do • It’s not just about people • It increases market size with disabilities • It addresses the aging • It improves SEO and population Usability. • My mother made me do it!
  31. 31. Examples
  32. 32. Useful Resources
  33. 33. • Cynthia Says- ( test your sites for Section 508 Compliance • Section official Section 508 site; access to tools and resources available • Section 508 Tutorial- ( nice tutorial on making your sites 508 compliant • Access Board ( developers of Section 508 standards • World Wide Web Consortium Web Accessibility Initiative- ( Collaborators and developers of accessibility guidelines
  34. 34. Any Questions?
  35. 35. Thank You! Stephen Bouikidis Executive Vice President NetReach; 215-283-2300, ext. 147 To sign up for our next newsletter which focuses on Section 508, and more section 508 information please give me your business card or email me!