[Athen] JAWS inspect
Bourne, Sarah (MASSIT)
sarah.bourne at mass.gov
Thu Jan 31 12:02:49 PST 2019
Dan is correct. There is no testing tool that can find 100%, so using just one tool can never be sufficient.
Each of them can be good for finding particular things, though. This one could be handy for a developer to test to be sure form fields and link text are correct and meaningful, to see if your in-page navigation by element is useful, and to check that alternative text for images makes sense in context. I suppose you could use it to do an audit for those things, but I would probably use other tools since it's JAWS-specific.
Sarah E. Bourne
Director of IT Accessibility
1 Ashburton Place, 8th Floor, Boston, MA 02108
Office: (617) 626-4502
sarah.bourne at mass.gov | www.mass.gov/eotss<http://www.mass.gov/anf/research-and-tech/oversight-agencies/itd/>
Executive Office of Technology Services and Security (EOTSS)
EOTSS provides secure and quality digital information, services, and tools
to constituents and service providers when and where they need them.
From: athen-list <athen-list-bounces at mailman12.u.washington.edu> on behalf of Dan Comden <danc at uw.edu>
Sent: Thursday, January 31, 2019 1:29 PM
To: Access Technology Higher Education Network
Subject: Re: [Athen] JAWS inspect
Just based on the video that Doug linked and the bit of text on that page, I would say this tool has limited use for evaluating true accessibility of a web page or web-based application. There is much more to accessibility than assuring "JAWS accessibility" and we need to keep reminding designers and developers that screenreaders are not the only AT that is in use, nor do they define what accessibility means for web-delivered materials.
Just this week we met with a software company and part of their design/dev team and one of the key devs was quite familiar with NVDA. That was really nice to see, but they were still missing some important visual accessibility issues as well as overall functional accessibility/usability with their product. Using and knowing screen readers only catches some of the issue. They are key issues, but far from a complete accessibility picture.
On Thu, Jan 31, 2019 at 9:34 AM Khoa Pham <kpham at swccd.edu<mailto:kpham at swccd.edu>> wrote:
Has anyone ever heard of JAWS inspect or currently using it? I wanted to get some input on this tool by someone who have used it to evaluate Web contents, Web apps, and other contents.
athen-list mailing list
athen-list at mailman12.u.washington.edu<mailto:athen-list at mailman12.u.washington.edu>
-*- Dan Comden danc at uw.edu<mailto:danc at washington.edu>
Access Technology Center www.uw.edu/itconnect/accessibility/atl/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uw.edu_itconnect_accessibility_atl_&d=DwMFaQ&c=lDF7oMaPKXpkYvev9V-fVahWL0QWnGCCAfCDz1Bns_w&r=rhLenV33VPpmkT7iP0-OkUlRYw9YWn3HMLHZVP2q9y8&m=IcNyxIoDJoo_jSXKwYq2hoPDvk164mzMTfhbhLczj4g&s=knOPJGUY2NpsBgqzbJYjVHyns28T_66ooc54IKs_Oeg&e=>
University of Washington UW Information Technology
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the athen-list