Comments on: hAccessibility, one year on

By: Some links for light reading (30/4/08) | Max Design

Some links for light reading (30/4/08) | Max Design — Sun, 31 Jan 2010 12:27:01 +0000

[...] hAccessibility, one year on [...]

By: Eat your greens! » 34th Annual Blackheath & Greenwich Amnesty Book Sale

Eat your greens! » 34th Annual Blackheath & Greenwich Amnesty Book Sale — Tue, 05 Jan 2010 23:47:52 +0000

[...] PS. No tags were harmed during the making of this blog post. [...]

By: Andy Mabbett

Andy Mabbett — Sun, 10 Aug 2008 13:11:24 +0000

On checking my archives for an unrelated discussion, I found today that I first raised issues with abbr-abuse on 24 April 2006, much earlier than I thought I had done so. The cabal was in denial, even then.

By: Frances Berriman

Frances Berriman — Fri, 16 May 2008 14:38:14 +0000

By the way – just wanted to ping: http://fberriman.com/2008/05/16/the-bbc-needs-you/ – if you (or anyone else) can help in any way? Thanks Bruce

By: Andy Mabbett

Andy Mabbett — Mon, 05 May 2008 15:41:16 +0000

@Cerbera: You may not be able to “keep a straight face”, but you have also failed to respond to the challenge to come up with a better, more accessible, usable and valid method than the “data:” prefix proposal. HTML5 is, at best, a decade-and-a-half away from widespread deployment in the real world. It may be a useful fix then, but for now it’s just a red herring.

@Eric Meyer: Do you think , as currently used in microformats, is accessible and understandable? Or do you think people will perhaps understand it to mean 1 January 2009, and not, as it is used, 31 December 2008?

@Bruce/ Mike: Yes, people are are being stone-walled. Stone-walling is an oft-used – and documented – tactic of the unelected cabal running the microformats “community”.

By: Ben 'Cerbera' Millard

Ben 'Cerbera' Millard — Thu, 01 May 2008 22:40:52 +0000

Accessify Forums is back up, so you can read the most recent Microformats thread. It includes links to past threads about Microformat accessibility. Good analogy to text sizing, Bruce. Framing this debate as being about custom settings in screen readers is missing the point, imho. Data in title affects everyone using a device which implements HTML4 title according to the specification. Try hovering your mouse over any , or with data in its title value. Then explain how that's a user-friendly design choice while keeping a straight face. I can't manage that! :) It's worth mentioning HTML5 for the time and date cases. But letting the data- attributes have meaning to UAs seems more widely useful than enshrining one particular use-case, to me.