Skip to content

[Combo] readonly attribute can create confusion for screen reader users #15842

Open
@jamesuhl

Description

@jamesuhl

Description

When navigating to the combobox, the screen reader announces "readonly", implying the combobox itself is read-only, possibly causing confusion

Solutions

The combobox is using an element with a readonly attribute to display the current selection(s) of the combobox. The source of confusion comes when the screen reader announces the comboxbox as readonly -- but is editable.
Two possible solutions here may be to
A. use a <div role="combobox"> element instead of an <input>. Or
B. give the <input> a dynamic aria-label of either “no options selected” (when empty) or “selected options” when populated with values.
Then
The component code needs to use a <button> element to actually reveal the drop-down. Currently, the code is using an <input> to open and close the dropdown, which is fine for people with functioning eyes, but for the blind, using an <input> to open/close a dropdown is not intuitive.

Additional context

Image

Image
Make these elements actual <button>s

Metadata

Metadata

Assignees

Labels

🧰 feature-request♿ a11yWhen the issue or PR is related to accessibility✅ status: resolvedApplies to issues that have pending PRs resolving them, or PRs that have already merged.aria-supportcombo

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @kdinev@ChronosSF@Lipata@jamesuhl@kacheshmarova

      Issue actions

        [Combo] readonly attribute can create confusion for screen reader users · Issue #15842 · IgniteUI/igniteui-angular