Liberated Accessibility

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

description

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

Transcript of Liberated Accessibility

Page 1: Liberated Accessibility

Liberated Accessibility

Christian Heilmann | http://wait-till-i.com | http://twitter.com/codepo8

A-Tag, Wien, November 2008

Or: Why isn’t anybody listening?

Page 2: Liberated Accessibility

Hello there...

Page 3: Liberated Accessibility

I’m Chris.

Page 4: Liberated Accessibility

“International Developer Evangelist”

at Yahoo.

Page 5: Liberated Accessibility

Author of several books, including the JavaScript

chapter of “Web Accessibility”.

Page 6: Liberated Accessibility

I spend a lot of time on conferences.

Page 7: Liberated Accessibility

And I am sick of seeing accessibility being treated as

the redhead stepchild at conferences.

Page 8: Liberated Accessibility

People talk about “the cloud”, “the semantic web”

or what marvels and wonders CSS3 will bring and the room

are packed...

Page 9: Liberated Accessibility

...and attendees are inspired, blog and write about it and

generally go nuts.

Page 10: Liberated Accessibility

However, even if there is an accessibility talk (which is

seldom enough), things look different.

Page 11: Liberated Accessibility
Page 12: Liberated Accessibility

Why is that?

Page 13: Liberated Accessibility

Accessibility has a bad reputation as a topic for

conferences.

Page 14: Liberated Accessibility

This is mostly our own fault.

Page 15: Liberated Accessibility

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

Page 16: Liberated Accessibility
Page 17: Liberated Accessibility

The most common accessibility talks are:

Page 18: Liberated Accessibility

The consultant, explaining that accessibility is the law and that you will get sued if

you don’t follow the guidelines.

Page 19: Liberated Accessibility

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).

Page 20: Liberated Accessibility

The web designer telling people that when you want

to be accessible, you need to change your design

drastically.

Page 21: Liberated Accessibility

We sell accessibility as a gigantic problem.

Page 22: Liberated Accessibility

Lots of bloggers make the same mistake.

Page 23: Liberated Accessibility

And that creates a bad example

Page 24: Liberated Accessibility

To threaten people with laws is pointless.

Page 25: Liberated Accessibility

Two weeks ago I was in Sao Paulo, Brazil.

Page 26: Liberated Accessibility

They have a law that you need to check if the lift

arrived before you enter it.

Page 27: Liberated Accessibility
Page 28: Liberated Accessibility

Sweden had a similar issue, but coped with it in a different manner – by

showing you the consequences.

Page 29: Liberated Accessibility
Page 30: Liberated Accessibility

You cannot change the web by dragging people to court

or threatening with law suits.

Page 31: Liberated Accessibility

Someone with the same family name as me learnt

that the hard way last week.

Page 32: Liberated Accessibility

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

Page 33: Liberated Accessibility

What we need are positive examples in a language the

target audience understands.

Page 34: Liberated Accessibility

I already started with some of them.

Page 35: Liberated Accessibility
Page 36: Liberated Accessibility
Page 37: Liberated Accessibility

Collaborating with designers.

Page 38: Liberated Accessibility

Others also show the way it should be done.

Page 39: Liberated Accessibility

Last week at Paris Web in Paris, France:

Page 40: Liberated Accessibility

Praesentation by Aurelien Levy and Stephane

Deschamps.

http://www.flickr.com/photos/pascale_pictures/3034691276/sizes/o/

Page 41: Liberated Accessibility

Other steps toward accessibility world domination:

Page 42: Liberated Accessibility

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

Page 43: Liberated Accessibility

Instead of simply demanding that a certain idea should be followed, show why using real life examples.

Blackberries suck with JavaScript and are used by a *lot*

of managers.

Page 44: Liberated Accessibility

Most of all it is time that we realise that web

development is constantly changing and evolving.

Page 45: Liberated Accessibility

Web DevelopmentAccessibility

“You need Jaws and Internet

Explorer 5”

“Everybody has Flash and

JavaScript and we are almost ready to ditch

IE6!”

Page 46: Liberated Accessibility

Using Firefox, Firebug and GreaseMonkey I can access

and fix any web site.

Page 47: Liberated Accessibility

And all of these are free!

Page 48: Liberated Accessibility

Developers love to play with technology and create

something cool and new all the time.

Page 49: Liberated Accessibility

The results are always interesting, but not always

useful.

Page 50: Liberated Accessibility

The prime number shitting bear.

http://alpha61.com/primenumbershittingbear/

Page 51: Liberated Accessibility

We have a lot of real problems of real people that

need solving.

Page 52: Liberated Accessibility

Developers have the time and dedication to fix those.

Page 53: Liberated Accessibility

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

other ideas...

Page 54: Liberated Accessibility

...rather than talking in parallel.

Page 55: Liberated Accessibility

So...

Page 56: Liberated Accessibility

We need much more information about assistive

technology that is open source.

Page 57: Liberated Accessibility

We need to work with web developers and not stop them

from evolving.

Page 58: Liberated Accessibility

Assistive technology has to become cheaper and much

easier to use and install.

Page 59: Liberated Accessibility

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

Page 60: Liberated Accessibility

Developers need to get more *real* and *up to date*

information about accessibility.

Page 61: Liberated Accessibility

In the channels that developers use and read...

Page 62: Liberated Accessibility

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

Page 63: Liberated Accessibility

Shared Items in Google Reader.

Page 64: Liberated Accessibility

Bookmarks in Del.icio.us.

Page 65: Liberated Accessibility

Large groups on Facebook.

Page 66: Liberated Accessibility

What we need are inspiring presentations, videos and

podcasts.

Page 67: Liberated Accessibility

Here’s an example.

Page 69: Liberated Accessibility

Well then, ladies and gentlemen..

Page 70: Liberated Accessibility

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

want.

Page 71: Liberated Accessibility

Christian Heilmann

http://scriptingenabled.org | http://wait-till-i.com

twitter/flickr: codepo8

Thanks!