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

Re: html 5 and accessibility issue

From: Anne van Kesteren <annevk@opera.com>
Date: Sat, 30 Jun 2007 17:36:47 +0200
To: "Robert Burns" <rob@robburns.com>
Cc: "aurelien levy" <levy@tektonika.com>, public-html@w3.org
Message-ID: <op.tuqqzlxr64w2qv@annevk-t60.oslo.opera.com>

On Sat, 30 Jun 2007 17:28:58 +0200, Robert Burns <rob@robburns.com> wrote:
> On Jun 30, 2007, at 9:08 AM, Anne van Kesteren wrote:
>> On Sat, 30 Jun 2007 15:53:39 +0200, aurelien levy <levy@tektonika.com>  
>> wrote:
>>> - actually their is no fallback content for embed element
>>
>> Why is that needed for plugins?
>
> That's when fallback content is needed: for non-text media (that is  
> sometimes serviced through plug-ins).

Isn't that a problem with the plugin?


> [...]
>
> However, if it said that the type of the iframe @src had to begin with  
> "text/  or "application/xml" then that might be sufficient. Simply  
> saying a browser context could lead authors to think a direct @src link  
> to an image or other non-text media was allowed (even PDF or Flash might  
> require fallback content since those do not have the accessibility  
> capabilities of HTML).

Well, yes, if you want to make things inaccessible you can do that.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Saturday, 30 June 2007 15:37:05 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:46 UTC