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 21164 - modify header and footer aria info
Summary: modify header and footer aria info
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P3 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, aria
Depends on:
Blocks: 21866
  Show dependency treegraph
 
Reported: 2013-03-01 05:55 UTC by steve faulkner
Modified: 2013-04-29 12:34 UTC (History)
5 users (show)

See Also:


Attachments

Description steve faulkner 2013-03-01 05:55:55 UTC
modify the ARIA mapping info for header and footer to reflect the webkit implementation and expected Firefox implementation. After discussion with implementers it has been agreed that mapping header to banner and footer to contentinfo when not a child of an article or section element (as per webkit) is a good way to go. So reflect this in the ARIA mapping table in the spec: http://www.w3.org/html/wg/drafts/html/master/dom.html#wai-aria
Comment 1 steve faulkner 2013-03-01 06:16:04 UTC
refer to webkit https://bugs.webkit.org/show_bug.cgi?id=78992
Comment 2 steve faulkner 2013-03-01 06:25:31 UTC
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: Accepted
Change Description: https://github.com/w3c/html/commit/6c5c62dbc4c6674d41b263c4aea6659103995b8f
Rationale: Spec now reflects one implementation (webkit) and planned implementation (Firefox)