- From: Jeana Clark <jclark@veritashealth.com>
- Date: Wed, 5 Feb 2020 07:20:58 -0600
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: W3C WAI ig <w3c-wai-ig@w3.org>
- Message-Id: <32FD1684-6BA2-40D9-B080-C8CDCCA4C40B@veritashealth.com>
It used to also be that Google used to leverage next/prev for search results: https://searchengineland.com/google-no-longer-supports-relnext-prev-314319 <https://searchengineland.com/google-no-longer-supports-relnext-prev-314319> It no longer does this. Jeana Clark Creative Director Tel: 847.607.8577 jclark@veritashealth.com <https://www.veritashealth.com/> <https://www.veritashealth.com/> Spine-health.com <https://www.spine-health.com/> | Arthritis-health.com <https://www.arthritis-health.com/> Sports-health.com <https://www.sports-health.com/> | Pain-health.com <https://www.pain-health.com/> *** CONFIDENTIALITY NOTICE*** This message and any included attachments are from Veritas Health, LLC (owner and operator of Spine-health.com, Arthritis-health.com, Sports-health.com and Pain-health.com) and are intended for the addressee only. The contents in this message may contain confidential information belonging to the sender that is legally privileged. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or contact the Veritas Health, LLC at admin@veritashealth.com. Veritas Health reserves the right to view all communications into and out of the company and senders shall have no expectation of privacy. > On Feb 5, 2020, at 2:55 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > > To my knowledge, no browser/UA/AT take advantage of the rel="..." attribute or expose it to the user in any meaningful way. So even technique H59 is rather dubious to me. There used to be browsers (probably old versions of Opera) and extensions (I have vague memories of something for Firefox) that surfaced rel="..." for a page, but this seems more like a historical quirk that never quite caught on. > > In short, unless you somehow use the rel="..." attribute in some way yourself (e.g. if you have extra JS that somehow exposes relationship information like that to the user), I would not bother with those attributes at all. > > P > > > On 31/01/2020 15:19, Bristow, Alan wrote: >> Hello, >> If you have a minute to help me with this I would be grateful and smile. >> I am investigating the accessibility benefit, or lack thereof, of the use of 'rel' 'next' and 'rel' 'prev' in <body>, with <a> tags, as opposed to in <head> with <link> tags. >> E.g.: >> ... >> </head> >> <body> >> <a href=”dogs.html rel=”prev”>Dogs</a> >> <a href=”cats.html rel=”next”>Cats</a> >> </body> >> While H59 (https://www.w3.org/TR/WCAG20-TECHS/H59.html) demonstrates the accessibility benefit from using <link> with 'rel' in the <head>, I cannot seem to find any measure of the benefit of implementing these 'rel' values in the <body> with <a>s. >> Does anyone know if it is generally accepted that as far as accessibility goes there is a comparable benefit from these two approaches, or no benefit with the BODY+A when compared to HEAD+LINK, etc? >> Thanks, very much, for any comments. >> Regards, >> Alan >> Alan Bristow >> Elections Canada >> alan.bristow@elections.ca >> [Logo du 100e anniversaire d'Élections Canada / Elections Canada's 100th anniversary logo] <https://www.elections.ca> > > > -- > Patrick H. Lauke > > https://www.splintered.co.uk/ | https://github.com/patrickhlauke > https://flickr.com/photos/redux/ | https://www.deviantart.com/redux > twitter: @patrick_h_lauke | skype: patrick_h_lauke >
Received on Wednesday, 5 February 2020 13:21:12 UTC