This presentation uses an out-of-the box HTML slideshow script which by itself is unaccessible. Keybindings exist to traverse forward and backward with
arrow keys, but focus never shifts as the slides advance. The slides
themselves are well structured, so you can use a read all command to listen to everything linearly.
My good buddy Karl Groves also added a live region which should work well for screen readers that support live regions. As you
traverse through the slides using arrow keys, the slide's content will be added to the live region.
Things I Wish I Knew When I Started in Digital Accessibility
A canoe is shown paddling through a garbage so thick you can not see the water.
Don't dump it all on the developer
If the developer is the first person to mention accessibility, you've messed up.
Boss from the movie "Office Space" talking to employee:
Yeah... we're going to have to ask you to make that accessible.
Accessibility is not a checklist
It is a goal
Start with the basics
Code to standards
Semantic code goes a long way
Pay attention to keyboard interaction
Not just a bridging technology anymore
Familiarize yourself with WAI-ARIA design patterns
Always Test Your Work
Don't forget the APIs
We must remember how important the relationship is between the DOM, the API, and the AT
A browser might support an element, but does it's accessibility API also support it?
The browser needs to pass through the necessary info to the AT in order for the AT's support for it to work
The DOMThe APIThe AT
The background image is a motion gif of the three stooges fighting to represent a breakdown between the DOM, the API, and Assitive tech.
The tools of the trade
There are a number of free tools available for testing. Whether they are testing tools to find errors, or assistive technology that will help you understand how your code is interpreted, there is no excuse not to use them.
We've now discussed the client, the vendor, the project managers, the designers, and the developer. One common feeling was present with all these groups when they were dealing with Accessibility for the first time.
A background image is shown here of a wheel of fortune style puzzle. The hint is "common feeling" and the partially solved puzzle shows "F--- Accessibility".
The solved puzzle is "Fear Accessibility".
We are not an angry mob.
We have built a culture of fear surrounding accessibility. We need to focus on the positives and not the negatives.
Don't be ana11y thug.
Stop attacking what people have done wrong. Lead with what they've done right and encourage them.
The chain of demand
In which the need for accessibility is compounded by fear as it makes it's way down.
The client hears word from a user that their product is inaccessible
Now has to deal with a panicking client.
Now have to deal with their bosses.
Gets this dumped on him.
If you build it, they will come...
...and bitch about everything you got wrong.
Then complain about it on the world's largest bug tracker...
Those who support it
Welcome! ... You're gonna have a good time!
a swiss army knife with a riduclous amount of options is shown to demonstrate how useful a tool the a11y community can be.
Some tin cans joined by strings are shown to demonstrate how difficult it would have been to share information before twitter and other social networks.
We work tirelessly, the end goal is to put ourselves out of work. Events like camps or CSUN can be a great refresh or reboot to help us remember how important our work can be.
We may not have all the answers.
Liam Neeson shown from the movie "Taken". Context is that he is talking on our behalf to those who ignore accessibility.
What we do have is a particular set of skills.
Skills we have acquired over very long careers.
Skills that make us a nightmare for people like you.