[Athen] site works with NVDA/Chrome, JAWS/IE,
but not NVDA/Firefox
Howard Kramer
hkramer at ahead.org
Fri Feb 3 09:30:15 PST 2017
Thanks Peter.
-Howard
On Thu, Feb 2, 2017 at 7:49 PM, Bossley, Peter A. <bossley.5 at osu.edu> wrote:
> It is worth noting that Firefox + NVDA is our default testing combination
> because it brings you closest to modern web standards + modern screen
> reader without some of the guessing and extra excuse making that the
> commercial offerings sometimes insert into the process.
>
> If the site doesn’t work in FF + NVDA there are bound to be other issues.
>
> Without seeing the code it will be hard to guess what the issues are but
> I’ll tell you that service now has some serious challenges in this arena,
> and any views that are generated with their frameworks are probably going
> to be troublesome on one level or another for screen reader reliant users.
>
>
>
>
>
> *From:* athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] *On
> Behalf Of *Howard Kramer
> *Sent:* Thursday, February 2, 2017 5:02 PM
> *To:* Access Technology Higher Education Network <
> athen-list at u.washington.edu>
> *Subject:* [Athen] site works with NVDA/Chrome, JAWS/IE, but not
> NVDA/Firefox
>
>
>
> Just wanted to get other folks' opinion on this. I've been helping to
> evaluate a prototype application here on our campus - time/payroll type
> tool. Surprisingly I've found the the interface is pretty accessible with
> NVDA/Chrome and JAWS/Firefox but not accessible with NVDA/Firefox. The
> developer said he tested his design with ChromeVox so that helps explain
> the accessibility with Chrome.
>
>
>
> Two questions: at what point do you say an application or website is
> screenreader accessible - does it have to work with every AT/browser combo
> or if it seems to work with most, is that okay. Second, any ideas on why
> the NVDA/FF environment does not work? BTW - this application was developed
> under the ServiceNow platform.
>
>
>
> Thanks,
>
> Howard
>
>
>
>
>
>
> --
>
> Howard Kramer
>
> Conference Coordinator
>
> Accessing Higher Ground
>
> 303-492-8672 <(303)%20492-8672>
>
> cell: 720-351-8668 <(720)%20351-8668>
>
>
>
> Join us for the *Accessing Higher Ground Conference
> <http://accessinghigherground.org/>* in Denver, Colorado, Nov 13-17,
> 2017. Request for proposals will be announced at the beginning of March.
>
>
>
> Complete program information and registration is open for our full line-up
> of webinars, *AHEADtoYOU!
> <http://ahead.org/learn/virtual-learning/webinars>* And the *Technology
> Access Series <http://ahead.org/learn/virtual-learning/at_webinars_15_16>*.
> Site capacities for all webinar events is limited; please register at your
> earliest convenience for the largest selection.
>
>
>
> Not yet a member of AHEAD? *We welcome you to join AHEAD now.
> <http://ahead.org/join/become-a-member>*
>
>
>
> _______________________________________________
> athen-list mailing list
> athen-list at mailman13.u.washington.edu
> http://mailman13.u.washington.edu/mailman/listinfo/athen-list
>
>
--
Howard Kramer
Conference Coordinator
Accessing Higher Ground
303-492-8672
cell: 720-351-8668
Join us for the *Accessing Higher Ground Conference
<http://accessinghigherground.org/>* in Denver, Colorado, Nov 13-17, 2017.
Request for proposals will be announced at the beginning of March.
Complete program information and registration is open for our full line-up
of webinars, *AHEADtoYOU!
<http://ahead.org/learn/virtual-learning/webinars>* And the *Technology
Access Series <http://ahead.org/learn/virtual-learning/at_webinars_15_16>*.
Site capacities for all webinar events is limited; please register at your
earliest convenience for the largest selection.
Not yet a member of AHEAD? *We welcome you to join AHEAD now.
<http://ahead.org/join/become-a-member>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20170203/8d1a8a60/attachment.html>
More information about the athen-list
mailing list