W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

Getting real for - Accessibility testing on device simulators

From: ALAN SMITH <alands289@gmail.com>
Date: Mon, 4 Dec 2017 17:16:26 -0500
Message-ID: <5a25c93c.1504810a.51e25.89ea@mx.google.com>
To: "Subramanian, Poornima (PCL)" <psubramanian@hagroup.com>, Elizabeth Linnetz <elizabeth.linnetz@theprimacy.com>, Tobias Bengfort <tobias.bengfort@posteo.de>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>, Steve Green <steve.green@testpartners.co.uk>

My experience is that anything other than a real device does not support proper touch gestures, read-all gesture (I have my android set to tap once since the gesture just does not work correctly or reliably) and does not support Android dev tools displaying what Talkback says or does not support VoiceOver or Talkback period anyway. Finally, emulation methods do not support Bluetooth keyboards either.

Good luck.

You can always rent devices, or find testers with their own devices, at least one Android recent OS on phone and tablet and the same for iOS phone and tablet.


Alan Smith

From: Subramanian, Poornima (PCL)
Sent: Monday, December 4, 2017 3:48 PM
To: Elizabeth Linnetz; Tobias Bengfort; w3c-wai-ig@w3.org; Steve Green; ALAN SMITH
Subject: RE: Accessibility testing on device simulators

Yes, agreed! Thank you for all your valuable feedback.

Right now, with the lack of real devices available for testing, am exploring other options as we have 'browser stack' accounts in our team. Latest, I got response from their support team that they do not support testing with screen readers at this point.

@ Alan, we are testing with JAWS, NVDA on desktops. This is mainly for testing on mobile devices. Your response is great in terms of understanding various perspectives on testing with real devices.

@ Tobias, yes if the browser stack can make the screen reader testing a reality, it is absolutely worth at least for some high level testing.

Thanks again!


-----Original Message-----
From: Elizabeth Linnetz [mailto:elizabeth.linnetz@theprimacy.com]
Sent: Monday, December 04, 2017 2:59 PM
To: Tobias Bengfort <tobias.bengfort@posteo.de>; w3c-wai-ig@w3.org
Subject: RE: Accessibility testing on device simulators

Tobias and Poornima,

We've seen through our own testing that we find issues on real devices that don't show up on browserstack.  For this reason, we only use browserstack in a pinch- if the client requires testing on a device we can't get, for example.

For the majority of our qa testing - both functionality and layout, as well as all of our accessibility testing, we use real devices.




quality assurance analyst
hartford / nyc / boston / west palm

for what’s next

-----Original Message-----
From: Tobias Bengfort [mailto:tobias.bengfort@posteo.de]
Sent: Monday, December 4, 2017 2:43 PM
To: w3c-wai-ig@w3.org
Subject: Re: Accessibility testing on device simulators

Hi Poornima,

On 04/12/17 16:13, Subramanian, Poornima (PCL) wrote:
> 2.      Any experience with "browse stack" simulator?

As far as I know, browserstack is not a simulator. Instead, it gives you access to real browsers on VMs via a web interface. So far, they do not support screen readers.

According to their website, they include OS/browser combinations based on market share[1]. Sound is already available[2]. I think it would be totally possible for them to include screen readers in their services.
Maybe they have just never thought of it.

I must admit that I have never thought of it either. But having a service that gives me access to all kinds of OS/Browser/AT combinations would actually be fantastic. If someone from browserstack is reading
this: Please make this reality!


[1]: https://www.browserstack.com/question/479
[2]: https://www.browserstack.com/question/626

This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________
The information contained in this email and any attachment may be confidential and/or legally privileged and has been sent for the sole use of the intended recipient. If you are not an intended recipient, you are not authorized to review, use, disclose or copy any of its contents. If you have received this email in error please reply to the sender and destroy all copies of the message. Thank you.

To the extent that the matters contained in this email relate to services being provided by Princess Cruises and/or Holland America Line (together "HA Group") to Carnival Australia/P&O Cruises Australia, HA Group is providing these services under the terms of a Services Agreement between HA Group and Carnival Australia.
Received on Monday, 4 December 2017 22:16:55 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 December 2017 16:04:47 UTC