WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Voiceover bugs for Web


From: Birkir R. Gunnarsson
Date: Oct 26, 2021 3:44AM

A <span> is a semantically neutral inline element, no reason to put it
on its own line, especially when its part of a focusable block level
element (like a link).
There is no need for a text role to make that happen. Even if it were,
the native HTML equivalent would be the <span> element.

I spoke up against the text role at the time, though the use case I
didn't like was to use it on image elements.

You could try role="none" on the <span> to see if it changes anything?
It's worth a try certainly.

On 10/26/21, David Engebretson Jr. < <EMAIL REMOVED> > wrote:
> Lots of history in there Glen, thanks for sharing!
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of glen
> walker
> Sent: Monday, October 25, 2021 5:59 PM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] Voiceover bugs for Web
>> It will likely be around to stay and will most likely make it into the
>> ARIA specification at some point, and is safe to use now.
> That might be a bit generous. Until something is in the spec, I would not
> consider it safe to use. There was a text role batted around for a while
> by the ARIA committee but it was decided to not include it in the spec. It
> *might* make it in one day but unless you're on the committee lobbying for
> it, there's no guarantee it'll ever be there.
> https://www.w3.org/WAI/ARIA/track/issues/435
> https://lists.w3.org/Archives/Public/wai-xtech/2011Apr/0007.html
> > > > >
> > > > >

Work hard. Have fun. Make history.