W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2014

Re: Broken Links and Redirects in Understanding and Techniques

From: Carlos A Velasco <carlos.velasco@fit.fraunhofer.de>
Date: Sat, 06 Sep 2014 13:15:58 +0200
Message-ID: <540AECEE.7060108@fit.fraunhofer.de>
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>, Christophe Strobbe <strobbe@hdm-stuttgart.de>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Dear Stefan,

Just for clarification. I do not think that your assertion is true. Our 
tool suite is able to validate (both markup and accessibility 
evaluation) at the server-side complete websites, and we use for it the 
rendered DOM of the page by integrating different rendering engines in 
our tools.

We do not need a browser for that.

On 09/05/2014 09:34 AM, Schnabel, Stefan wrote:
> Hi Christophe,
> which validators + accessibility validators do currently check using the *client-side browser DOM* and *not* server-side generated or static html? For instance, W3C Validator relies on protocols and *cannot* do this.
> I know e.g.  HTML Validator plugin for Firefox that can do this client-side: http://users.skynet.be/mgueury/mozilla/new_install4.html but validating an entire site with it is tedious since IMO there is no crawling mechanism integrated.
> Do you have a complete list of alternatives?
> ...

Best Regards, Mit freundlichen Grüßen, Saludos,

Dr Carlos A Velasco
   Fraunhofer Institute for Applied Information Technology FIT
   Web Compliance Center: http://imergo.com/ · http://imergo.de/
   Schloss Birlinghoven, D53757 Sankt Augustin (Germany)
   Tel: +49-2241-142609 · Fax: +49-2241-1442609
Received on Saturday, 6 September 2014 11:16:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:16 UTC