[wp-accessibility] Let's get started on improving WordPress accessibility

[Aaron D. Campbell]

The read more links can be easily adjusted by doing something like:
the_content('Read the rest of <em>'.the_title('','',false).'</em> &raquo;');

However, while the reply link text can be changed, you can't make it 
specific to the comment.  It seemed like a quick patch was in order, 
which I made and posted on trac 
(http://core.trac.wordpress.org/ticket/10569).  Please give it a look, 
test it, and comment on trac.

Tynan Colin Beatty wrote:
> Let's see, since I'm jumping in here completely unaware of previous 
> reports, I'll get the ball rolling by bringing up one of the most 
> glaring issues that I've encountered:
> Repetetive/non-descriptive link anchors need to be more descriptive 
> and unique. This applies to comment 'reply' links, 'read more' links, 
> etc. The current preferred technique is to place excess text into a 
> span and then use css to make that span 1 pixel and place it outside 
> of the viewable screen area as describe here: 
> http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C7
> I'm uncertain as to how this would affect the 'reply' situation, 
> should WordPress Trac ticket #10550 ( 
> http://core.trac.wordpress.org/ticket/10550 ) be resolved by changing 
> the links to form inputs; but as it is now, this particular case 
> should be resolved by adding comment id #s into the hidden spans, like 
> <a>reply <span class="hide-me">to comment #</span></a> or similar.
> 'Read more' can be supplemented by titles. Any other repetetive / 
> unclear anchors should also be similarly supplemented to comply with 
> this guideline. Thoughts?
>
> On Thu, Aug 6, 2009 at 9:38 PM, Lynne Pope <lynne.pope at gmail.com 
> <mailto:lynne.pope at gmail.com>> wrote:
>
>     First off, I wish to thank "the powers that be" for responding to
>     my request for this mailing list.
>     I believe that by discussing and proposing changes to improve
>     WordPress accessibility those of us with expertise in this area
>     can make a significant difference.
>
>     Let's see if we can gather together all reports of accessibility
>     issues and/or concerns, look at what needs to be done at the code
>     level to correct these, and get moving on bringing WordPress into
>     ATAG and WCAG2.0 compliance.
>
>     I'm excited to see this underway!
>
>     Lynne
>
>
>     _______________________________________________
>     wp-accessibility mailing list
>     wp-accessibility at lists.automattic.com
>     <mailto:wp-accessibility at lists.automattic.com>
>     http://lists.automattic.com/mailman/listinfo/wp-accessibility
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> wp-accessibility mailing list
> wp-accessibility at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-accessibility
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-accessibility/attachments/20090808/e0a6ec0b/attachment.htm>