WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?

for

From: Birkir R. Gunnarsson
Date: Jul 29, 2023 2:31PM

ARIA does not allow for an empty role attribute value, that's invalid markup.
At best, and fortunately this appears to be the case, it's ignored by
browsers/screen readers.
At worst this would remove the native role attribute from the elements
where they are present, e.g. buttons/links/headings etc.
This is invalid markup, and I have a hard time seeing why you'd want
it on the page (a role attribute without a pre-determined value that
is).
Again, if you can verify through testing with a sufficient
combinations of screen readers and browsers that this does not impact
the user experience you can justify keeping it, but I'd definitely see
if there could be ways to do it differently.


On 7/29/23, jp Jamous < <EMAIL REMOVED> > wrote:
> While everything is working good, I would fail this if I was testing a page.
> Also, automated tools would fail it.
>
> The ID may not be the biggest concern, but the Role would be. It would fail
> Role, Name Value.
>
> I prefer to have values for all of those by default, then the script can
> change them when the JS execute. Nothing wrong with this approach. However,
> leaving them empty is bad markup and would fail 1.4.2.
>
>