- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 05 Feb 2010 20:25:44 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8885
Summary: Fallback mechanism for embedded content
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Keywords: a11y
Severity: normal
Priority: P2
Component: HTML5 spec bugs
AssignedTo: dave.null@w3.org
ReportedBy: ian@hixie.ch
QAContact: public-html-bugzilla@w3.org
CC: ian@hixie.ch, mike@w3.org, public-html@w3.org,
gez.lemon@gmail.com, public-html-a11y@w3.org
(Split from bug 8644.)
2. From an accessibility perspective, HTML5 should describe a model for
fallback content that allows the user to choose from any available fallbacks.
The problem with specifying that fallback content should only be "used when an
external resource cannot be used", is that it puts users in the position of
having to guess about the accessibility of the content on different sites and
to reconfigure their browser to find out if they guessed correctly. For
example, an author on one site might embed captioned video that requires a
plugin in order to be rendered with no fallback while an author on a second
site uses the same plugin to include a video, omits captions, but provides
fallback content that includes a text transcript of the video. The problem is
that a deaf user who has the required plugin installed will get the captions on
the first site, but will likely miss that there's no fallback on the second
site entirely. Similarly, if the same user does not have the required plugin
(or has turned it off so that they could access fallback content on another
site), they end up getting nothing on site 1 and the fallback content on site
2.
--
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 Friday, 5 February 2010 20:25:49 UTC