Fwd: [Bug 15948] New: <area> should be classified as "interactive content"

Everett Zufelt
Accessibility Consultant & Web Developer

Web
http://zufelt.ca
Phone (toll free U.S. & Canada)
1-877-ZUFELT-8 (1-877-983-3588)

Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



Begin forwarded message:

> Resent-From: "Michael[tm] Smith" <mike@w3.org>
> From: bugzilla@jessica.w3.org
> Subject: [Bug 15948] New: <area> should be classified as "interactive content"
> Date: 10 February, 2012 2:15:08 AM EST
> Resent-To: public-html@w3.org
> To: public-html@w3.org
> 
> https://www.w3.org/Bugs/Public/show_bug.cgi?id=15948
> 
>           Summary: <area> should be classified as "interactive content"
>           Product: HTML WG
>           Version: unspecified
>          Platform: PC
>               URL: http://dev.w3.org/html5/spec/content-models.html#inter
>                    active-content-0
>        OS/Version: All
>            Status: NEW
>          Severity: major
>          Priority: P2
>         Component: HTML5 spec (editor: Ian Hickson)
>        AssignedTo: ian@hixie.ch
>        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
>         QAContact: public-html-bugzilla@w3.org
>                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
>                    public-html@w3.org
> 
> 
> Created attachment 1076
>  --> https://www.w3.org/Bugs/Public/attachment.cgi?id=1076
> Demo of how a <area> styled look like <a>
> 
> It is inconsistent:
> 
> * that <area> has 'link' role within the WAI ARIA section [1], 
> * and yet the element isn't  listed as 'interactive content'. [2]
> 
> For example, a consequence of the current status is that it is conforming to
> place an <area> element inside an <a> element: 
> 
>      <a href=foo ><area href=foo ></a>
> 
> I don't rule out that it could make sense to nest <area> inside <a>. However,
> for the most part, it would only leads to trouble. For instance, screenreaders
> are likely to hear the same link announced twice.
> 
> But even if it can be justified to permit <area> inside <a>, the <area> should
> still be treated as interactive content, and instead a special exception to the
> rule which says that interactive content cannot be the child of an <a> should
> be made.
> 
> The justification for why <area> must be considered interactive content is that
> when the image of an image map does not display -  or otherwise when it is
> wanted, then one can make <area> visible via area{display:inline-block} and
> area:before{content:attar(alt)} etc. In that case, one can also navigate to the
> <area> link via tabulation or click it with the mouse and it reacts to :focus.
> In other words: It attains all the interactive features of <a>.
> 
> Demo of how a <area> styled look like <a>: http://tinyurl.com/7detoab 
> (Or use the attached variant - if your browser does not support data URIs.)
> 
> [1] http://dev.w3.org/html5/spec/wai-aria.html#table-aria-strong
> [2] http://dev.w3.org/html5/spec/content-models.html#interactive-content-0
> 
> -- 
> Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> 
> 
>