[Athen] Accessibility Audits
arovner at shoreline.edu
Thu Feb 2 15:12:02 PST 2017
We need to do a full Accessibility Audit (physical and virtual) of our campus and I am in need of suggestions for companies that you have worked with that you liked, as well as approx. cost of the audit. We have about 5000 Annual FTE if that helps with the size of our campus.
Any recommendations are appreciated!
Thank you in advance!
Amy Rovner, MPH RD
Accessible IT Coordinator
Shoreline Community College
arovner at shoreline.edu
From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On Behalf Of Sean Keegan
Sent: Thursday, February 2, 2017 2:43 PM
To: Access Technology Higher Education Network <athen-list at u.washington.edu>
Subject: Re: [Athen] site works with NVDA/Chrome, JAWS/IE, but not NVDA/Firefox
Is the UI a single-page application in which a "view" is updated but the page does not undergo a full browser refresh?
The dev fixed the focus script to happen after the page had completed loading (and used the correct code on the target) and suddenly NVDA worked via Firefox. Also fixed the crash issue.
Simply Accessible had a good article on focus management for Angular.js applications that may be useful. We were using React, but the same principles apply:
I establish the operating environment and screen-reader requirements at the start, so sign-off happens when we meet those requirements (e.g., NVDA+Firefox, JAWS+IE, VoiceOver+Safari, etc.). The operating environment can vary depending on the app in question - for example, if this was an internal application and the only browsers supported by the IT department are Chrome and Firefox, then a screen-reader would have to work with at least one of those browsers. That said, I am highly suspicious of any web application that does not work in Firefox with NVDA.
On Thu, Feb 2, 2017 at 2:02 PM, Howard Kramer <hkramer at ahead.org<mailto:hkramer at ahead.org>> wrote:
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.
Accessing Higher Ground
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<mailto:athen-list at mailman13.u.washington.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the athen-list