My presentation at the A-Tag in Vienna about lack of communication between the development and the accessibility world.

1. Liberated
Accessibility
Or: Why isn’t anybody listening?
Christian Heilmann | http://wait-till-i.com | http://twitter.com/codepo8
A-Tag, Wien, November 2008

2. Hello there...

3. I’m Chris.

4. “International Developer
Evangelist”
at Yahoo.

5. Author of several books,
including the JavaScript
chapter of “Web
Accessibility”.

6. I spend a lot of time on
conferences.

7. And I am sick of seeing
accessibility being treated as
the redhead stepchild at
conferences.

8. People talk about “the
cloud”, “the semantic web”
or what marvels and wonders
CSS3 will bring and the room
are packed...

9. ...and attendees are inspired,
blog and write about it and
generally go nuts.

10. However, even if there is an
accessibility talk (which is
seldom enough), things look
different.

12. Why is that?

13. Accessibility has a bad
reputation as a topic for
conferences.

14. This is mostly our own fault.

15. It is very hard to guess how
you really come across and
what people think of you.

17. The most common
accessibility talks are:

18. The consultant, explaining
that accessibility is the law
and that you will get sued if
you don’t follow the
guidelines.

19. The screenreader user
showing lots and lots of sites
that fail to work and
complaining how expensive
Jaws is.
(after spending 20 minutes setting up the reader and the
computer to use for the presentation).

20. The web designer telling
people that when you want
to be accessible, you need to
change your design
drastically.

21. We sell accessibility as a gigantic
problem.

22. Lots of bloggers make the
same mistake.

23. And that creates a bad example

24. To threaten people with laws
is pointless.

25. Two weeks ago I was in Sao
Paulo, Brazil.

26. They have a law that you
need to check if the lift
arrived before you enter it.

28. Sweden had a similar issue,
but coped with it in a
different manner – by
showing you the
consequences.

30. You cannot change the web
by dragging people to court
or threatening with law suits.

31. Someone with the same
family name as me learnt
that the hard way last week.

32. You cannot sell anything by
showing that it doesn’t work.

33. What we need are positive
examples in a language the
target audience understands.

34. I already started with some of
them.

37. Collaborating with designers.

38. Others also show the way it
should be done.

39. Last week at Paris Web in
Paris, France:

40. Praesentation by Aurelien
Levy and Stephane
Deschamps.
http://www.flickr.com/photos/pascale_pictures/3034691276/sizes/o/

41. Other steps
toward
accessibility
world
domination:

42. Instead of
condemning
technologies, show
how they can be
fixed to work.

43. Instead of simply
demanding that a
certain idea should
be followed, show
why using real life Blackberries suck
examples. with JavaScript and
are used by a *lot*
of managers.

44. Most of all it is time that we
realise that web
development is constantly
changing and evolving.

45. Accessibility Web Development
“Everybody
“You need
has Flash and
Jaws and
JavaScript and
Internet
we are almost
Explorer 5”
ready to ditch
IE6!”

46. Using Firefox, Firebug and
GreaseMonkey I can access
and fix any web site.

47. And all of these are free!

48. Developers love to play with
technology and create
something cool and new all
the time.

49. The results are always
interesting, but not always
useful.

50. The prime number shitting
bear.
http://alpha61.com/primenumbershittingbear/

51. We have a lot of real
problems of real people that
need solving.

52. Developers have the time and
dedication to fix those.

53. ...if we talk to them in a
language they understand
and have an open mind to
other ideas...

54. ...rather than talking in
parallel.

55. So...

56. We need much more
information about assistive
technology that is open
source.

57. We need to work with web
developers and not stop them
from evolving.

58. Assistive technology has to
become cheaper and much
easier to use and install.

59. And I am 100% sure that this
will not happen in the
commercial market.

60. Developers need to get more
*real* and *up to date*
information about
accessibility.

61. In the channels that
developers use and read...

62. ...and not only the
“accessibility” publications.

63. Shared Items in Google
Reader.

64. Bookmarks in Del.icio.us.

65. Large groups on Facebook.

66. What we need are inspiring
presentations, videos and
podcasts.

67. Here’s an example.

68. http://www.youtube.com/watch?v=CwsDKaalgq8&
http://www.youtube.com/watch?v=QiuT0y0KR6I

69. Well then, ladies and
gentlemen..

70. ...get off your butts and go
and tell the web what we
want.

71. Thanks!
Christian Heilmann
http://scriptingenabled.org | http://wait-till-i.com
twitter/flickr: codepo8