- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Thu, 5 Jul 2012 11:02:56 +0100
- To: "Sunyang (Eric)" <eric.sun@huawei.com>
- Cc: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
- Message-ID: <CA+ri+VnBDpw1BsQ4hkNWA5=xstrWWiYKAZ+heErW7F5OYQiihg@mail.gmail.com>
HI Eric. To understand WAI-ARIA it is best to read the source documents: The main table in 'Using ARIA in HTML' is an interpretation, extension and clarification of the information in the WAI-ARIA section of HTML5 [1]. The WAI-ARIA section of HTML5 defines rules for use of ARIA in HTML and how ARIA roles,states and properties map to HTML features. The WAI-ARIA specification [2] defines ARIA roles,states and properties. The WAI-ARIA implementation guide [3] defines how ARIA is to be implemented in browsers. Advice for users (developers/authors) of WAI-ARIA is provided in WAI-ARIA 1.0 Authoring Practices [4] you wrote: "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>." > Using ARIA only describes how it owrks, it does not define anything, that is defined in the docs I cited. If it is the case that a developer is using a link, but it looks (via CSS) and acts (via scripting) like a button, then the first advice would be to use a HTML button, if this is not practical, then provide the correct role information to assistive technology using ARIA role. you wrote: "And I also see that role can also be a class like attribute, like > “presentation”, what’s the meaning?" > role=presentation is defined in WAI-ARIA 1.0, its effect is defined in the WAI-ARIA user agent inplementation guide, information for developers is provided in the WAI-ARIA authoring practices document [5] Further notes for developers are provided in Using ARIA in HTML [6] regards SteveF [1] http://dev.w3.org/html5/spec/wai-aria.html#wai-aria [2] http://www.w3.org/WAI/PF/aria/ [3] http://www.w3.org/WAI/PF/aria-implementation/ [4] http://www.w3.org/WAI/PF/aria-practices/ [5] http://www.w3.org/WAI/PF/aria-practices/#presentation_role [6] http://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html#notes On 5 July 2012 09:28, Sunyang (Eric) <eric.sun@huawei.com> wrote: > 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 what’s 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”, what’s the meaning?**** > > ** ** > > Sorry for so many questions ;)**** > > ** ** > > ** ** > > ** ** > ------------------------------ > > Yang Sun > Email: eric.sun@huawei.com > Huawei Technologies Co., Ltd. > http://www.huawei.com **** > ------------------------------ > > 本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁 > 止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中 > 的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件! > 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] > *发送时间:* 2012年6月29日 20:23 > *收件人:* HTMLWG WG > *抄送:* 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. > > <goog_994905413> > http://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.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 | www.HTML5accessibility.com | > www.twitter.com/stevefaulkner > HTML5: Techniques for providing useful text alternatives - > dev.w3.org/html5/alt-techniques/ > Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html > > **** >
Received on Thursday, 5 July 2012 10:04:07 UTC