Skip to content

[Autocomplete Item] Context is not provided to assistive technology when in focus #12505

Open
@geospatialem

Description

@geospatialem

Check existing issues

Summary

When the autocomplete-item component is in focus it does not provide context to assistive technologies.

Discovered during the verification of adding an aria-label to the parent autocomplete when results are displayed when interacting with the component: #12433 (comment)

Actual Behavior

When an autocomplete-item is in focus the component does not provide context to assistive technologies.

Expected Behavior

When an autocomplete-item is in focus the heading, or if provided label is communicated to assistive technologies.

For instance:

<!-- Heading communicated when in focus -->
...
<calcite-autocomplete-item value="elderberry" heading="Elderberry"></calcite-autocomplete-item>
...

<!-- Label communicated when in focus -->
...
<calcite-autocomplete-item value="a-value" heading="Displayed value" label="A more descriptive label"></calcite-autocomplete-item>
...

Reproduction Sample

https://codepen.io/isaacbraun/pen/pvjvbvX

Reproduction Steps

  1. Activate NVDA or JAWS
  2. Open the sample
  3. Search for a place like "San Diego"
  4. Arrow down into the first autocomplete-item result
  5. Observe no context is provided for the item's heading or label

Reproduction Version

3.3.0-next.33

Working W3C Example/Tutorial

https://www.w3.org/WAI/WCAG22/Understanding/on-input.html

Relevant Info

Violates WCAG SC 3.2.2: On Input (Level A)

Blocks: #12515

Regression?

No response

Priority impact

impact - p1 - need for current milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

Calcite (dev)

Metadata

Metadata

Assignees

No one assigned

    Labels

    0 - newNew issues that need assignment.Calcite (dev)Issues logged by Calcite developers.a11yIssues related to Accessibility fixes or improvements.bugBug reports for broken functionality. Issues should include a reproduction of the bug.estimate - 5A few days of work, definitely requires updates to tests.impact - p1 - need for current milestoneUser set priority impact status of p1 - need for current milestonep - highIssue should be addressed in the current milestone, impacts component or core functionality

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions