W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2012

Re: Evaluating an iframe-based website

From: Charles McCathieNevile <chaals@opera.com>
Date: Mon, 27 Feb 2012 17:12:22 +0100
To: "Michael S Elledge" <elledge@msu.edu>, Ramón Corominas <listas@ramoncorominas.com>
Cc: "WAI Interest Group" <w3c-wai-ig@w3.org>
Message-ID: <op.wachywpzwxe0ny@widsith.eng.oslo.osa>
I think the failure Mike noted is a systemic one - the title won't change.  
You may find other failures that are systemic because of the context -  
while some individual pages in the frame may have a failure in which case  
you should record it against the URI of that content.

Essentially, you need to identify how to *fix* the failures - if there is  
a failure in something it doesn't meet the requirements. Whether that is a  
major and serious problem, or a relatively trivial problem, depends on the  
circumstances. But you either pass, or fail...

You could of course conclude that certain parts of the site have no  
failures (if that is the case - which would require no failures that come  
 from being in their frame context i.e. fixing things like the title),  
while others have whatever problems you identify.

hope that is helpful


On Mon, 27 Feb 2012 16:33:07 +0100, Ramón Corominas  
<listas@ramoncorominas.com> wrote:

> Not exactly, since the title can be dynamically changed using JavaScript  
> (although of course they are not doing it now).
> My question comes because I feel that I cannot consider the iframe-based  
> content as separate from its parent, because it could lead to failures  
> that would not exist when this content is in context (for example,  
> heading structure, links purpose, multiple ways...). So I cannot  
> separate the iframe from its context, but at the same it sounds a bit  
> hard to me that one failure in one of the pages would imply the whole  
> website (the single URI) to fail.
> Thanks,
> Ramón.
> Mike wrote:
>> When we evaluate sites we treat the frames as separate pages, and the  
>> iFrame wrapper has its own identity. You'll also need to review the  
>> entire page (wrapper + iFrame) together, however, so you can evaluate  
>> their interaction.  Btw, you've already identified one failure on the  
>> site that is a common problem with frame-based websites: that the page  
>> title doesn't change to reflect page content.

Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg kan litt norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Monday, 27 February 2012 16:14:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:39 UTC