| Summary: | Support ARIA "tab" roles | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | chris fleizach <cfleizach> | ||||
| Component: | Accessibility | Assignee: | chris fleizach <cfleizach> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | bdakin, cfleizach | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | PC | ||||||
| OS: | OS X 10.5 | ||||||
| Attachments: |
|
||||||
|
Description
chris fleizach
2009-10-27 20:07:47 PDT
tab needs to support AXValue (whether its selected... which can be either if an item in its associated tab panel has focus, or it has aria-selected) a tab can also be selected if KB focus is in one of its aria-controls elements tablist needs to support AXValue = selected tab, AXContents (children that are not tabs) and AXTabs (children that are tabs) tabpanel needs to be an AXGroup with a subrole, like the other aria landmarks make sure this works http://codetalks.org/source/widgets/tabpanel/tabpanel1.html Created attachment 42300 [details]
patch
Beth, I've made these tab roles like we talked about
tab = AXRadioButton
tablist = AXTabGroup
tabpanel = AXGroup:AXTabPanel
I also mirrored the other Mac accessibility things relating to tabs, and tried to follow ARIA spec.
I re-organized some code so that it would be easy to get all Elements from a specific attribute.
As a note, when i ran update-webkit-strings, it removed two accessibility strings. i guess those are no longer used...
Beth, can you review this one. One of the ARIA things we talked about Comment on attachment 42300 [details]
patch
Nice! r=me
|