Bruce Lawson wrote:
I'm wondering if this is an appropriate used of details
snip
.. thereby acting as a discoverable-by-anyone longdesc. (The example is
adapted from the longdesc example at
http://webaim.org/techniques/images/longdesc#longdesc)
Note to grumpy people: I'm not trying to
Bjartur Thorlacius wrote:
As I understand details, it's for hiding the information contained
within from
users, but rendering it on command.
Correct, but it is the definition of 'hiding' that is under discussion here. If
it is just 'tucked away' but still in the page flow, is it really
[21:28] Dashiva Does anyone know when JF went from against wcag2 to being
for it?
Sometime between the 27 April 2006 Draft
(http://www.w3.org/TR/2006/WD-WCAG20-20060427/) and the 11 December 2007
Draft (http://www.w3.org/TR/2007/WD-WCAG20-20071211/)
I think it was on a Tuesday.
JF
I have been requested to forward on the following important information
regarding accessibility issues with the canvas element. If you have an
interest in this area, or have some suggestions on how to overcome some of
the known issues, then please consider actively following this W3C
discussion,
Maciej Stachowiak wrote:
(Probably the best way to do something like this (short of a realtime
sound API) would be the ability to queue up an audio file (or range
thereof) to play next when the current one finishes, because then the
media framework can take care of ensuring a smooth
James Graham wrote:
What's the easiest way to test existing aria implementations on
Mac/Linux (I don't have access to a Windows box)?
Firefox 3 + Accessibility Extensions for Mozilla
http://cita.rehab.uiuc.edu/software/mozilla/installation.php
JF
Silvia Pfeiffer wrote:
Sorry to be getting back to this thread this late, but I am trying to
catch up on email.
I'd like to contribute some thoughts on Ogg, CMML and Captions and
will cite selectively from emails in this thread.
snip
This would be problematic when downloading the
There have been a number of recent discussions regarding the requirement for
ALT text and the use of LONGDESC. Many of the suggestions and proposals
appear to be based on supposition rather than actual feedback. The
following email exchange from the WebAIM mailing list might give pause to
Maciej Stachowiak wrote:
This isn't my advice to the WebKit developers, this is my comment on a
bug report *as* a WebKit developer.
However, is it the comment of a WebKit developer or as a member of the HTML5
Working Group? This lack of transparency lends the impression that the spec
is
Earlier today, Lachlan Hunt posed the following question
[http://krijnhoetmer.nl/irc-logs/whatwg/20070823#l-271]:
# [04:40] Lachy why do people keep overreacting and bringing up the
headers issue all the time?!
http://lists.w3.org/Archives/Public/public-html/2007Aug/0926.html
# [05:15] Hixie
Dan Connolly wrote:
I sympathize with your frustration, but I ask that you remain patient.
Dan,
Thank you for your prompt response. While patience is indeed a virtue, my
(our?) patience is being sorely tested, as while the official word is that
we're nowhere near deciding anything, current
Dan Connolly wrote:
* Is Lachlan Hunt definitive when stating, HTML5 now defines the
usemap attribute as a Hashed ID Reference, not a URI, and can only
reference maps within the same document.
[https://bugzilla.mozilla.org/show_bug.cgi?id=189643], as well as
HTML5 currently will not be
.
Cheers!
JF
--
John Foliot
Web Accessibility Specialist
WATS.ca www.wats.ca
13 matches
Mail list logo
