Breadcrumb Implementation Discrepancies

[LYacheva]

The active item of the Breadcrumb component is implemented with the style of disabled item across jQuery and Angular demos.

The correct way to display the active item is as implemented in React:

[silviyaboteva]

@nenchef , @tapopov , @Raisolution,
This seems to come from the component logic. Can you please remove the disabled attribute from the last element of the breadcrumb?

When ready, please close this issue :)

[Raisolution]

It was intentionally implemented this way to indicate that the user cannot interact with this item, because it is already active e.g. represents the current page.

I agree that the disabled styles might not be the best ones. Maybe we need readonly styles to differentiate it from the rest of the items, which the user could navigate to.

[silviyaboteva]

@telerik/kendo-a11y may I ask you to research this topic and once we came up with a solution, the affected suites will have to change the component implementation?

[Raisolution]

I will log the item for design revision in the upcoming weeks after the release. Best case scenario would be to (probably) not force the decision, but let the user decide if the last item should be active, disabled or readonly.

[veselints]

@silviyaboteva
From an accessibility point of view, there is no difference whether the active link has k-disabled class or not. There is no other requirement apart from having the aria-current attribute set on the end link.

Apart from the discussed here, I have reviewed the rendering of the Breadcrumb component in Angular, Blazor, jQuery, and React. What is missing in the React implementation and must be added is the role="link" on the link elements.