veyepar: Beyond Alt Text: What Every Project Should Know About Accessibility

Author(s):	Denise Paolucci
Location	MCC6
Date	feb Fri 01	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	1:40:00	Offset	None
End	12:20	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30271/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Beyond_Alt_Text_What_Every_Project_Should_Know_About_Accessibility.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

You know it's important for your web project to be accessible to people who use all kinds of assistive technology to access the internet. But all the guidelines for web accessibility you can find don't go much beyond "make sure all your images have alt text", and all the resources you can find treat "accessibility" as a synonym for "making your site work in a screen reader". You know there are other things you should be doing and other forms of assistive technology you should be accomodating, but all the best practices documents are a complicated morass of contradicting information (if you can find best practices documents at all.)

Have no fear! This tutorial will guide you through the basics of improving web-based open source projects until they work with all kinds of assistive technologies -- and there are more assistive technologies out there than you might think. Together, we'll cover:

* the wide range of assistive technology people use (including things most people wouldn't think of as assistive technology);

* quick demonstrations of what the experience of using assistive technology is actually like (no more guessing about how screenreaders treat elements of a page or how voice recognition software allows for keyboardless navigation);

* common myths about accessibility (and the truths behind the myths);

* "attractive nuisances" (things people think are helping, but actually make the situation worse);

* simple, concrete examples of changes you can make to your site -- right now!

Code samples will be provided, along with basic exercises to reinforce the lessons, so please bring a laptop if you can. You won't leave as an accessibility guru, but you'll definitely leave with a toolkit full of ways you can move beyond alt text.

Comment:

production notes