E-mail List Archives

Re: Using a Mouse with a Screen Reader - further Questions

for

From: Tim Harshbarger
Date: Aug 31, 2017 6:46AM


Sarah,

1. Why is this happening?
You are seeing a difference between explore by touch and swiping because they work differently. When you use a swiping gesture to explore the user interface, screen readers (like Voiceover on iOS or Talkback on Android) work more like a desktop screen reader in document/browse mode. The screen reader navigates the user interface according to how elements appear in the DOM tree. With explore by touch, the screen reader reads elements based on their spatial relationships.

2. What can be done about it?
If spatial relationships convey information, that same information should be conveyed in a manner that is presented when someone navigates the user interface by swiping or using the document/browse mode.

3. Is swiping between elements on a mobile device analogous to the tab order, and touching and moving without lifting one's finger equivalent to using a mouse?
Yes, you could say that. However, while I think Joel presents some good information for why you might also test using a mouse and screen reader, I personally would not bother testing that way--unless I was responding to direct user feedback. Basically, any information that is conveyed visually through spatial relationships should also be conveyed in a non-visual manner as well. While I think you could make a case that explore by touch provides a non-visual way to convey spatial information, I tend to think that it still relies on an understanding of visual spatial relationships and how they work--and I am not sure that is something I would want to assume the user always understands. Instead I would likely stick to presenting that same information either programmatically or via text. On the accessibility of user interfaces every day. I would not consider myself a typical user.

I hope this helps some.

Thanks,
Tim
-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Sarah Jevnikar
Sent: Wednesday, August 30, 2017 9:29 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Using a Mouse with a Screen Reader - further Questions

Hi Joel,
Thanks for your thoughts. I'll try a mouse in the way you suggested and see how it goes. You raise a good point - screen layout has become more important in the age of the touch screen; why wouldn't the same be true of the laptop or pc?

To everyone - I'm curious though with the original problem: the mouse was giving different speech output to the tab key and links list. On iOS, touching the screen and moving my finger around without lifting it gave different results than swiping between elements.

Three questions arise
1. Why is this happening?
2. What can be done about it?
3. Is swiping between elements on a mobile device analogous to the tab order, and touching and moving without lifting one's finger equivalent to using a mouse?

Thank you so much
Sarah

Sarah Jevnikar

Accessibility Consultant

Digital Echidna

p: 519-858-4438 ex. 211
e: <EMAIL REMOVED>

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of J Isaac
Sent: August 25, 2017 3:26 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] Using a Mouse with a Screen Reader

Hi Sara,

You asked if using a mouse with a screen reader is a viable test case.

Regardless of others opinions, I do believe it is.

I have had similar experiences as Jon Avila with non-screen reader users trying to test keyboard flows and that is one thing to consider.

As a full time screen reader user, I sometimes use the mouse tracking in NVDA and mouse echo feature in JAWS to gain orientation to screen layout.

I believe this will be a use case that will gain acceptance amongst daily screen reader users over time as these tools become more accurate and use is understood.
If I were to add this case to my testing methodology, I would draw a distinct difference between screen reader with keyboard and screen reader with mouse, ensuring the mouse tracking and mouse echo are off when keyboard testing.

HTH,
== Joel Isaac

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Sarah Jevnikar
Sent: Friday, August 25, 2017 11:51 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: [WebAIM] Using a Mouse with a Screen Reader

Hi all,
I've been evaluating some accessibility tickets of potential WCAG level A failures, but the original tests were run with a mouse and a screen reader. I use a screen reader but can't use a mouse, and can't replicate the problems the original tests indicated. Is a screen reader user with a mouse a viable test case to explore? If a mouse user finds different results than a keyboard user, does this suggest a WCAG failure, as possibly a failure of 2.1.1? How might something like that be rectified?
Thank you for your help,
Sarah