This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"3.2.7.3 Strong Native Semantics" <map> has no consistent display or role across browsers. IE no role or display properties FF IA2 textframe no display properties Chrome not role display:inline
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: added <map> to strong semantics table with no role Rationale: is a good candidate for restrictions as it has non consistent display and role properties across browsers
(In reply to steve faulkner from comment #1) > Change Description: added <map> to strong semantics table with no role Steve, can you point out please what 'no role' means in this context? > Rationale: is a good candidate for restrictions as it has non consistent > display and role properties across browsers
(In reply to alexander surkov from comment #2) > (In reply to steve faulkner from comment #1) > > > Change Description: added <map> to strong semantics table with no role > > Steve, can you point out please what 'no role' means in this context? > > > Rationale: is a good candidate for restrictions as it has non consistent > > display and role properties across browsers hi alex, "The entry "no role", when used as a strong native semantic, means that no role can be used (BY THE AUTHOR) and that the user agent has no default mapping to ARIA roles. (However, it could have its own mappings to the accessibility layer.) When used as a default implicit ARIA semantic, it means the user agent has no default mapping to ARIA roles. (However, it could have its own mappings to the accessibility layer.)" http://www.w3.org/html/wg/drafts/html/master/dom.html#concept-role-none
Thanks, Steve. Not related to this bug I'm getting worried that ARIA becomes a measure of things. Is it plausible that one day HTML will be mapped to ARIA rather than AT API (what makes HTML a11y mapping guide no sense)?
(In reply to alexander surkov from comment #4) > Thanks, Steve. Not related to this bug I'm getting worried that ARIA becomes > a measure of things. Is it plausible that one day HTML will be mapped to > ARIA rather than AT API (what makes HTML a11y mapping guide no sense)? Hi alex, did you read this email from rich (i emailed you a while back about it) http://lists.w3.org/Archives/Public/public-html-a11y/2014Jan/0040.html and the related outlines: http://www.w3.org/WAI/PF/wiki/ARIA ?
apparently I missed it, thanks again.