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 10446 - Consider limiting the roles of certain media and plugin elements
Summary: Consider limiting the roles of certain media and plugin elements
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf, aria, media
Depends on:
Blocks: 10066 10482
  Show dependency tree / graph
 
Reported: 2010-08-26 10:03 UTC by Maciej Stachowiak
Modified: 2010-12-15 14:45 UTC (History)
9 users (show)

See Also:

Attachments

Description Maciej Stachowiak 2010-08-26 10:03:00 UTC 
The following embedding elements currently allow any role:

audio, embed, iframe, object, svg, video

However, it does not really make sense to use these as an arbitrary widget or landmark. Consider the following limitations:

audio -> no role, application
embed -> no role, application, document, image
object -> no role, application, document, image
svg -> no role, application, document, presentation, image
video -> no role, application
Comment 1 Henri Sivonen 2010-08-26 11:03:37 UTC 
svg can be used to create just about any widget from primitive shapes and event handlers, so I'd expect svg to be able to take any role.
Comment 2 Maciej Stachowiak 2010-08-26 12:03:28 UTC 
(In reply to comment #1)
> svg can be used to create just about any widget from primitive shapes and event
> handlers, so I'd expect svg to be able to take any role.

Good point. And people do in fact use SVG to build arbitrary widgets.
Comment 3 Ian 'Hixie' Hickson 2010-08-26 19:41:56 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: see diff given below
Rationale: Concurred with reporter's comments, except "svg" is up to the SVG WG.
Comment 4 contributor 2010-08-26 19:42:28 UTC 
Checked in as WHATWG revision r5366.
Check-in comment: Provide more ARIA role mappings for embed,audio,video,iframe,object
http://html5.org/tools/web-apps-tracker?from=5365&to=5366
Comment 5 Leif Halvard Silli 2010-08-28 16:06:09 UTC 
Ian (and Maciej, too!): The bug was fixed incorrectly: There is no ARIA role "image". The correct role is "img". Relates to embed and object (and svg).
Comment 6 Maciej Stachowiak 2010-08-29 01:09:19 UTC 
Mea culpa. Leif is correct that it should be "img".
Comment 7 Maciej Stachowiak 2010-08-29 01:26:46 UTC 
I filed bug 10486 about the new issue about the spelling of "image" vs "img". Closing this bug.
Comment 8 Michael Cooper 2010-12-15 14:45:27 UTC 
Bug triage sub-team notes there is active discussion, and this appears to meet the threshold of being of interest to the HTML A11Y TF. Adding a11ytf keyword. 

Also considered question of whether roles of media elements affect processing of media. Adding the media keyword so the media sub-team can weigh in on this.