Closed Bug 1588784 Opened 6 years ago Closed 14 days ago

Expose heading level more clearly

Categories

(DevTools :: Accessibility Tools, enhancement, P3)

enhancement

Tracking

(firefox153 fixed)

RESOLVED FIXED
153 Branch
Tracking Status
firefox153 --- fixed

People

(Reporter: annevk, Assigned: nchevobbe)

References

Details

(Keywords: dev-doc-needed)

Attachments

(1 file)

The accessibility tree shows that something is a heading and under attributes you can find its level, but it would be nice if this was a little more prominent, perhaps even visible in the main tree given its significance.

(See also bug 998590 comment 6.)

See Also: → 998590
Summary: Expose heading level → Expose heading level more clearly

Along similar lines, we should consider exposing the landmark role from the xml-roles attribute if the role is "landmark". If searching for "level" in the attributes is not intuitive, searching for the "xml-roles" attribute is even less so. :)

Perhaps we could just expose this in the tree where we expose the role? "heading level 2" instead of just "heading" and "main landmark" instead of just "landmark"?

That seems reasonable to me. Perhaps add the distinction between parenthesis as in "heading (level 2)" and "landmark (main)" so it's clear what the role is and what the modifier is.

Severity: normal → S3
Priority: -- → P3
Duplicate of this bug: 2044590
Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED

As noted in bug 2044904, this change seems to be worth being mentioned in the dev release notes together with the change in the other bug.

Sebastian

Keywords: dev-doc-needed
Status: ASSIGNED → RESOLVED
Closed: 14 days ago
Resolution: --- → FIXED
Target Milestone: --- → 153 Branch
See Also: → 2044336
QA Whiteboard: [qa-triage-done-c154/b153]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: