The new property aria-label="string" is a better way to override the accessible name for text that is not shown on the page. (If text is shown, it would be better to simply point to it using aria-labelledby). http://www.w3.org/WAI/PF/aria/#label aria-label takes precedence over aria-labelledby: http://www.w3.org/WAI/PF/aria/#nameref Please change the following name calc docs as well, once this is implemented: http://developer.mozilla.org/en/ARIA_User_Agent_Implementors_Guide#11.3.6_Name
Thank you for your support with my aria-label (or what was aria-name) proposal. It would be really great to have the support of aria-label so the application developers can go on and use it.
Created attachment 336690 [details] [diff] [review] Patch Implement aria-label, plus Mochitests.
Assignee: nobody → marco.zehe
Status: NEW → ASSIGNED
Attachment #336690 - Flags: review?(surkov.alexander)
Comment on attachment 336690 [details] [diff] [review] Patch > >+ // Check for DHTML accessibility label property nit: Check for ARIA 'aria-label' attribute maybe or something like? The similar for XUL. Could you file following up bug for the issue we should move 'aria-label' attribute check to cross-XML-language code. I can see you can't just put it into nsAccessible::GetName but I believe it should be there because we miss ARIA support for XForms for example. with this looks ok, r=me
Attachment #336690 - Flags: review?(surkov.alexander) → review+
I filed following up bug 453591 for getName reorganization. Also, Marco, please fix nsXFormsAccessible::GetName to handle aria-label attirbute
Pushed in changeset: http://hg.mozilla.org/mozilla-central/rev/8ebb9800a80d Sri, this will be in 3.1b1pre nightlies starting Fri September 5. If you would like to see this in a 3.0.x release, with 3.0.3 being the earliest possible, please let us know.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Noticed that the URL Aaron requested be updated is already updated with this new info. Setting appropriate keyword.
You need to log in before you can comment on or make changes to this bug.