I agree with what everyone is saying, altough it is not always feasible to make the link text descriptive and sometimes makes it look "clunky" when you've added the "read more" link straight after the title, having to write "read more about..." and repeat the title again.
All that aside, it is a requirement, so it must be followed. I did find Joe Clark's comments at @media interesting though. If you go to his speaker's notes and search for "Headings and links read out of context", it's worth a read and a valid point. http://joeclark.org/appearances/atmedia2007/ Anyway, until it is no longer a requirement, I'll be making my links descriptive. On 21/10/2007, russ - maxdesign <[EMAIL PROTECTED]> wrote: > > You have given a good reason, still, I think that criteria should > > have room for flexibility (just as George has given the same reason) > > because, link texts in the articles aren't the same and the excerpt > > of the article should have given enough information for a user > > (including screen reader user) whether he wants to continue reading > > the full article. If my argument is prudent, I think validator should > > have something like > > Tee, > > I apologise if I misread your original post. > > You mentioned a "...'continue reading' link..." and then mentioned "...more > than one title attribute with 'continue reading'...". > > I assumed you were referring to the content of the link being the same for > each link - like this: > <a href="" title="continue reading">continue reading</a> > <a href="" title="continue reading">continue reading</a> > > However, you may have been referring to the content of the title attribute > only - like this: > <a href="" title="continue reading">Unique content</a> > <a href="" title="continue reading">Some other content</a> > > If this is the case, then I agree with Gunlaug - that this is much less of > an issues. The title is designed to provide additional information, and is > rarely used by assistive devices. > > As you say, Steve Faulkner has raised issues with the title attribute - even > though his original article is not online, he gives a brief summary here: > http://webstandardsgroup.org/features/steve-faulkner.cfm#seven > > "due to its present support in browsers, it can actually add to making > content less accessible." > > Guideline 13.1 states that "Link text should be meaningful enough to make > sense when read out of context." It goes on to say "In addition... content > developers may further clarify the target of a link with an informative link > title". To me, this implies that this title is not essential. It could also > be interpreted that as long as your content is meaningful and unique, you > should pass this checkpoint. Someone with a deeper understanding of this > checkpoint may be able to clarify this! > > Again, apologies for misreading and for any confusion. > Thanks > Russ > > > > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
