This document provides an overview of how to improve the accessibility of a website without making it overly complex. It begins by defining web accessibility and its importance for people with disabilities. It then addresses common questions about accessibility and provides resources on getting started, following guidelines, and ensuring usability. The key messages are that accessibility should be considered from the beginning, not as an afterthought, and that it leads to a better user experience for all while allowing a website to reach more people.

1. Howto Improve
Your Website’s Accessibility
Without Going Crazy
Eric Eggert
ee@w3.org • yatil
W3C/Web Accessibility Initiative

5. – w3.org/accessibility
The Web is fundamentally designed to work for
all people, whatever their hardware, software,
language, culture, location, or physical or mental
ability. When the Web meets this goal, it is
accessible to people with a diverse range of
hearing, movement, sight, and cognitive ability.

6. Accessibility:
Make sure that People with disabilities
can effectively interact with the Web

7. – Aaron Gustafson (Foreword in: Sarah Horton. “A Web for Everyone.”)
“On the web, every decision I make can have a
profound effect on hundreds of thousands (if not
millions) of people’s lives. I can make checking into
a flight a breeze, or I can make it a living hell.
That’s a lot of power. And to quote Stan Lee: ‘With
great power comes great responsibility.’”

8. >1 billion
Persons with some form
of disability
— WHO Report 2011

9. 15%
Persons with some form
of disability
— WHO Report 2011

10. @dstorey

11. People
Accessibility
Usability
People

12. users is People

13. Q: How do
People With Disabilities
Use the web?

14. Browser Web
Content

15. Browser Web
Content
Assistive
tech

16. Zoom

17. Pinch Out by Julie Muckensturm from the Noun Project

19. Single Switch

20. Braille

21. customizations

22. Captions

23. Resource:
How People with
Disabilities Use the Web
w3.org/WAI/intro/people-use-web/

24. Q: Accessibility sounds
complicated.

25. Q: How do I start with
Accessibility?

26. Designers
Content creators
Developers

32. Resource:
Tips for getting started
with web accessibility
w3.org/WAI/gettingstarted/tips/

33. Q: How do I make sure my
website is accessible?

34. Resource:
Web Content
Accessibility Guidelines
(WCAG) 2.0
w3.org/TR/WCAG/

35. Principles:
Perceivable
Operable
Understandable
Robust

36. Perceivable:
Meaningful Sequence

37. Perceivable:
TextAlternatives

38. <button>
<span class="icon icon-pencil">
</span>
</button>

39. <button title="Edit">
<span class="icon icon-pencil">
</span>
</button>

40. <button title="Edit">
<span class="icon icon-pencil-kaput“>
</span>
</button>

42. ImageS

43. <button>
<img src="pencil.png" alt="Edit">
</button>

44. <button>
<img src="pencil.svg" alt="Edit">
</button>

45. Resource:
Image Tutorial
w3.org/WAI/tutorials/images/

46. Resource:
Web Accessibility
Tutorials
w3.org/WAI/tutorials/
<aside>

47. Page structure (Draft)
Menus (Draft)
images
Tables
forms
carousels (Draft)
</aside>

48. Visible text labels

49. <button>
<span class="icon icon-pencil">
</span>
Edit
</button>

50. Perceivable:
Color Contrast

51. Operable:
usable with a Keyboard

52. Operable:
Ability to bypass
blocks

53. Operable:
Proper headings
F labels

54. Understandable:
Page language

55. Understandable:
Consistent Navigation

56. Understandable:
Indicate errors

57. Robust:
Compatibility

58. Q: How do I make sure
that the
user experience is
accessible?

59. You achiEve the best
results when…

60. Accessibility is
not an afterthought

61. Smooth use of your
product

62. Everything feels
coherent

63. No compromises

64. No need to rebuild

65. Accessibility is
an opportunity

66. Reach more people

67. makes your web project
easy to understand

68. consistent layout H
Navigation

69. Accessibility is
A creative outlet

70. Produce the best
video player UI

71. Consider the order of the
content

72. Take the available data
and do something no one
expects

74. thankyou.
Eric Eggert
W3C/Web accessibility initiative
ee@w3.org & @yatil