Toby A Inkster wrote:
It is fair enough to take time to consider these things carefully before
issuing an edict (perhaps if that had been done to begin with we would
have never ended up with a broken datetime design pattern), but while
the community dithers over deciding upon a replacement,
Toby A Inkster wrote:
An example of the inaccessible datetime pattern can now be seen in the
Microsoft WebSlice whitepaper[1]. The further it spreads, the harder it
will be to fix.
1. http://code.msdn.microsoft.com/Release/ProjectReleases.aspx?
date directly on the page,
then hide the element containing the date with display:none?
Cheers
Jim
Original Message:
-
From: Toby A Inkster [EMAIL PROTECTED]
Date: Tue, 4 Mar 2008 15:53:12 +
To: microformats-discuss@microformats.org
Subject: [uf-discuss] Re: Putting microformats
Alasdair King wrote:
This is clearly a contentious statement. However, the fact that this
able, technical and motivated forum has been unable to come up with a
agreed accessible format in eighteen months strongly suggests it isn't
going to be able to do so with current assistive technology:
On 4/3/08 16:42, Andy Mabbett [EMAIL PROTECTED] wrote:
as I've pointed out before, the imminent release of Firefox
3, with native support for microformats, will see a significant leap in
public awareness of microformats.
Is this still true? My understanding was that native uf support would
On Mar 5, 2008, at 4:57 AM, Toby A Inkster wrote:
For example, the following:
span title=Monday 3 March 2008 (data:2008-03-03)
class=dtstartstarted two days ago/span
Is perfectly accessible in all tested screen readers (the read the
human-
readable started two days ago) and
Adam Craven - Four Shapes wrote:
Does anyone have suggestions how this can be worked around whilst still
keeping relatively good screen reader support?
You mentioned hiding the ABBR with CSS as a solution, but IE6 (which
plenty of screen readers hook into) ignores the ABBR element entirely
On Tue, March 4, 2008 15:53, Toby A Inkster wrote:
The fact is that the microformats datetime design pattern (and to a
lesser extent, the ABBR design pattern) suffers from major accessibility
problems. This has been known about and discussed for over 18 months,
with various alternatives being
I'd do two things:
1 Decide on a microformat that'll work, and ignore the accessibility
issues. If you do it well, then other sites will copy you and it'll
become a de facto standard. Then the assistive technology vendors
(like me) will code support for it into their solutions. There'll be a
lag,
