Improve accessibility of box model view
Categories
(DevTools :: Inspector, enhancement)
Tracking
(Not tracked)
People
(Reporter: sebo, Unassigned)
References
(Blocks 1 open bug)
Details
The box model view needs some improvement regarding its ARIA support.
Currently it has aria-level and aria-owns attributes set on the legend elements of the different levels (i.e. position, margin, border, and padding).
An a11y peer should provide some input on what's the best solution for the logical structure.
|
||
Comment 1•4 years ago
|
||
Previously the boxmodel view had 4 isolated "navigation" levels:
- position (4 inputs)
- margin (4 inputs)
- padding (4 inputs)
- width and height (2 inputs)
If you focused a "position" input, pressing TAB would only cycle through "position" inputs. To reach "margin" inputs, you had to press the DOWN ARROW key.
But after Bug 1357890 lands, all the inputs mentioned above can be reached through TAB.
In the markup right now we assign aria-level 1 to position inputs, aria-level 2 to margin inputs etc...
I can see how this made sense with the previous implementation, where each group was isolated.
But I wonder if it's still meaningful now.
Description
•