gmane.comp.web.wordpress.devel

ATAG Compliance

Joe Clark[1] has graciously run down the Authoring Tool Accesibility 
Guidelines and graded WordPress on each point. His findings are here:

http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html

There are some opportunities for improvement here. Joe has said we're 
free to put it in the Codex if someone wants to volunteer for that.

[1] http://joeclark.org/

--

-- 
Matt Mullenweg
  http://photomatt.net | http://wordpress.org
http://automattic.com | http://akismet.com

headers

Michael E. Hancock | 31 Jan 03:27

Re: ATAG Compliance

From: "Matt Mullenweg" <m <at> mullenweg.com>
> Joe Clark[1] has graciously run down the Authoring Tool Accesibility 
> Guidelines and graded WordPress on each point. His findings are here:
> 
> http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html
> 
> There are some opportunities for improvement here. Joe has said we're 
> free to put it in the Codex if someone wants to volunteer for that.

First pass at:
http://codex.wordpress.org/WordPress_ATAG_Evaluation

~~~~MichaelH

headers

Phillip Pearson | 31 Jan 05:44

Re: ATAG Compliance

btw - section 3.1 - I think the ATAG document is suggesting a preview 
mode that renders HTML like Lynx does, i.e. one that displays 
alternative content INSTEAD of the primary content.  There's no 
contraction here - this is not your usual preview mode, it's a *second* 
preview mode that shows how your HTML will appear to users who can't 
view images, etc.

Cheers,
Phil

Michael E. Hancock wrote:

>From: "Matt Mullenweg" <m <at> mullenweg.com>
>  
>
>>Joe Clark[1] has graciously run down the Authoring Tool Accesibility 
>>Guidelines and graded WordPress on each point. His findings are here:
>>
>>http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html
>>
>>There are some opportunities for improvement here. Joe has said we're 
>>free to put it in the Codex if someone wants to volunteer for that.
>>    
>>
>
>First pass at:
>http://codex.wordpress.org/WordPress_ATAG_Evaluation
>
>~~~~MichaelH
>_______________________________________________

(Continue reading)

headers

Roy Schestowitz | 31 Jan 06:29

Re: ATAG Compliance

_____/ On Tue 31 Jan 2006 04:44:59 GMT, [Phillip Pearson] wrote : \_____

> Michael E. Hancock wrote:
>
>> From: "Matt Mullenweg" <m <at> mullenweg.com>
>>
>>> Joe Clark[1] has graciously run down the Authoring Tool 
>>> Accesibility Guidelines and graded WordPress on each point. His 
>>> findings are here:
>>>
>>> http://joeclark.org/access/webaccess/WordPress-ATAG-evaluation.html
>>>
>>> There are some opportunities for improvement here. Joe has said 
>>> we're free to put it in the Codex if someone wants to volunteer for 
>>> that.
>>>
>>
>> First pass at:
>> http://codex.wordpress.org/WordPress_ATAG_Evaluation
>>
>> ~~~~MichaelH
>
> btw - section 3.1 - I think the ATAG document is suggesting a preview 
> mode that renders HTML like Lynx does, i.e. one that displays 
> alternative content INSTEAD of the primary content.  There's no 
> contraction here - this is not your usual preview mode, it's a 
> *second* preview mode that shows how your HTML will appear to users 
> who can't view images, etc.
>
> Cheers,

(Continue reading)