Closed
Bug 740863
Opened 13 years ago
Closed 8 years ago
XBL accessibility
Categories
(Core :: XBL, defect)
Core
XBL
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: enndeakin, Unassigned)
References
Details
(Keywords: access)
Currently, accessibility information for bindings is provided by implementing
nsIAccessibleProvider.
This is a placeholder bug for features I want to explore on improving this so that a binding can specify how the element maps to accessibility features in more detail.
|
||
Comment 1•13 years ago
|
||
Few years ago I suggested to extend XBL syntax (I started thinking here https://wiki.mozilla.org/Accessibility/CustomWidgets). If it seems reasonable then I can write down the idea in details.
Keywords: access
|
Reporter | |
Comment 2•13 years ago
|
||
Please do write your ideas down.
My basic idea was to add a role element where one could define the role, how focus behaves and how properties the xbl binding defines map to specific properties accessibility understands. For example, using current xbl syntax:
<binding>
<role role="button" focus="normal" properties="accessibleText:label"/>
<implementation>
<property name="label" onget="..."/>
</implementation>
</binding>
But I didn't explore much further than that.
|
||
Comment 3•8 years ago
|
||
Web Components \o/
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•