Bug 132510
| Summary: | Web Inspector: AX: difficult to use the Web Inspector DOM tree view with a screen reader | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | James Craig <jcraig> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, vtsaran, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
James Craig
Web Inspector: AX: It is difficult to use the DOM tree with VoiceOver
Putting this in the tracker because Victor mentioned it, but I'm not sure how to solve it yet. This behaves something like an interactive ARIA tree, but it's almost like it's inside a selectively editable region, like a custom contenteditable but a tree. The editable attributes act mostly like contenteditable, but it's done in a way that WebKit isn't exposing and VoiceOver wouldn't recognize anyway, unless WebKit were pretending that this node were temporarily turning into text fields. I don't think we've even got precedent for how to make that accessible on the desktop, let alone in web standards.
The long-term solution to this problem will probably involve changes to WebKit Inspector, WebCore Accessibility, and potentially even platform APIs or screen readers. We might also determine we need to be additions to ARIA or other specs, too. First step is to break this into more manageable sub-tasks. This can be the umbrella tracker.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/16803858>
James Craig
*** Bug 115973 has been marked as a duplicate of this bug. ***