This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

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.
Summary: JimJJewett gmail: The implications of these tables should also appear at elem...
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://whatwg.org/specs/web-apps/curr...
Whiteboard:
Keywords: NoReply
Depends on:
Blocks:
 
Reported: 2009-08-31 17:35 UTC by contributor
Modified: 2010-10-04 14:29 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2009-08-31 17:35:44 UTC 
Section: http://whatwg.org/specs/web-apps/current-work/#annotations-for-assistive-technology-products

Comment:
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.

Posted from: 32.97.110.60
Comment 1 Ian 'Hixie' Hickson 2009-09-21 23:50:09 UTC 
Could you elaborate? I don't understand what you are asking for.
Comment 2 Jim Jewett 2009-09-22 19:17:21 UTC 
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
Comment 3 Ian 'Hixie' Hickson 2009-09-22 21:24:12 UTC 
For point 1, I don't really want to spread the information all over the document because it then becomes a maintenance nightmare. It's also not particularly useful information as far as I can tell; the table is needed for implementors, but the only reason it's relevant to authors is that it limits what they can override. If someone starts using ARIA, they're most likely to be adding ARIA everywhere at once, so it's more useful for the information to be in one place rather than dotted all over the place.

For point 2, please raise ARIA feature requests with the PWFG.
Comment 4 Maciej Stachowiak 2010-03-14 14:50:27 UTC 
This bug predates the HTML Working Group Decision Policy.

If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
  http://dev.w3.org/html5/decision-policy/decision-policy.html

This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.