- From: Tom Shaw <tom-shaw@hotmail.com>
- Date: Wed, 15 May 2024 10:44:19 +0000
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <DB9P251MB00625A813D1B0B002906DB8999EC2@DB9P251MB0062.EURP251.PROD.OUTLOOK.COM>
Thank you, Léonie. Great response and exactly what I was looking for. ________________________________ From: Léonie Watson <lwatson@tetralogical.com> Sent: 15 May 2024 11:35 To: Tom Shaw <tom-shaw@hotmail.com>; w3c-wai-ig@w3.org <w3c-wai-ig@w3.org> Subject: Re: Breadcrumb trail One advantage to using a link is that it keeps it in the Tab sequence. So someone using the Tab key to navigate through the content will land on the link and (if they use a screen reader) will be informed that the link represents the current page. If it isn't a link then it's more likely that someone will bypass it and perhaps not realise they've missed out on potentially useful information. On 15/05/2024 11:24, Tom Shaw wrote: Hi all. I see that w3 and WCAG give examples of breadcrumb trails whereby they are all links...even the last one..which typically I am used to seeing as plain text...with aria-current being used on the <li> element to convey the cuurrent page....but lots of examples use the page they are on as a link, too. Personally I think it doesn't matter whether it's a link or plain text..although I am slightly swaying towards it's OK being a link for users that may want to refresh the page I guess. I would just like your opinion if possible - please! Thank you. -- Léonie Watson (she/her) Director https://tetralogical.com/
Received on Wednesday, 15 May 2024 10:44:25 UTC