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

RE: Evaluating an iframe-based website

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Mon, 27 Feb 2012 11:25:06 -0500
Message-ID: <6d978305813c78368784e2306982ed58@mail.gmail.com>
To: WAI Interest Group <w3c-wai-ig@w3.org>
[Ramon wrote]
> 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

You should be able to locate the URI for that frame from the DOM and the
crub trail  and indicate the site except that page meet the conformance
level criteria.

While I agree that the page cannot be taken out of its context as far as
reporting - for normative testing purposes I would generally test the each
iFrame was a page and the containing page as a separate page.  During
functional testing the pages together would be taken into consideration.

Jonathan


-----Original Message-----
From: Ramón Corominas [mailto:listas@ramoncorominas.com]
Sent: Monday, February 27, 2012 10:33 AM
To: Michael S Elledge
Cc: WAI Interest Group
Subject: Re: Evaluating an iframe-based website

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.
Received on Monday, 27 February 2012 16:25:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 February 2012 16:25:54 GMT