Re: adding accessibility test suite

"Arnaud Desitter" <[email protected]>
Newsgroups gmane.comp.web.html-tidy.devel
Message-ID <[email protected]>
Thanks. This is http://tidy.sf.net/feature/1169854.

----- Original Message ----- 
From: "Chris Ridpath" <[email protected]>
To: "Arnaud Desitter" <[email protected]>; 
<[email protected]>; "Terry Teague" 
<[email protected]>
Cc: "Mike Lam (Utoronto.ca)" <[email protected]>
Sent: Thursday, March 24, 2005 7:01 AM
Subject: Re: [Tidy-dev] adding accessibility test suite


> Hi Arnaud,
>
> Thanks for adding the accessibility checking to the Tidy code base. Here's 
> the list of accessibility checks that should be removed or disabled:
>
> Warning number [1.1.1.11] - Priority 1
> All images require text equivalents including those used to identify items 
> in a list. If an image is used as a bullet, it should include the 
> following "alt" text: alt="*" or alt="bullet".
>
> Warning number [1.1.1.12] - Priority 1
> All images require text equivalents including those used to indicate 
> breaks within a web page. If an image is used as a horizontal rule, it 
> should include the following "alt" text: alt="*" or alt="horizontal rule".
>
> Error number [10.2.1.1] - Priority 2
> Create a clear association between a form control and its label by 
> ensuring labels are positioned properly within html markup. Do not 
> separate a label from its form control with additional text, images, etc. 
> If there are two or more controls on a single line, labels should be 
> placed immediately before its corresponding control or place each label 
> and control on a separate line.
>
> Error number [10.2.1.2] - Priority 2
> Create a clear association between a form control and its label by 
> ensuring labels are positioned properly within html markup. Do not 
> separate a form control from its label with additional text, images, etc. 
> If there are two or more controls on a single line, labels should be 
> placed immediately after its corresponding control or place each label and 
> control on a separate line.
>
> Error number [10.4.1.1] - Priority 3
> Include default text for all <input> form controls. Placing default text 
> in form fields enables keyboard users to insert a cursor into placeholder 
> text or characters and enter their own data.
>
>
> Error number [10.4.1.2] - Priority 3
> Default text for all <input> form controls must include an actual value. 
> Null (i.e. value="") is not valid default text but using placeholder 
> characters (i.e. value="****") is acceptable. Placing default text in form 
> fields enables keyboard users to insert a cursor into placeholder text and 
> enter their own data.
>
> Error number [10.4.1.3] - Priority 3
> Default text for all <input> form controls must include an actual value. 
> Including spaces (i.e. value=" ") in default text is not allowed but using 
> placeholder characters (i.e. value="****") is acceptable. Placing default 
> text in form fields enables keyboard users to insert a cursor into 
> placeholder text and enter their own data.
>
>
> Error number [13.1.1.5] - Priority 2
> Avoid ambiguous link text such as "more". Create link text that remains 
> meaningful even when read out of context. Identify the purpose or target 
> of each link (i.e. describe the destination of the link) and keep the text 
> concise.
>
>
> Error number [13.1.1.6] - Priority 2
> Avoid ambiguous link text such as "follow this". Create link text that 
> remains meaningful even when read out of context. Identify the purpose or 
> target of each link (i.e. describe the destination of the link)and keep 
> the text concise.
>
>
> We'd like to eventually bring these accessibility tests up to date with 
> the test suite being developed for the WCAG 2 but that is still months 
> away.
>
> Cheers,
>
> Chris
>
> ----- Original Message ----- 
> From: "Chris Ridpath" <[email protected]>
> To: "Arnaud Desitter" <[email protected]>; 
> <[email protected]>; "Terry Teague" 
> <[email protected]>
> Cc: "Mike Lam (Utoronto.ca)" <[email protected]>
> Sent: Thursday, March 17, 2005 1:31 AM
> Subject: Re: [Tidy-dev] adding accessibility test suite
>
>
>>> For the moment and very pragmatically, would you mind if the first 
>>> generation
>>> test suite (http://www.aprompt.ca/Tidy/) was added to the tidy source 
>>> base
>>> (using the w3 license) ?
>>>
>> That is OK with me.
>>
>> There are a couple of the tests that are now obsolete and should be 
>> removed. Could I send you a list of these tests so they could be disabled 
>> or removed?
>>
>> Chris
>>
>
> 



-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.