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

RE: Browser support with screen reader query

From: Chagnon | PubCom <chagnon@pubcom.com>
Date: Wed, 22 Nov 2017 17:46:40 -0500
To: <w3c-wai-ig@w3.org>
Message-ID: <007201d363e3$c38dc310$4aa94930$@pubcom.com>
Sean wrote:
" 1. At what time do the vendors of browser communicate with the assistive
technology companies of major changes to their browsers  which are going to
impact the accessibility community? "

The protocol of software development would let the A T companies become
members of the browser beta testing programs. This gives the A T vendor not
only advanced time to adjust their software to work with the forthcoming new
browser, but also talk directly with the software engineers about any
problems and issues.

--Bevi Chagnon


-----Original Message-----
From: Sean Murphy (seanmmur) [mailto:seanmmur@cisco.com] 
Sent: Wednesday, November 22, 2017 5:08 PM
To: tink@tink.uk; w3c-wai-ig@w3.org
Subject: RE: Browser support with screen reader query

Léonie

Thanks for the information again, I was aware of this resource. The question
is more generic and across all OS platforms. 

In relation to Harry's two questions, I don't know. As this raises other
questions:
1. At what time do the vendors of browser communicate with the assistive
technology companies of major changes to their browsers  which are going to
impact the accessibility community?
2. What is the speed of fixing outstanding caveats in relation to
accessibility and bringing the browser into conformance to the standards?
3. I understand the USA FCS law states browsers on mobile devices have to be
accessible, should this be expanded to computers as they can now be used as
communication devices? Would this change the landscape and give a assistive
technology user the same expected experience across browsers assuming the
assistive technology vendor have done their job?

Just questions which I don't have answers for. :-)



Sean Murphy
ENGINEER.CUSTOMER SUPPORT
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-agreeme
nt/company-registration-information.html
-----Original Message-----
From: Léonie Watson [mailto:tink@tink.uk]
Sent: Wednesday, 22 November 2017 7:33 PM
To: Sean Murphy (seanmmur) <seanmmur@cisco.com>; w3c-wai-ig@w3.org
Subject: Re: Browser support with screen reader query

Sean,

There is this effort from Freedom Scientific and TPG, to document Jaws
support for HTML, CSS, ARIA, and SVG:
https://github.com/FreedomScientific/VFO-standards-support/issues

It's also a place where issues can be filed with Jaws support for any of
those four technologies.

It's a community effort, so help improving the documentation is always
welcome.



On 22/11/2017 03:00, Sean Murphy (seanmmur) wrote:
> Team,
> 
> Is there any resources other than WebAim which have done in depth 
> screen reader browser support? The below resources I have reviewed:
> 
> The Paciello Group published HTML5Accessibility.com 
> <http://www.html5accessibility.com/> which goes through the common 
> browsers and their level of supporting accessibility elements. From my 
> reading it doesn't discuss screen reader support with browsers, rather 
> HTMl Accessibility attributes.
> 
>  From PowerMapper.com published Assistive technology compatibility 
> tests <https://www.powermapper.com/tests/> which is very comprehensive.
> Checkout their data on WAI-ARIA screen reader compatibility 
> <https://www.powermapper.com/tests/screen-readers/aria/>. This test 
> research I have not dived deeply into. This information I am still 
> reviewing and not sure if it will give the support factor.
> 
> The reason for this question, I am starting to see a trend where the 
> browser support is becoming more fragmented for screen readers then 
> previously. Especially with Firefox version 57 not supporting NVDA and 
> Jaws. I did see there was an upcoming fix for NVDA for the Firefox 
> version 57 issue. Edge support is a mix bag and so is Chrome. IE11 has 
> stability issues. From a testing point of view, this is a real 
> challenge for us all, not talking about the end-user trying to find a 
> browser on the windows platform which they can use effectively. Thoughts?
> 
> https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/stand
> ard/08_standard_graphic.png
> 
> 	
> 
> *Sean Murphy*
> 
> ENGINEER.CUSTOMER SUPPORT
> 
> 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.
> 
> 	
> 

--
@LeonieWatson @tink@toot.cafe tink.uk carpe diem
Received on Wednesday, 22 November 2017 22:47:10 UTC

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