E-mail List Archives
Re: [EXTERNAL] Breadcumb nav same page accessibility
From: glen walker
Date: Dec 13, 2019 8:06AM
- Next message: Patrick H. Lauke: "Re: [EXTERNAL]Duration of Success message"
- Previous message: glen walker: "Re: [External Sender]Treegrid Question"
- Next message in Thread: Jared Smith: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- Previous message in Thread: allyssa jessicon: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- View all messages in this Thread
No to first question, Yes to second question.
No:
WCAG does not address breadcrumbs specifically. You can use the authoring
practice as a best practice (
https://www.w3.org/TR/wai-aria-practices/#breadcrumb) and it states:
- The *link *to the current page has aria-current
<https://www.w3.org/TR/wai-aria-1.1/#aria-current> set to page. If the
element representing the current page is not a link, aria-current is
optional.
But the authoring practice is just a guideline and not a requirement.
Yes:
If every element in the breadcrumb list were a link, including the current
page, then I would mark it a failure of 4.1.2 if the current page link did
not indicate it were the current page because its state ("value" of "name,
role value") were not announced.
On Fri, Dec 13, 2019 at 1:13 AM Ramshif Richu < <EMAIL REMOVED> > wrote:
> is it a WCAG violation to not have the current page as a plain text?
> what if the current page in the breadcrumb nav is a link which has no
> current role added to it?
>
>
- Next message: Patrick H. Lauke: "Re: [EXTERNAL]Duration of Success message"
- Previous message: glen walker: "Re: [External Sender]Treegrid Question"
- Next message in Thread: Jared Smith: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- Previous message in Thread: allyssa jessicon: "Re: [EXTERNAL] Breadcumb nav same page accessibility"
- View all messages in this Thread