The document discusses inclusive development and accessibility in website design. It notes that websites should be accessible to all audiences, including those with disabilities, as inaccessible sites exclude users and limit their reach. It outlines different types of disabilities that may impact accessibility like visual, mobility, hearing and cognitive impairments. The document provides guidance on how to design accessible websites by following standards like W3C, using responsive design, and validating websites for accessibility issues. It recommends tools for validation and testing accessibility.

1. Inclusive development: some notes
Kaido Kikkas
Associate professor
Estonian IT College / Tallinn University
Garage48, November 2014

2. Why?
● The website that nobody can access has no
point at all
● The website that 10% of audience cannot
access has 10% less point than it should
● (plus, Mom told that we all should play nice!)

3. Who?
● People with different disabilities
– Visual impairments
– Mobility/coordination impairments
– Hearing impairments
– Cognitive impairments
● The axiom of accessibility – things that are
created accessible are friendly overall

4. How?
● Follow the standards (W3C)
● Responsive web design
● Accessibility considerations
– http://www.w3.org/TR/WCAG20/
– WAI ARIA (see text and links at
https://en.wikipedia.org/wiki/WAI-ARIA)

5. With what?
● W3C validator (http://validator.w3.org)
● WAVE (http://wave.webaim.org/)
– Toolbar (http://wave.webaim.org/toolbar/)
● Google Chrome Accessibility Developer
Tools (A Damn Long URL in Chrome Apps)
● Text-based browsers (Lynx etc)
● ...

6. Good luck!
These slides @ Slideshare:
http://www.slideshare.net/UncleOwl
Inquiries/questions: kakk@kakupesa.net

7. Good luck!
These slides @ Slideshare:
http://www.slideshare.net/UncleOwl
Inquiries/questions: kakk@kakupesa.net