W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2005

Re: 4.2 WCAG 1.0 Checkpoint

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Tue, 22 Nov 2005 19:21:01 +0000
Message-ID: <43836F9D.7010501@splintered.co.uk>
To: w3c-wai-ig@w3.org

Christophe Strobbe wrote:

> At 17:40 22/11/2005, Patrick Lauke wrote:
> <blockquote>
> Keep in mind that Internet Explorer does not support ABBR...
> </blockquote>
> 
> What exactly is the evidence for this statement?

> Does it mean that certain information is not in the DOM? That screen 
> readers can't access the title attribute of abbr because of lacking 
> support in IE (not the screen reader!)?

Well, Gez and Jon covered the answer, but I'd add: even *if* abbr was
in IE's DOM but the browser simply chose to completely ignore it, I'd 
contentiously ask from a pragmatic point of view: what use would it be 
then to the majority of web users if the browser didn't present them the 
expanded abbreviation in any useful form? Particularly if we're talking 
(like David's original remark) about "a learning or age-related 
impairment" - which does not automatically mean "they're using a screen 
reader"?

-- 
Patrick H. Lauke
__________________________________________________________
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com
__________________________________________________________
Web Standards Project (WaSP) Accessibility Task Force
http://webstandards.org/
__________________________________________________________
Received on Tuesday, 22 November 2005 19:21:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:23 GMT