- From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
- Date: Mon, 20 Aug 2018 01:28:09 +0000
- To: Shivaji Kumar <kumar140ster@gmail.com>, Matt Elton <mattelton35@gmail.com>
- CC: "Subramanian, Poornima (PCL)" <psubramanian@hagroup.com>, "Elizabeth Linnetz" <elizabeth.linnetz@theprimacy.com>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hello all, My 2 pennies (cents) worth. The notion of using one screen reader with a specific browser in my view is bad testing. As you are making assumptions which are not correct. There are users out there who use edge, firefox and Chrome with NVDA, Jaws and Narrator on the windows platform. Regardless of the stats shown in the webAim survey. IE in my view is a historical browser and is being phased out. Jaws and Window-eyes of course are the two screen readers which worked the best with this browser. It is important people test firefox and Chrome with Jaws and NVDA. Any bugs they find which they believe are related to the screen reader. Then they must be reported to the vendors of those products for them to fix the issues. The simple identification of these types of bugs is by using both screen readers against the same page loaded in the same browser on the same machine. If there is a difference of behaviour between one screen reader and the other. Then you have possibley identified a bug. If both screen readers have the same issue, then you have found a bug in your code or the browser. Repeat the test on the different browser and if the issue still exist, then it is your code. I would suggest people review this blog on the webAim survey short coming. The survey is still our only good source of user trends by the way and the Webaim team does a good job providing this resource. http://chrishofstader.com/screen-reader-market-figures-my-analysis-of-webaim-survey-6/ Sean Murphy SR ENGINEER.SOFTWARE ENGINEERING seanmmur@cisco.com Tel: +61 2 8446 7751 Cisco Systems, Inc. The Forum 201 Pacific Highway ST LEONARDS 2065 Australia cisco.com Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html -----Original Message----- From: Shivaji Kumar <kumar140ster@gmail.com> Sent: Saturday, 18 August 2018 1:37 AM To: Matt Elton <mattelton35@gmail.com> Cc: Subramanian, Poornima (PCL) <psubramanian@hagroup.com>; Elizabeth Linnetz <elizabeth.linnetz@theprimacy.com>; w3c-wai-ig@w3.org Subject: Re: WCAG v2.1 for mobile website evaluation If you have luxury of time and money, I would test Chrome with JAWS and NVDA. WebAim's survey shows 6.5 and close to 6 percent Chrome users rely on JAWS and NVDA, respectively. See that survey here: https://webaim.org/projects/screenreadersurvey7/ Best Shivaji On 8/17/18, Matt Elton <mattelton35@gmail.com> wrote: > Thank you very much. All your replies have been very helpful in > providing me with a fuller picture. > > I have one more question (sorry for being greedy!). I've been told > that it is best to match certain desktop screen readers with browsers. > For example, IE with JAWS, NVDA with Firefox etc. With the newer > desktop screen readers (like JAWS 18) is this still important? If so, > what desktop screen reader would you use with Chrome? > > Cheers, > Matt > > On Fri, Aug 17, 2018 at 4:07 PM, Subramanian, Poornima (PCL) < > psubramanian@hagroup.com> wrote: > >> That’s correct. Though the website is responsive, the user interface >> will have at least minimal change in terms of layout and presentation. >> >> >> >> For example, the visual label in desktop label can act as a hidden >> label in mobile view. And, the elements presented as show/hide >> elements in mobile view coded differently on desktop view. >> >> >> >> We initially test with Chrome mobile and desktop view to identify any >> change in the presentation on both views. This helps to a great >> extent to find out any missing labels, menu presentations, etc. to >> cover most of WCAG >> 2.0 guidelines. >> >> Then, testing with keyboard to ensure the elements are keyboard >> accessible >> >> Then, testing with both desktop (JAWS & NVDA) and mobile readers (VO, >> Talkback) to comply with full WCAG 2.0 standards. >> >> >> >> Best, >> >> Poornima. >> >> >> >> *From:* Elizabeth Linnetz [mailto:elizabeth.linnetz@theprimacy.com] >> *Sent:* Friday, August 17, 2018 10:23 AM >> *To:* Matt Elton <mattelton35@gmail.com>; w3c-wai-ig@w3.org >> *Subject:* RE: WCAG v2.1 for mobile website evaluation >> >> >> >> Hi Matt, >> >> >> >> You’ll find different issues on a mobile vs. desktop view – even if >> most of the elements are the same, frequently the menu renders >> differently on mobile vs. desktop. Tabs may render as accordions and >> need to be tested, and other elements may change as well. You’ll want >> to make sure that anything hidden in mobile renders properly on >> desktop and remains hidden from screen readers. VoiceOver, TalkBack, >> JAWS, and NVDA all have different quirks as well. >> >> >> >> >> >> *From:* Matt Elton [mailto:mattelton35@gmail.com >> <mattelton35@gmail.com>] >> *Sent:* Friday, August 17, 2018 10:07 AM >> *To:* w3c-wai-ig@w3.org >> *Subject:* WCAG v2.1 for mobile website evaluation >> >> >> >> Hi everyone, >> >> >> >> I hope you can help me with a question I have been thinking about for >> a while. >> >> >> >> The updated WCAG v2.1 guidelines seem to be device independent but I >> was wondering if all the non-compliant issues would be discovered if >> someone was to conduct an assessment of a mobile version of a >> responsive site using just an iPhone (and VoiceOver). Is this >> sufficient or should the desktop version also be assessed (using a >> desktop screen reader like JAWS or NVDA). >> >> >> >> Thank you very much for your help. >> >> >> >> Cheers, >> >> Matt >> >> >> _____________________________________________________________________ >> _ 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. >> > -- JAWS® Certified Trainer, 2018 Twitter handle @ShivKumar140 My Blog https://digitalaccess365.wordpress.com/ Webpage www.linkedin.com/pub/shivaji-kumar/35/a73/11a/en
Received on Monday, 20 August 2018 01:28:34 UTC