Toby Inkster wrote:
Andy Mabbett's proposed data: prefix already solves the abbr design
pattern accessibility issue
Andy made an honest stab at solving the issue; I don't think his
proposal is workable however.
In so far as end-users want to be able to ignore the data:
1. It requires
If the problem is 'machine readable dates get read out sometimes' I
don't see how the data: prefix solves that.
Screen readers may be configured to read out the title attribute for
abbr and acronym; perhaps also a and img. But they don't
automatically read out the contents of the title
I'm wondering, can you also configure screen readers to expand out
titles on any elements?
Adam
On 17 May 2008, at 22:46, Toby A Inkster wrote:
If the problem is 'machine readable dates get read out sometimes' I
don't see how the data: prefix solves that.
Screen readers may be configured
I'm wondering, can you also configure screen readers to expand out
titles on any elements?
Not any of which I'm aware. There is a good article on this issue here:
http://www.paciellogroup.com/resources/articles/WE05/forms.html
--
Toby A Inkster
mailto:[EMAIL PROTECTED]
On 17 May 2008, at 23:14, Adam Craven - Four Shapes wrote:
I'm wondering, can you also configure screen readers to expand out
titles on any elements?
Not as far as I'm aware. Titles may be read out for links, images,
form elements and abbreviations and that's about it. I definitely
Toby A Inkster wrote:
Not any of which I'm aware. There is a good article on this issue here:
http://www.paciellogroup.com/resources/articles/WE05/forms.html
Be warned that the data presented there is very old. While there are
plenty of people still using such old AT, Home Page Reader is no
