- From: <bugzilla@jessica.w3.org>
- Date: Sat, 13 Aug 2011 06:02:25 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13436 --- Comment #12 from John Foliot <jfoliot@stanford.edu> 2011-08-13 06:02:25 UTC --- (In reply to comment #10) > > You don't understand how to file browser bugs. > > The spec doesn't mandate UI. Tab, this is not a browser bug tracker, it's the HTML5 bug tracker, and this is an editorial defect with the current Draft Spec. This bug was discussed by members of the accessibility task force media group and had support from members present at that discussion. This is not a UI requirement but rather a control requirement. You can make it a button, a drop-down menu or any other UI widget you want it to look like, but an accessible toggle mechanism is a MUST requirement whenever captions or other accessibility support materials are present. If you read the original bug, the phrase "...though such features should, again, not interfere with the page's normal rendering." is retained, so I am unclear why this seems so controversial. If you have a start button, you need a stop button. If you have optional asset(s) assigned to a media asset, you require a means to toggle it/them on or off. This is not a SHOULD, this is a MUST - how else will a user be able to interact with the option(s)? If a user-agent chooses (for example) to make their native controls operate as a "show/hide" effect (such as how YouTube operates today) then that control bar MUST contain the toggle when all other controls are presented to the user. This is not mandating the UI of the controls bar, only the components present on that controls bar. -- 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, 13 August 2011 06:02:27 UTC