W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: html 5 and accessibility issue - need of fallback content

From: Robert Burns <rob@robburns.com>
Date: Sun, 1 Jul 2007 16:22:19 -0500
Message-Id: <D387BA98-0330-4854-BCDE-C2BA536432A0@robburns.com>
Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, aurélien levy <aurelien.levy@free.fr>, public-html@w3.org
To: Henri Sivonen <hsivonen@iki.fi>

On Jul 1, 2007, at 4:11 PM, Henri Sivonen wrote:

> On Jul 2, 2007, at 00:01, Robert Burns wrote:
>> The author doesn't mention in the  prose any problem with AT.  
>> Could you provide some more details on your reading of that article?
> I scanned to the row "Uses &lt;embed&gt;" and located the columns  
> flagged "No". Then I scanned up each column and found yellow  
> (problem) cells in each one (one screen reader issue, one aural  
> browser issue and one old visual UA issue).

Well as is often the case, skimming like that is not sufficient. Even  
the first solution that uses embed is included in the approach I was  
advocating. Scripting is another drawback that the table doesn't  
quickly visually illustrate (in yellow), so they're are issues  
important to authors that the table doesn't illustrate. However,  
those are the types of details I'm not sure if we need to concern  
ourselves with. I think whenever we can we should encourage the  
deployment of implementations that make this basic stuff very easy  
for authors to do without any add-ons (including scripting). However,  
I will admit that some of those scripting solutions are quite  
elegant, but the table doesn't show that scripting drawback for quick  

Take care,
Received on Sunday, 1 July 2007 21:22:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:23 UTC