There is one URL you are going to: href='display_part.php?PID=218' But there are multiple descriptions (titles) of that URL. In one case, you call it title='M.G. Judd Part Number' but in another case you call it title='Original Equipment Manufacturers Part Number'.
It's the same URL, but you're potentially confusing the reader by giving it two different names. I think that's what they're getting at. Make scents? :) Bob On Tue, Jun 22, 2010 at 7:52 PM, Phillip Whiteside <[email protected]> wrote: > > Hi, > They're taking the urine now. > > <a class = 'N' title='M.G. Judd Part Number' > href='display_part.php?PID=218'> > 68 OL/OP007/1 > 68 </a> > 68 </td> > 69 <td> > 69 E836 [WCAG v1 13.1 (AA)] Use different values for 'title' attributes > with links that use the same link text: > <a class = 'N' title='Original Equipment Manufacturers > Part Number' href='display_part.php?PID=218'> > 69 - > 69 </a> > > Ermm. , and they have two different 'title' tags? the link text is different > per item WTF? > > Confused @ phill > Regards, > Phill. > On Tue, Jun 22, 2010 at 11:33 PM, Bob Trevithick <[email protected]> > wrote: >> >> Hi, >> >> All I see so far is the issue with using the same text to link to >> different places. Try running tv on: >> >> http://mgjuddltd.co.uk/search.php?LookFor=chain&MyImpSize=NULL&MyMetSize=NULL >> >> Is there a page in particular that we should look at? I just did that >> search at random. >> >> Best, >> Bob >> >> On Tue, Jun 22, 2010 at 6:23 PM, Phillip Whiteside >> <[email protected]> wrote: >> > Hi Kenny, Alex & Bob, >> > firstly, thank you for helping me on this one. I have re-written the site >> > in >> > terms of headers etc. along with changes to table descriptions / column >> > descriptions. I have made so many changes that I ask if you would have a >> > good check on the site and check that it is usable, in the "find parts" >> > think of 'oil', 'spanner', 'filter' etc. >> > I'm up to http://www.accessifyforum.com/viewtopic.php?t=16289 ::sigh:: at >> > negative comments :-( >> > Hi Mailing list, >> > I'm dipping my toe back into the mailing list, after the last time went >> > bad. >> > If any of you have chance, please have a look. >> > I'd also appreciate any views on whether I should code to WCAG version 1 or >> > version 2 ? >> > Has any one has worked out the answer to 'until' from >> > the http://www.w3.org/TR/WAI-WEBCONTENT/#tech-divide-links where the word >> > 'until' has its own entry as I use a programming routine that seems to work >> > fine with readers, yet am told "until" the readers can handle them, i am >> > not >> > allowed to? >> > I know that there is still a lot of for me to learn on the difference >> > between a robot site saying it is okay and someone with using a screen >> > reader, or any other accessibility access (Do shout now, while I am >> > learning), I ask this time that only those who will give >> > constructive criticism reply. I do need people who will do the manual >> > testing against what the robots reply. >> > Regards, >> > Phill. >> > >> > >> > >> > >> > > -- Ubuntu-accessibility mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
