[Obs Synthetics > Monitor Detail views][COGNITION] Breadcrumb links should be aligned with information architecture: 0008

[1Copenut]

Point of contact

@petrklapka

Description

See https://github.com/elastic/observability-accessibility/issues/13 for full description of the issue and code reference for a suggested fix.

Environment

• MacOS
• Safari + VO
  • Monitor detail
  • Test run detail
  • Performance breakdown

Screenshots or Trace Logs

Monitor detail

---

Test run detail

---

Performance breakdown

WCAG or Vendor Guidance (optional)

• Understanding SC 1.3.1: Info and Relationships (Level A)
• Understanding SC 2.4.4: Link Purpose (In Context) (Level A)

[jasonrhodes]

Does "feels extra" mean we are required to remove it? Or is this just a design/UX suggestion and not a WCAG requirement?

[jasonrhodes]

Also, I see a "blocked" tag on this issue in the a11y board. Can someone from that team help us understand if this is still blocked? cc @petrklapka

[petrklapka]

@alexwizp and @dave-gus - I'm a little skeptical about this issue. "Feels Extra" isn't an accessibility violation. Yes, it's duplicate functionality, and yes it's a "non standard" bit of navigation when compared to other Kibana apps and pages, but I don't understand how this is in any way preventing a user with A11Y needs from getting their work done. Can we revisit the ruling here?

[alexwizp]

@petrklapka I agree with both of you. I'm not sure it's a significant accessibility issue, but I also think we don't need to overload the UI with extra controls.

[jasonrhodes]

Thanks, both. I was wondering if those "Feels extra" comments were the main thrust of this issue or if it was trying to say that the breadcrumb links themselves in these examples are somehow improperly aligned with the IA, and the comments about the back links were just added suggestions... with the description referencing another issue, it's hard for me to make sense of what the actual request is here, re: WCAG.