Open
Description
Check existing issues
- I have checked for existing issues to avoid duplicates and reviewed the Accessibility page for guidance.
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
- Activate NVDA or JAWS
- Open the sample
- Search for a place like
"San Diego"
- Arrow down into the first
autocomplete-item
result - Observe no context is provided for the item's
heading
orlabel
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
Labels
New issues that need assignment.Issues logged by Calcite developers.Issues related to Accessibility fixes or improvements.Bug reports for broken functionality. Issues should include a reproduction of the bug.A few days of work, definitely requires updates to tests.User set priority impact status of p1 - need for current milestoneIssue should be addressed in the current milestone, impacts component or core functionality