Provide unique link text to assistive technology

[shellchulx]

Description

Currently, the semantics are not mapped to the accessibility API for calcite-link with the role="presentation", which the Calcite team explains as why the aria-label isn't read back to all AT. An enhancement request to add support for a label attribute for calcite-link could help fix this.

cc @catherinehynes

Acceptance Criteria

NVDA will read the aria-label

Relevant Info

No response

Which Component

calcite-link

Example Use Case

No response

Priority impact

p4 - not time sensitive

Esri team

ArcGIS Enterprise

[geospatialem]

@shellchulx Could you provide a use case for the benefit of a label over the current slotted link text for us to consider and prioritize the enhancement?

[catherinehynes]

@geospatialem The ArcGIS Enterprise accessibility evaluation at 10.9.1 included an audit of the portal home app Organization > Licenses page, which has a Manage link for many different types of add-on licenses:

This is where we were hoping to add a label for each link so we could have a more descriptive name for AT.

[geospatialem]

This is where we were hoping to add a label for each link so we could have a more descriptive name for AT.

Thanks for the quick response, @catherinehynes! Out of curiosity could the button component work in this use case? Wondering if perhaps it could provide a similar use case, as it contains href and label attributes.

For instance: https://codepen.io/geospatialem/pen/dyQOyEZ

[geospatialem]

@catherinehynes @shellchulx Would the above recommendation with button fit the use case? If changing the component altogether isn't feasible, could a .sr-only, or similar, span element be added to provide unique context?

[catherinehynes]

@geospatialem I believe the button would work - @shellchulx could you weigh in?

[geospatialem]

@catherinehynes @shellchulx Circling back to the above, was button able to achieve the need?

[geospatialem]

Closing the above with the recommended workflow.