W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2010

[Bug 10448] Consider broadening the set of allowed roles for command elements

From: <bugzilla@jessica.w3.org>
Date: Sat, 02 Oct 2010 07:05:07 +0000
To: public-html-a11y@w3.org
Message-Id: <E1P1w9b-0007Qm-KJ@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448

Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xn--mlform-iua@xn--mlform-i
                   |                            |ua.no

--- Comment #5 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2010-10-02 07:05:07 UTC ---
(In reply to comment #4)

> I really don't understand the motivation here. How do any of these suggestions
> improve accessibility?

Consentrating on the anchor element:  It improves accessibility by sending
relevant information to the user.

An <a> element that doesn't take you to another location but instead activates
a player is better presented to AT as a button. 

That is how Yahoo's media player works (http://mediaplayer.yahoo.com/)
The Yahoo Media Player is simply a script which turns all the MP3 links into
player buttons.
And it was recently hailed as the most accessible solutio for uas which doesn't
support <audio>:
http://terrillthompson.blogspot.com/2010/09/quest-for-accessible-flash-mp3-player.html

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 2 October 2010 07:05:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:21 GMT