WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Working around flaky browser accessibility tree

for

From: Birkir R. Gunnarsson
Date: Apr 7, 2018 11:39AM

Exactly. You only have a chance to do proper user testing with one
combination of a browser and a screen reader, doing more than that is
usually unattainable because of the resources required.
so you should have a statement, or help page or something publically
accessible that states: For best experience use combination x, (often
NVDA and Firefox) or that your site was tested with combination x.


On 4/6/18, Glen Walker < <EMAIL REMOVED> > wrote:
> In this particular case, it sounds like you're ok, but it's a good general
> question. If my site works well with browser A and screen reader X, do I
> have to worry about browser B or screen reader Y? I think a common practice
> is for companies to have an accessibility statement that says something
> like, "For the best user experience, we recommend using jaws with ie or nvda
> with firefox", with possible details about browser or AT version numbers. VO
> is usually included too. I don't see chrome mentioned very often in those
> statements, fwiw.
> > > > >


--
Work hard. Have fun. Make history.