The document discusses web accessibility, emphasizing the importance of making content usable for individuals with disabilities. It highlights the Web Content Accessibility Guidelines (WCAG) and provides best practices for web developers, including the use of tables, metadata, and unobtrusive JavaScript. The author, Martin Leyrer, stresses that accessibility is an ongoing process rather than a one-time task.

1. Accessible Websites Martin Leyrer

2. Agenda About me

3. What you are not going to hear

4. What is “Accessibility” (a11y)

5. Web Content A11y Guidelines (WCAG)

6. Best Practices

7. Tools

8. Wrap Up and Q&A

9. About Me Martin Leyrer – just “Martin” is fine :)

10. From Vienna, Austria

11. Notes Dev. & Admin. since 1995 (R3.1)

12. Web Developer even longer

13. Work for a large IT service organization

14. One large Client

15. The “NOT” Slide I am NOT a W3C spokesperson

16. I am NOT a WCAG editor

17. I am NOT certifying your site “accessible”

18. No definitive answers, only “best practices”

19. Focus on technical issues

20. What is “Accessibility” Accessibility make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these.

21. Following these guidelines will also often make your Web content more usable to users in general.

22. Accessibility Is More! It's not about the “Disability Discrimination Act 1995” (UK), the “Americans with Disabilities Act of 1990” or any other law.

23. It's not making Websites “uglier”