- From: Philip Jägenstedt <philipj@opera.com>
- Date: Wed, 17 Feb 2010 13:37:18 +0800
- To: "Silvia Pfeiffer" <silviapfeiffer1@gmail.com>, "HTML Accessibility Task Force" <public-html-a11y@w3.org>
On Wed, 17 Feb 2010 11:44:32 +0800, Silvia Pfeiffer <silviapfeiffer1@gmail.com> wrote: > Hi all, and in particular media subgroup, > > Today we had a phone discussion about the JavaScript API spec and we > realised that we haven't actually specified the list of roles that the > @roles attribute should accept. > > So, I wanted to start a discussion on this with the goal of eventually > reaching a list that we can all agree on to cover the known use cases. > > Let me start by stating that in today's call everyone agreed that we > need to come up with a determined list of values for the roles, so if > you disagree with that, you should speak up now. In all discussions so far role is only an attribute that exists in the markup without having any influence on... well anything. I would like to see suggestions on how UAs should use roles (e.g. in a track selection algorithm) before investing effort in defining them. -- Philip Jägenstedt Core Developer Opera Software
Received on Wednesday, 17 February 2010 05:37:52 UTC