Closed Bug 1992028 Opened 3 months ago Closed 2 months ago

Add 'details-from' attribute to clarify details relationship origin.

Categories

(Core :: Disability Access APIs, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
146 Branch
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?

Flags: needinfo?(jteh)

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.

Type: task → enhancement
Flags: needinfo?(jteh)

Do we need this to ship?

Yes. I'll have a patch ready today.

This allows ATs to distinguish the source of details relations.

Assignee: nobody → eitan
Status: NEW → ASSIGNED

Backed out for causing mda and dt failures.

Flags: needinfo?(eitan)
Flags: needinfo?(eitan)
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 146 Branch
QA Whiteboard: [qa-triage-done-c147/b146]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: