- From: <bugzilla@jessica.w3.org>
- Date: Sat, 13 Aug 2011 09:34:26 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13436
Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bhawkeslewis@googlemail.com
--- Comment #13 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2011-08-13 09:34:25 UTC ---
(In reply to comment #12)
> > The spec doesn't mandate UI.
[snip]
> 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.
As always, by UI Tab does not mean *just* how the interface looks, or what
widgets the interface uses, but also what the interface *is* - that is the
specific functionality that user agents offer the users based on the semantics
of the markup language and its APIs (their "feature sets", if you prefer). That
would include "control requirements".
In general, the spec tries to specify what the language and its APIs mean, not
what consuming software should do with that on the user's behalf. This frees
user agents to act in the best interests of their user given their specific use
case.
In this case, I don't see how your proposed text change would make any sense
for user agents like wget that do not display content, or printers that do not
allow interaction with content, or any user agent that does not have access to
sound output and therefore cannot "display" audio description tracks.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Saturday, 13 August 2011 09:34:27 UTC