WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Voiceover bugs for Web


From: glen walker
Date: Oct 25, 2021 8:04AM

Agreed. I typically let the screen reader do what it does and don't code
around the way it works, but sometimes the "owner" of the product requires
it so I was pointing out the hack to get around it. When I'm a contractor,
there's only so much "clout" that I can wield and even if I suggest the
code is technically accurate, if they don't like the UX of the SR, then I
give them workarounds. Thus I've used role=text when needed.

On Mon, Oct 25, 2021 at 2:19 AM Murphy, Sean <
<EMAIL REMOVED> > wrote:

> Glenn,
> The point is you should not have to use such undocumented solutions. No
> other screen reader requires this on desktop or mobile. Using aria to
> address shortcoming of assistive technology isn't best practise. These
> types of band-aid solutions are not supporting the community of users who
> require this technology to access digital content. If any main stream
> vendor is stepping into the assistive technology space, then they need to
> be held accountable to making the assistive technology work for the end
> user and not have such strange bugs placing more effort on to other
> developers.
> Likewise for browser vendors, there is a lot of ARIA usage which could
> quite easily be address by HTML and CSS. Reducing the crappy implementation
> of ARIA that exist now. Browser vendors from my point of view are using
> ARIA as a band-aid solution rather than expanding the specs to provide
> support for common patterns being used today.