ARIA property
aria-owns
Claims elements as children when the markup cannot nest them. A last resort, and easy to get wrong.
It rearranges the accessibility tree without touching the DOM, so an element somewhere else in the page is presented as a child of this one. Nothing visual moves. Only the shape assistive technology sees changes.
Which roles may carry aria-owns
- Value
- ID reference list
- Filed as
- A property, which is how ARIA files it and not a rule about how often it changes.
- Roles that may carry it
- Any role. This one is global, which is why no individual role lists it.
Global means no role has to grant permission for it. There is one more place to check, because ARIA in HTML sets rules per element as well as per role, and it allows no aria-* attributes at all on a datalist or on the html element. Past that, the way a global attribute goes wrong is rarely where it sits. It is whether it is still true, which is the next section.
Every role above comes from the specification's own list for this attribute, checked name for name. The normative definition stays with the W3C, in the aria-owns section of the ARIA specification.
Keeping aria-owns true
Two rules keep this from turning into a mess. An element can have exactly one owner, and the spec makes it a requirement that no id appears in more than one aria-owns anywhere in the document at the same time. And real DOM children come first in the resulting order unless you list them explicitly, which catches everybody who expects their own list to be the whole order. Add the usual reference problem on top, where an id that stops resolving is dropped in silence. Each of those breaks the moment a component is rendered twice on one page, which is the argument for fixing the DOM instead wherever you can.
How aria-owns gets checked
There are test rules that check an ARIA attribute is one that exists, is allowed on the role underneath it, and carries a value of the right type. What they map to is ARIA's own author requirements rather than any WCAG criterion, so a misplaced attribute breaks ARIA without being a WCAG failure by itself. It becomes one under 4.1.2 Name, Role, Value the moment the missing or wrong value means the control's state cannot be worked out programmatically, which is what usually happens next.
The value testing skips id references on purpose. Pointing at an element that does not exist and having no pointer at all come to the same end, so a broken reference fails no rule directly. It fails later, wherever the missing name or description was needed.
Nothing automated catches the failure this page is about. A stale value is a valid value, on a permitted role, with the right type. It is only wrong about the world.
Attributes you will meet alongside aria-owns
- aria-atomic Whether an update should be read whole, or only the part that changed.
- aria-busy Says a region is still being updated, so wait before announcing it.
- aria-controls Points at what this control operates. A combobox has to say what it opens.
- aria-current Marks the one item in a set that represents the here and now, such as the current page in a nav.
- aria-describedby Points at further description, read after the name. Hints and error text usually go here.
- aria-details Points at richer explanation elsewhere in the page, which people can navigate to rather than have read out.
- aria-flowto Overrides reading order by pointing at what should be read next. Rarely the right answer.
- aria-hidden Removes an element from the accessibility tree while leaving it on screen.
Every ARIA state and property · Every ARIA role · ARIA explained