Add 'details-from' attribute to clarify details relationship origin.
Categories
(Core :: Disability Access APIs, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox146 | --- | fixed |
People
(Reporter: eeejay, Assigned: eeejay)
References
Details
Attachments
(1 file)
Chrome exposes a details-from attribute when an accessible has a details relation. This would be straightforward to implement for the automatic details relations we create, but should we?
Comment 1•3 months ago
|
||
The idea here is to enable AT to filter out details relationships if they decide they don't want to report them or the like. However, I'd argue that if AT start filtering out automatic details relations of any type, that suggests we possibly shouldn't be exposing them in the first place.
NVDA doesn't use details-from at this stage. Interestingly, it does have an advanced setting to toggle reporting of aria-description via description-from.
My thinking at this stage is that this isn't a wontfix, but I don't think we should invest in it unless a client actually wants to start using it.
Comment 2•2 months ago
|
||
Do we need this to ship?
| Assignee | ||
Comment 3•2 months ago
|
||
Yes. I'll have a patch ready today.
| Assignee | ||
Comment 4•2 months ago
|
||
This allows ATs to distinguish the source of details relations.
Updated•2 months ago
|
Backed out for causing mda and dt failures.
- Backout link
- Push with failures
- Failure Log mda failures
- Failure Log dt failures
- Failure Log reftest failures
| Assignee | ||
Updated•2 months ago
|
Updated•1 month ago
|
Description
•