W3C home > Mailing lists > Public > public-html@w3.org > July 2012

: Using ARIA in HTML

From: Sunyang (Eric) <eric.sun@huawei.com>
Date: Thu, 5 Jul 2012 08:28:39 +0000
To: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>
CC: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <9254B5E6361B1648AFC00BA447E6E8C32AEB6EE4@szxeml545-mbx.china.huawei.com>
Hi Steve:

Thanks for your document.
I am new to a11y, so I spend some time to review and try to understand ARIA in HTML.

Alt is easy for understanding, is just some text will be reading to assist people know what is the image/video/
But for the role, I feel a little confused, in your using ARIA in HTML, if we define role in an element, the element will be change to another kind of element.
For example, <a href=. Role=button>link</a>, so the a element will be change to <button>link</button>.
I cannot understand whats benefit to change the element to another using role, why?

And I also see that role can also be a class like attribute, like presentation, whats the meaning?

Sorry for so many questions ;)

Yang Sun
Email: eric.sun@huawei.com
Huawei Technologies Co., Ltd.

This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

: Steve Faulkner [mailto:faulkner.steve@gmail.com]
ʱ: 2012629 20:23
: HTML Accessibility Task Force
: Using ARIA in HTML

I have posted an intial draft of a document I have been working on which attempts to provide practical advice to developers on what ARIA to use in HTML.


My intention is to provide a non normative resource that fills in the gaps in the current HTML5 specification and a document that is more readable (i.e. less jargonist) It does deviate from HTML5 in some of its suggestions, these deviations are based on current implementation realities.

all feedback welcome

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com<http://www.paciellogroup.com> | www.HTML5accessibility.com<http://www.HTML5accessibility.com> | www.twitter.com/stevefaulkner<http://www.twitter.com/stevefaulkner>
HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/<http://dev.w3.org/html5/alt-techniques/>
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 5 July 2012 08:32:44 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:24 UTC