WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: training sr users for the modern web (wasIntuitiveness of JAWS jump to tabpanel shortcut for ARIA Tabs in FF??

for

From: Stanzel, Susan - FSA, Kansas City, MO
Date: Jul 10, 2014 7:28AM

I follow this list, but I probably don't have as much training for the modern web as I need. I use JAWS 15. Where can I get this necessary training. There was a webinar from JAWS, but it was a long time ago.

Susie Stanzel

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Sailesh Panchang
Sent: Monday, July 07, 2014 9:57 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] training sr users for the modern web (was Re: Intuitiveness of JAWS jump to tabpanel shortcut for ARIA Tabs in FF??

I believe the problem is introduction of new UI controls like tabs, menus, slider control etc. that are implemented differently on different websites / Web apps with varying levels of accessibility or none at all.
The lack of uniform support for these using different combinations of browsers and SRs (or assistive technologies in general) does not make it easier for users.
For instance, tabs can be implemented simply by using HTML, JavaScript and CSS in which a tab is a link also exposed as a tab.
Eg. http://www.health.govt.nz/yourhealth-topics/diseases-and-illnesses/heart-disease/angina
(Check out Summary, Symptoms, Treatment, etc.). This works and is usable but strictly, every link is a tabstop ... not just the selected tab.
And then one can use ARIA to markup tabs too. When done right only the selected tab is a tabstop and one can arrow across. Here again sometimes simply arrowing makes the current tab active and sometimes one has to use the space / enterkey to make it active.
Well one can navigate by headings or images or pull up a list of links but cannot do so for tabs or menus and the like.
There's no compulsion that tabs and menus should be within a navigational landmark so their discovery is often a problem.
And when landmarks are used inconsistently or only the navigation and contentinfo are marked up as landmarks for instance but not the main or search regions, an SR user cannot simply rely on landmark navigation to discover and navigate to content.
Regards,
Sailesh


On 7/7/14, Tim Harshbarger < <EMAIL REMOVED> > wrote:
> What I find interesting about this situation is that typically if you
> ask someone using a screen reader to interact with a tab panel on a
> desktop application, they know what to do. But present the same UI on
> a web page and they seem to have difficulty figuring out how to
> interact with the tab panel.
>
> I definitely think part of that has to do with the non-existent to terrible
> keyboard interactions that are implemented on the web. I also agree that
> some of it has to do with the training. I think most of the time we
> still tend to present the web and desktop as 2 different things to the
> user when in reality we keep trying to make them more and more identical in reality.
>
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R.
> Gunnarsson
> Sent: Friday, July 04, 2014 8:07 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] training sr users for the modern web (was Re:
> Intuitiveness of JAWS jump to tabpanel shortcut for ARIA Tabs in FF??
>
> I think this project is something that is absolutely vital to the
> increased functionality of the modern web; one which has been somewaht
> niglected by a lot of us.
> When you work with testing, code and screen reader compatibility all
> day, you sometimes forget about the ultimate purpose, which is to
> enable end users of all abilities (not just blind/vi users) to
> interact with, and use, the web.
> Part of that is inevitably to teach end users waht to expect,
> especially when it comes to the more advanced widgets used.
>
> Me and my colleague had a very aggressive project lined up a year ago
> called Cognosco. Its purpose was to creae interactive online tutorial
> on using the web with screen readers and other assistive technologies
> using a combination of text, videos and online sample pages.
> Unfortunately we work on two continents in two unrelated jobs, and the
> funding we had been promised in the spring of 2013 was not delivered
> in the fall, so we had to make the painful decision to put that
> project on ice.
>
>
> On 7/4/14, Jennison Mark Asuncion < <EMAIL REMOVED> > wrote:
>> On 7/4/14, Léonie Watson < <EMAIL REMOVED> > wrote:
>>> Discovery is possibly the biggest challenge. It isn't helped by the
>>> fact that little changed on the web for a long time, so people
>>> rarely had to figure out new forms of interaction. Screen readers
>>> don't explain how to use links for example.
>>
>> Léonie,
>>
>> Your comment gave me an opportunity to raise an issue that I've been
>> informally discussing with folk for a while now - while we are all
>> implementing the best solutions possible to make the modern web
>> accessible, I am convinced that there exists a training gap for the
>> average screen reader users (who are not on this list, monitoring
>> twitter, etc.) when it comes to interacting with web apps and their
>> associated design patterns.
>>
>> I would be curious to hear from anyone who conducts screen reader
>> training to blind end-users about this topic.
>>
>> Jennison
>> >> >> list messages to <EMAIL REMOVED>
>>
>
>
> --
> Work hard. Have fun. Make history.
> > > list messages to <EMAIL REMOVED>
> > > list messages to <EMAIL REMOVED>
>
This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.