W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2009

[Bug 7470] JimJJewett gmail: The implications of these tables should also appear at element level -- e.g, td model or dom should mention aria- -- unless it is explicitly not exposed, for some reason.

From: <bugzilla@wiggum.w3.org>
Date: Tue, 22 Sep 2009 19:17:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1MqArZ-0005id-LY@wiggum.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7470


Jim Jewett <jimjjewett@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jimjjewett@gmail.com




--- Comment #2 from Jim Jewett <jimjjewett@gmail.com>  2009-09-22 19:17:21 ---
For example, the table in section 3.2.6 with the following thead

    <th>Language feature
    <th>Strong native semantics <span class=impl>and implied ARIA
semantics</span>

The first body row says that an <a> element has a strong native role of "link".
 But there is nothing in the <a> section
(http://www.whatwg.org/specs/web-apps/current-work/#the-a-element) to indicate
this.

(1)  I believe that the <a> section should indicate the aria-* semantics, when
these are specified.

(2)  I personally believe that the <a> DOM element should also expose this
information (including default values for aria-* attributes) to scripts and
CSS, but I grant that there is not consensus on that.  (And there may be strong
reasons not to, at least in the default or implicit case.)

-jJ


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 22 September 2009 19:17:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:01 UTC