W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2018

RE: NVDA /FF vs NVDA/Chrome [SEC=UNCLASSIFIED]

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Thu, 26 Jul 2018 22:20:08 +0000
To: Paul E Matthews <PaulE.Matthews@ato.gov.au>, sirisha gubba <nsfsiri2014@gmail.com>
CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <1f04074156c24710a654e6c7ea039785@XCH-RCD-001.cisco.com>
I want to clear something up here. Jaws 2018 does work fine with Firefox. Jaws 18 works fine with versions of firefox before version 60. There is a miss understanding in the accessibility world stating Jaws does not support firefox and only IE.

The difference between the two screen readers is how they obtain, process and present the information to the end user.

Chrome support for either screen reader I am not sure is at the same level as Firefox or IE. As I have found some users having issues in Chrome due to the screen reader and they have to change to later versions of Chrome.


[https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/standard/02_standard_ciscoblue02.png]




Sean Murphy
SR ENGINEER.SOFTWARE ENGINEERING
seanmmur@cisco.com<mailto:seanmmur@cisco.com>
Tel: +61 2 8446 7751










Cisco Systems, Inc.
The Forum 201 Pacific Highway
ST LEONARDS
2065
Australia
cisco.com



[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]

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.
Please click here<http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html> for Company Registration Information.







From: Paul E Matthews <PaulE.Matthews@ato.gov.au>
Sent: Friday, 27 July 2018 7:57 AM
To: sirisha gubba <nsfsiri2014@gmail.com>
Cc: w3c-wai-ig@w3.org
Subject: RE: NVDA /FF vs NVDA/Chrome [SEC=UNCLASSIFIED]

Hi Siri

I pressed SEND to quickly … I meant to include this link too:

https://developer.paciellogroup.com/blog/2015/01/the-browser-accessibility-tree/


Thanks
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Paul E. Matthews
ATO Community User Interface Designer
Enterprise Culture, Change and Innovation
Australian Taxation Office
Ph: 03 622 10112

[cid:image008.png@01D42582.9B249870]<https://www.facebook.com/ato.gov.au>

[cid:image009.png@01D42582.9B249870]<https://twitter.com/ato_gov_au>

[cid:image010.png@01D42582.9B249870]<https://www.linkedin.com/company/australian-taxation-office>

[cid:image011.png@01D42582.9B249870]<https://community.ato.gov.au/>

[cid:image012.png@01D42582.9B249870]<http://sharepoint/GASites/DigitalExperience/SitePages/Home.aspx>



From: Paul E Matthews
Sent: Friday, 27 July 2018 7:55 AM
To: 'sirisha gubba'
Cc: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: RE: NVDA /FF vs NVDA/Chrome [SEC=UNCLASSIFIED]

Hi SIri

What a really good question!  I know that JAWS prefers IE and NVDA prefers FireFox but it never occurred to me to ask why.

I did some very limited Google-research and found information on the Accessibility Tree at http://whatsock.com/training/.  I’ve only scanned it for an answer at the moment but I’ll go back and read this properly later.  Chapter 4 seems to hold a clue in your search for a definitive answer.

If you follow-up on Marc’s advice about talking to Marco Zehe, please share your findings because now you’ve got me wondering.

Hope this helps …

Regards
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
Paul E. Matthews
ATO Community User Interface Designer
Enterprise Culture, Change and Innovation
Australian Taxation Office
Ph: 03 622 10112

[cid:image008.png@01D42582.9B249870]<https://www.facebook.com/ato.gov.au>

[cid:image009.png@01D42582.9B249870]<https://twitter.com/ato_gov_au>

[cid:image010.png@01D42582.9B249870]<https://www.linkedin.com/company/australian-taxation-office>

[cid:image011.png@01D42582.9B249870]<https://community.ato.gov.au/>

[cid:image012.png@01D42582.9B249870]<http://sharepoint/GASites/DigitalExperience/SitePages/Home.aspx>



From: sirisha gubba [mailto:nsfsiri2014@gmail.com]
Sent: Thursday, 26 July 2018 6:14 AM
To: w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: NVDA /FF vs NVDA/Chrome


I have a question about why NVDA in FF browser is recommend even though Chrome and FF uses same API.  As per WEBAIM screen reader usage survey shows NVDA with FF is used more.



Also can you please tell which browser builds better accessibility tree?







Thanks,

Siri
**********************************************************************
IMPORTANT
    The information transmitted is for the use of the intended
recipient only and may contain confidential and/or legally
privileged material. Any review, re-transmission, disclosure,
dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other
than the intended recipient is prohibited and may result in
severe penalties. If you have received this e-mail in error
please notify the Privacy Hotline of the Australian Taxation
Office, telephone 1300 661 542 and delete all copies of this
transmission together with any attachments.
*********************************************************************

image006.png
(image/png attachment: image006.png)

image007.gif
(image/gif attachment: image007.gif)

image008.png
(image/png attachment: image008.png)

image009.png
(image/png attachment: image009.png)

image010.png
(image/png attachment: image010.png)

image011.png
(image/png attachment: image011.png)

image012.png
(image/png attachment: image012.png)

Received on Thursday, 26 July 2018 22:20:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:20 UTC