RE: Comments and thoughts about WCAG 2.0

Hi again,

Look at the bottom.


> > I don't know where are you going with this or what is your use case, but
> my understanding is the following:
> >
> > At http://example.org/frames.html you have:
> >
> > ...
> > <frameset ROWS="20%,*,20%">
> >   <frame src="frm1.html" title="Title1" id="one" />
> >   <frame src="frm2.html" title="Title2" id="two" />
> >   <frame src="frm3.html" title="Title3" id="three" />
> >   <noframes>
> >     <p><a href="whatever.html">Whatever</a></p>
> >   </noframes>
> > </frameset>
> > ...
> >
> > At http://example.org/frm1.html, http://example.org/frm2.html and
> http://example.org/frm3.html you have whatever html.
> >
> > Then, at the results level you can have:
> >
> > <earl:Assertion rdf:ID="assertion1">
> >   <earl:assertedBy rdf:resource="#assertor"/>
> >   <earl:result rdf:resource="#failure"/>
> >   <earl:test rdf:resource="#badtitles"/>
> >   <earl:subject rdf:resource="http://example.org/frames.html"/>
> > </earl:Assertion>
> >
> > Or
> >
> > <earl:Assertion rdf:ID="assertion2">
> >   <earl:assertedBy rdf:resource="#assertor"/>
> >   <earl:result rdf:resource="#ok"/>
> >   <earl:test rdf:resource="#whatever"/>
> >   <earl:subject rdf:resource="http://example.org/frm1.html"/>
> > </earl:Assertion>
> >
> > Or
> >
> > <earl:Assertion rdf:ID="assertion3">
> >   <earl:assertedBy rdf:resource="#assertor"/>
> >   <earl:result rdf:resource="#failure"/>
> >   <earl:test rdf:resource="#whatever"/>
> >   <earl:subject rdf:resource="http://example.org/frm2.html"/>
> > </earl:Assertion>
> 
> Yes, this is the initial state. Now consider that some other HTML
> document is loaded in frame "one". The state is changed. But this cannot
> be distinguished from the initial state only by referencing
> http://example.org/frames.html.

If you load some other HTML document, let's say "frm4.html", in frame "one" nothing has really changed at frames.html. Assertion1 remains valid and whatever thing that affects to frm4 could be addressed like:

<earl:Assertion rdf:ID="assertion4">
   <earl:assertedBy rdf:resource="#assertor"/>
   <earl:result rdf:resource="#failure"/>
   <earl:test rdf:resource="#whatever"/>
   <earl:subject rdf:resource="http://example.org/frm4.html"/>
</earl:Assertion>

> Again, I don't say that this is in scope of EARL, but you may need
> something if you want to record results about the changed state of the
> frameset in EARL.

Again, I think there are two different questions here:

1 - IMO there's no such change of state in a frameset because the content of each single URI remains intact and also the EARL Assertions.

2 - There may be real changes of state in other uses cases, typically AJAX and such things. This may be a problem for EARL as the Assertions may become invalid without noticing it.

In summary, my understanding is that the only problem here is we don't have a way to ensure the current state of test subjects (checksum or similiar) and it may be necessary in some cases to check if an assertion remains valid (still don't think this is the case of framesets)

Regards,
 CI.

________________

Carlos Iglesias

Fundación CTIC
Parque Científico-Tecnológico de Gijón
33203 - Gijón, Asturias, España

teléfono: +34 984291212
fax: +34 984390612
email: carlos.iglesias@fundacionctic.org
URL: http://www.fundacionctic.org

Received on Wednesday, 5 March 2008 12:22:30 UTC