RE: Broken Links and Redirects in Understanding and Techniques

My colleague who is a regular user reports that:

SortSite does check the DOM.

Sortsite also attempt to flag up the differences between different browser DOMs. Try a scan of try.powermapper.com against http://mothereffingtoolconfuser.com to see what I mean.

More info about the tool there.

N
________________________________________
From: Schnabel, Stefan [stefan.schnabel@sap.com]
Sent: 05 September 2014 09:10
To: Neil Milliken; Aurélien Levy
Cc: w3c-wai-gl@w3.org
Subject: RE: Broken Links and Redirects in Understanding and Techniques

Do they also execute pure client-side checks?
It is IMPORTANT not to confuse this in the listing of validators :)

Regards
Stefan

-----Original Message-----
From: Neil Milliken [mailto:Neil.Milliken@bbc.co.uk]
Sent: Freitag, 5. September 2014 10:01
To: Aurélien Levy
Cc: w3c-wai-gl@w3.org
Subject: Re: Broken Links and Redirects in Understanding and Techniques

I have the Powermapper /sortsite set of tools.
Sent from my iPad

> On 5 Sep 2014, at 08:58, "Aurélien Levy" <aurelien.levy@temesis.com> wrote:
>
> Hi,
>
> in France we have at least two :
> reporting.opquast.com and www.tanaguru.com
>
> In Us, i think that tools of deque and hisoftware are doing that too
>
> Regards,
> Aurélien
>> 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?
>>
>> Regards
>> Stefan
>>
>> -----Original Message-----
>> From: Christophe Strobbe [mailto:strobbe@hdm-stuttgart.de]
>> Sent: Donnerstag, 4. September 2014 15:49
>> To: w3c-wai-gl@w3.org
>> Subject: Re: Broken Links and Redirects in Understanding and Techniques
>>
>>
>>> On 4/09/2014 13:34, Joshue O Connor wrote:
>>> #http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140902/G134.html
>>> The Peter Kranz link to 'Validating an entire site' is moved from
>>> http://www.standards-schmandards.com/?2005/04/10/18-massvalidate
>>>
>>> to
>>>
>>> http://www.standards-schmandards.com/2005/massvalidate/
>>>
>>> NOTE: Some of the validators are looking very old - and some articles
>>> are over 10 years old also.
>> Ah, validators. I know who collected those links ;-)
>>
>> The link to STG XML Validation Form leads to an Error 404 and I can't
>> find a replacement on Brown University's website.
>>
>> The URL for XML Nanny now leads to a site in Japanese that is apparently
>> not about XML validation. (There is a tool called "XML Nanny" for
>> validating XML and XHTML in the Mac App Store:
>> <https://itunes.apple.com/us/app/xml-nanny/id423791387?mt=12>.)
>>
>>> The link to 'XHTML-Schemata für FrontPage 2003 und Visual Studio .NET'
>>> should have the text 'XHTML-Schemata für FrontPage 2003 und Visual
>>> Studio .NET [In German]' included in the URI.
>>>
>>> '<a>Nvu</a> is a free and open-source Web authoring tool for Windows,'
>>> should be
>>> '<a>Nvu is a free and open-source Web authoring tool</a> for Windows,'.
>> Nvu was discontinued some time ago; its successor was Kompozer
>> <http://kompozer.net/>, which had its most recent release in ... 2010.
>>
>> With regard to XML editors:
>> * The link to SCREEM can be removed; the project has been inactive for
>> several years now.
>> * There have been no xerlin releases since 2005 (though the program may
>> still work (it's in Java).
>>
>> Best regards,
>>
>> Christophe
>>
>>> Including useful keywords in the Amaya link (an links to remaining XML
>>> editors) would also be useful for screen reader users.
>>> (...)
>
>
> --
> Aurélien Levy
> ----
> Temesis
>
>

Received on Wednesday, 10 September 2014 14:40:52 UTC