WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Does aria-owns child need to exist prior to being used?

for

From: Aditya
Date: Dec 12, 2018 2:25PM

In my opinion, unless it's aria-labelledby or aria-describedby, axe should not be reporting it. It makes sense to report missing ref for the above two because these Aria attributes are used in calculating accessible name. For aria-owns, aria-controls, it should not require that the id be present in default state.

Performance wise, it's better to change value of attributes rather than adding attributes themselves.



> On Dec 12, 2018, at 2:35 PM, glen walker < <EMAIL REMOVED> > wrote:
>
> I think if someone knew the answer, you should still create test
> implementations to verify, especially given the variety of
> AT/browser/platform combinations.
>
> I don't think it's well documented (at least that I've been able to find),
> about the timing of such things. If an element is created dynamically that
> is referenced in an IDREFS
> <https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#IDREFS> attribute
> (aria-labelledby, aria-describedby, aria-owns, aria-controls, etc), when
> does AT try to reference that object?
>
> I know when I'm viewing a page and have the code inspector up, I can change
> things dynamically in the code inspector and most of the time, AT will pick
> up the change. It's a nice way to test concepts without writing an
> example. (I say "most of the time" because occasionally I won't hear what
> I expected after a change, but I can't specifically point out what didn't
> work.) I'm usually adding new aria attributes, or changing the value of
> existing attributes. But the timing on doing that in the code inspector is
> quite different than the timing you'll have when doing stuff from
> javascript.
>
> Glen
> > > >