WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: browsers and screen reader testing

for

From: Jonathan Avila
Date: Oct 15, 2015 8:29AM

> Is the description of the experience in all cells whether marked Failed / Works / Works fine not sufficient or clear enough?

Sailesh, I would agree with Steve that by marking it as a failure it is implied that it is a screen reader failure or an accessibility failure when instead it's that the browser did not implement the feature for all users. Personally I would find a comparison between the feature as implemented for all users compared to the accessibility experience most helpful.

All, I appreciate everyone's efforts creating these types of matrices -- I create them myself. One thing that I see others do (not you specifically) is make general statements without documenting that nuanced ways things are exposed. That is, I've found with screen readers that things may be announced different with tab than with arrows in browser/virtual cursor mode, etc. So it's very important to document the method of navigation. Another example is how a technique is performed. For example, someone might conclude that aria-live is not work but there are multiple ways to implement dynamic content changes, e.g. display, visibility, node additional removal, text node removal additions, etc. and I've found that the varying methods may have different results. Thus, it is very important for those of us including myself to be very clear on these factors. So this is just something for everyone to keep in mind.

Jonathan

-- 
Jonathan Avila 
Chief Accessibility Officer
SSB BART Group 
<EMAIL REMOVED>
Phone 703.637.8957  
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter