<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The read more links can be easily adjusted by doing something like:<br>
the_content('Read the rest of
<em>'.the_title('','',false).'</em> &raquo;');<br>
<br>
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
(<a class="moz-txt-link-freetext" href="http://core.trac.wordpress.org/ticket/10569">http://core.trac.wordpress.org/ticket/10569</a>). Please give it a look,
test it, and comment on trac.<br>
<br>
Tynan Colin Beatty wrote:
<blockquote
cite="mid:4f9525dc0908062142n33c3a458j5772672faa08ea96@mail.gmail.com"
type="cite">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:<br>
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: <a moz-do-not-send="true"
href="http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C7"
target="_blank">http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/C7</a><br>
I'm uncertain as to how this would affect the 'reply' situation, should
WordPress Trac ticket #10550 ( <a moz-do-not-send="true"
href="http://core.trac.wordpress.org/ticket/10550">http://core.trac.wordpress.org/ticket/10550</a>
) 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.<br>
'Read more' can be supplemented by titles. Any other repetetive /
unclear anchors should also be similarly supplemented to comply with
this guideline. Thoughts?<br>
<br>
<div class="gmail_quote">On Thu, Aug 6, 2009 at 9:38 PM, Lynne Pope <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:lynne.pope@gmail.com" target="_blank">lynne.pope@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">First
off, I wish to thank "the powers that be" for responding to my request
for this mailing list.<br>
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.<br>
<br>
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.<br>
<br>
I'm excited to see this underway!<br>
<font color="#888888"><br>
Lynne<br>
<br>
</font><br>
_______________________________________________<br>
wp-accessibility mailing list<br>
<a moz-do-not-send="true"
href="mailto:wp-accessibility@lists.automattic.com" target="_blank">wp-accessibility@lists.automattic.com</a><br>
<a moz-do-not-send="true"
href="http://lists.automattic.com/mailman/listinfo/wp-accessibility"
target="_blank">http://lists.automattic.com/mailman/listinfo/wp-accessibility</a><br>
<br>
</blockquote>
</div>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
wp-accessibility mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wp-accessibility@lists.automattic.com">wp-accessibility@lists.automattic.com</a>
<a class="moz-txt-link-freetext" href="http://lists.automattic.com/mailman/listinfo/wp-accessibility">http://lists.automattic.com/mailman/listinfo/wp-accessibility</a>
</pre>
</blockquote>
<br>
</body>
</html>