This is a basic introduction to web accessibility

1. Web Accessibility

2. Web accessibility is for blind people WRONG

3. Web accessibility is for the disabled WRONG

4. Web accessibility is for EVERYONE

5. An overview

6. How are people using your site? Keyboard and mouse?

7. How are these people using your site? Mobile devices

8. How are these people using your site? Alternative input devices

9. Your users are not all the same Is your audience male or female, old or young?

10. Your users are not all the same Your users may be colour blind

11. Your users are not all the same Your users may suffer from epilepsy 3 flashes within one second can cause a seizure

12. Legal requirements Disability Discriminations Act (UK) Section 508 (US) a service provider has to take reasonable steps to change a practice which makes it unreasonably difficult for disabled people to make use of its services. Other legislations in different countries Legal cases Maguire v SOCOG (2000) Target (US) Odeon Cinema (UK) Threat of legal action by RNIB and many other pressure groups against many large companies and organisations if they do not make their websites more accessible

13. Not just a legal thing Enabling more people to use your website increases sales. Enable your brand across a wider range of technologies, and environments An accessible site is generally faster leading to reduced hosting costs An accessible site is generally more search engine optimised leading to increased brand visibility It’s Ethical

14. Accessibility guidelines WCAG 1 & 2 PAS 78 RNIB See it right Not all about checklists

15. Web accessibility means dull, boring websites WRONG

16. Accessible sites can look great too

17. Accessible sites can look great too

18. Accessible sites can look great too

19. Not just people using your website Search Engines don’t care what your site looks like

20. Basic Requirements (single A compliance) PERCEIVABLE - alternatives for non-text content - captioning - transcripts OPERABLE - keyboard navigation - timing of moving content can be adjusted - epilepsy - good semantic code UNDERSTANDABLE - Do not open new windows within pre-warning user - Do not change focus from what is expected - Form input assistance - Error handling ROBUST - good semantic code to withstand different user environments

21. Conformance to WCAG 2.0 Guidelines Each page of the website has to conform for the whole site to achieve conformance Claiming conformance is optional By using the W3Cs logos on your site, you are claiming conformance Do not rely on automated accessibility tools

22. Let real users loose on your website

23. Let real users loose on your website

24. Summary Accessibility is for EVERYONE Use REAL USERS to test your site People use the web in a variety of different ways, and in a variety of environments Accessibility should be an integral part of the whole process, not just a checklist, or an afterthought There’s more than just legal reasons to make your site’s more accessible

25. More information