We’d like to introduce you to Lisa Herrod, Principal User experience Consultant at Scenario Seven and expert in UX for Deaf users. We hope that Lisa’s presence at the conference this year will draw more attention to the needs of Deaf web users who are often overlooked even by those us that understand accessibility. Here, Lisa sets the record straight. Lisa will be running a low cost workshop on the 21st September and presenting at Accessibility 2.0 on the 22nd September. Oh, and like Kath Moonan, she’s a keen whippet fancier!

How long have you been an interpreter and what made learn to sign?

Ironically, I was initially interested in becoming a speech pathologist!  Around ‘93 someone recommended I read Oliver Sacks‘ “Seeing Voices” an amazing book that anyone working in education, employment or accessibility should read. I started signing regularly around 1994 and moved into interpreting around the end of 1995. I haven ‘t worked in a professional capacity as an interpreter since about 2003, so my Auslan (Australian sign language) skills have really slipped from what they were when I was interpreting 40 hours a week, which really saddens me.

Why is there such a lack of information about Deaf and hard of hearing web users?

I think a lot of it has to do with the fact that people tend to group deaf, Deaf and Hearing Impaired users into one big group of people who “just can’t hear. Most of us know someone that has diminished hearing through age or industrial damage, noise etc. But few of us understand Deafness from a cultural, linguistic perspective, i.e. from the perspective of those Deaf who use sign language as a first language and may not be fluent in English as a second language.

Is it true that If a website doesn’t have any rich media such as audio or video content then there’s no need to worry about access for Deaf and hard of hearing users?

No that’s only partly addressing the issue. Once you start to understand that we’re talking about providing content to an audience who speaks another language all together, then it starts to become a lot clearer. Because then you have to start thinking about how you write and how you present content to such an audience.

Can a technical approach to accessibility accommodate Deaf and hard of hearing users?

Look the thing is, when it comes to accessibility we’re talking about *people*. We’re talking about User Experience. We all need to remember that. So while there is definitely some work of a technical nature, I think it’s really important to understand *why* we’re doing these things. Who we are doing it for, and also the fact that there are so many different reasons and manifestations of deafness. Deafness is not a binary thing. People are not just Deaf or hearing. The most unrecognised attribute of Deafness is th fact that many native signers have English as a second language.

Why should web teams come to your workshop?

I think my last point above is the most compelling reason. We’re not just talking about people who can’t hear. We’re talking about people who speak a completely different language. One that is visual, spatial, grammatically different. It’s much more involved than simply captioning a video.

Anything else you’d like to add?

I’d really like to encourage people to come to the workshop. In the past ten years I’ve worked on the web, despite the number of really smart, engaged, interested people I’ve met working in web accessibility and user experience, I have never met a single person who actually understood the difference between deafness from a medical perspective and Deafness from a cultural perspective, the different approches required for each group and the reasons why. From an ethnographic perspective, Deaf culture and web accessibility really hasn’t been explored much. So if nothing else, come along and learn something new.

Follow Lisa on Twitter: @scenariogirl

We just don’t think there’s enough information out there about how Deaf and hard of hearing people use the web. Okay, many of us know about adding captions to video and providing audio transcripts but what about when we scratch under the surface and really try to understand the needs of this group?

It’s a bit of a problem in the field of web accessibility that there tends to be too much focus on screen reader users. This has come about because screen reader users can experience such a high level of frustration and difficulty when surfing the web and even more when using complex web applications. Accomodating screen reader users by Including alt text for graphics and buttons is the first checkpoint of the WCAG and often the first thing people discover when they first come across web accessibility. This primary position might also be what re-enforces a point of view that screen reader access needs are the only type of access needs site owners really need to worry about.

We’re not saying stop ensuring good usability for screen readers but we are saying let’s ensure other types of impairment are also considered. One of the most exciting things about taking a pan impairment approach to web accessibility is when a pattern emerges across groups with entirely different access needs. That means easy cherry picking of what might be a long and expensive bug list after a test with diverse users.

We’ve invited Lisa to host a workshop for us on Deaf Awareness for Web Teams on the 21st September as well as present at our main Accessibility 2.0 conference the next day. We hope that Lisa’s workshop will raise awareness across the industry and take the focus away from coding and the technical side of web accessibility.

We’ve kept the workshop as low cost as possible because we want as many web editors, designers, developers, user experience architects and information architects to attend.

It’s just a couple of hours out of your week and a few quid out of your pocket and it might be one of those precious moments that change the way you think about the web forever.

Be there!

Kath Moonan

Follow Kath on Twitter @ladymoonani

Follow Accessibility 2.0 on Twitter @millionflowers