13628 2011-08-03 19:56:45 +0000 Aside element should accept for attribute 2011-08-14 09:28:55 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified All All RESOLVED WONTFIX a11y P2 normal --- 1 gcl-0039 contributor annevk bhawkeslewis ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52223 0 gcl-0039 2011-08-03 19:56:45 +0000 The aside element should accept the for attribute (as does the label element) so that it can identify itself as related to something on the page (e.g. the main article) even if it is located elsewhere (e.g. in a side panel). The spec currently says that aside is always related to the content that contains the aside element, and it's not clear whether or how the author could then position it in a side panel or navigation area. There may be other elements to which this would also apply. 54044 1 mike 2011-08-04 05:35:38 +0000 mass-move component to LC1 54332 2 bhawkeslewis 2011-08-06 12:22:43 +0000 (In reply to comment #0) > The aside element should accept the for attribute (as does the label element) > so that it can identify itself as related to something on the page (e.g. the > main article) even if it is located elsewhere (e.g. in a side panel). The spec > currently says that aside is always related to the content that contains the > aside element, and it's not clear whether or how the author could then position > it in a side panel or navigation area. CSS, perhaps using a feature such as the proposed move-to property: http://www.w3.org/TR/css3-content/#moving @for might be useful as a bridging technology, but @aria-flowto could probably do this work already: http://www.w3.org/TR/wai-aria/states_and_properties#aria-flowto -- Benjamin Hawkes-Lewis 54950 3 annevk 2011-08-14 09:28:55 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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>. Status: Rejected Change Description: no spec change Rationale: You can use CSS.