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 16656 - Mapping of accessible actions from native semantics when overridden by @role
Summary: Mapping of accessible actions from native semantics when overridden by @role
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2012-04-07 07:53 UTC by Benjamin Hawkes-Lewis
Modified: 2012-04-18 11:36 UTC (History)
5 users (show)

See Also:

Attachments

Description Benjamin Hawkes-Lewis 2012-04-07 07:53:03 UTC 
In a recent email, Firefox developer Alexander Surkov writes:

> <a role=link href><img alt="Lorem ipsum."></a>
> role of html:a is link, action is "jump"
> role of img accessible is image, action is "jump" (inherited from
> html:a accessible)
>
> <a role=img href>
> role is html:a accessbile is image, action is "jump" since it's a
> still link after all.

http://lists.w3.org/Archives/Public/wai-xtech/2012Apr/0020.html

It is non-obvious that actions from native semantics should continue to be exposed to accessibility APIs when those semantics are overridden. Whether this is right or wrong, sounds like something the implementation guide should explicitly discuss.