How We Use The Web – Session 2 at Access U
Presenter: Geoff Stevens.
He did want a room with student computers. The session will focus on screen readers.
Likes to focus on the fact that not everyone does something the same way. Believes at least if we focus on universal accessibility, then let things come out in the wash.
this year, will focus on screen reader features, how people use the tool.
Didn’t create a powerpoint for us to get a better sense of what he goes through: no visuals. Will provide references at the end.
Uses a laptop computer with JAWS8. [he brought his own, he was supposed to have JAWS installed on the PC here, but it wasn't]. Also has an accessible PDA, uses Windows Mobile OS, has a screen reader (codefactory). Also has a braille printer and scanner with OCR software.
AnnualCreditReport
“link graphic image contact us btn” (btn was basically a grunt)
“visited link graphic….” — JAWS has an ability to bring up visited links.
CAPTCHAs are inaccessible. Some companies use audio, but it’s garbled, because they are worried about people using speech recognition software. MySpace is inaccessible. Google used to, fixed it.
Sometimes there are benefits to tables for layout — may be easier than 40 nested lists.
Gmail
form focus to username input. I asked if that was difficult, but he said it depends on the purpose of the page. For this page, generally you just want to log in.
CAPTCHA still very difficult to use.
Alternatives: challenge questions. But often these are social/cultural.
He thinks we should fix what we’ve come up with, rather than explore different things.
senate.gov
try to find senator — JS attached to “go” link.
IF YOU ARE GOING TO MAKE A FORM, USE REAL BUTTONS. I THINK YOU CAN ACHIEVE MOSTLY THE SAME THINGS.
He can use JAWS to do what he needs, but he needs to use a different JAWS function, and the button doesn’t announce that it needs that. Dont want to say JS is bad, but it needs some planning.
Got a volunteer to try JAWS:
amazon
JAWS — move to edit (“E”)
“ENTER” – forms mode
Virtual representation of page being used until you turn on Forms mode.
There isn’t alot on this page to help screen reader users (headers, etc). If you need to, you can figure out how to use it. You can actually use JAWS to add labels/images that aren’t properly marked up. You can navigate to divs, form fields, links list…
Question: do you design for the least common denominator?
Links List: CapsLock>F7.
Can use the first letter to get to the element you want. Can also set to only show unvisited links. Can also sort in tab or alphabetical order. What you miss with links list is the text between the links. Can activate link, or move to it (to get context)
(ESC to cancel)
Headings: CapsLock>H
Logical vs Physical Design:
if it’s logical to use headings, do so. Amazon — search terms is H1, but its not located directly before the content.
Options:
ignore Iframes — to ‘avoid advertising’
indicate lists – on/off
detect table type
Access Keys:
loves access keys on apps he will return to, especially on buttons, checkboxes. (JAWS can read them out)
Pitfall: screen reader uses so many keystrokes itself.
Roadrunner site — flash, totally inaccessible
Acronyms/abbreviations.
Efficiency is important. More syllables = more time. He worked for a company that wanted TCB read out as “Texas Commission for the Blind”. He fought that.
Other disabilities:
Speech recognition is getting better, but there are still problems. Hear about dragon: naturally speaking a fair amount.
Mobility impairments can use dragon, but there is a learning process.
There are also one-handed keyboards: limitations on keystrokes.
Questions:
– he likes JAWS, because he uses it most. An org will probably go with a single provider. Freedom scientific marketed itself to educational providers, successfully.
his email: geoffste@gmail.com
“how to optimize JAWS to use our app” – ok idea, but can be dangerous. Needs to be accessible with default settings — if not, why not? Biggest problem is that people don’t have enough knowledge to use all the settings it provides.
