- From: Chris Ridpath <chris.ridpath@utoronto.ca>
- Date: Wed, 7 Nov 2001 10:04:18 -0500
- To: "J. David Bryan" <jdbryan@acm.org>, "HTML Tidy List" <html-tidy@w3.org>
- Cc: <tidy-develop@lists.sourceforge.net>
> Note that for > this purpose, I don't intend to compile the source, but rather merely read > it to understand why a particular warning or error is being raised. > If you're interested in looking at why we perform the accessibility checks, check out the "Techniques for Accessibility Evaluation And Repair Tools" document: http://www.w3.org/TR/AERT Chris ----- Original Message ----- From: "J. David Bryan" <jdbryan@acm.org> To: "HTML Tidy List" <html-tidy@w3.org> Cc: <tidy-develop@lists.sourceforge.net>; <chris.ridpath@utoronto.ca>; <mikes.lam@utoronto.ca> Sent: Tuesday, November 06, 2001 1:37 PM Subject: [Tidy-dev] Re: Accessibility checking in Tidy > On 6 Nov 2001, at 0:54, Terry Teague wrote: > > > I will try to make binaries available in a couple of days. I will post a > > msg to the list when ready. > > Thanks. > > > > The purpose of this discussion is to determine how best to make the > > source available - it is not quite ready for release. What I am really > > waiting on is documentation - I think that would be more useful to > > explain what is checked. > > Documentation would be preferred, but in its absence, and presuming that > the source indicated why particular errors or warnings were being > generated, then even "not quite ready" source would help me to make > intelligent comments regarding the accessibility checks. Note that for > this purpose, I don't intend to compile the source, but rather merely read > it to understand why a particular warning or error is being raised. > > -- Dave > > _______________________________________________ > Tidy-develop mailing list > Tidy-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tidy-develop
Received on Wednesday, 7 November 2001 10:04:44 UTC