WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXTERNAL] Breadcumb nav same page accessibility

for

From: glen walker
Date: Dec 13, 2019 6:22PM

4.1.2 says the state or value of the element must be presented. If the
link is for the current page, I consider that a state. I'm fine if others
don't think that.

If there were a visual indicator that the current page in the breadcrumb
list looks different than all the other elements in the breadcrumb list,
that would also indicate a failure (and I'd use 4.1.2). You have a visual
presentation of a state that looks different than the state of all the
other elements. You don't necessarily have to use aria-current to indicate
the state, but that's one implementation.

The WebAIM site does something similar. In the breadcrumb list, there's a
hidden "you are here" span. I kind of expected that text to be associated
with the last element in the breadcrumb (as an alternative to using
aria-current) but it's actually the first piece of text in the breadcrumb
list. Not sure if that was intentional.


On Fri, Dec 13, 2019 at 4:04 PM Jared Smith < <EMAIL REMOVED> > wrote:

> > 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.
>
> While I wouldn't have a link in the breadcrumbs to the existing page,
> I disagree that if such a link existed that it would be a WCAG failure
> for it to not have aria-current. I don't believe this is inline with
> what 4.1.2 requires.
>
> Thanks,
>
> Jared
> > > > >