Skip to content

Accessibility problem in new helpers #25642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
afr-ux opened this issue May 29, 2025 · 0 comments
Open
4 tasks done

Accessibility problem in new helpers #25642

afr-ux opened this issue May 29, 2025 · 0 comments

Comments

@afr-ux
Copy link

afr-ux commented May 29, 2025

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

In configuration > helpers > new helper.
I select from the list: combine the status of several sensors.
In the new sensor configuration window, until recently, there was an edit box where you could type some letters and, with down key, the entities with that text were displayed. Pressing enter selected that entity and enabled a new text box to enter an additional entity.
Now a button called "select an entity" appears and is completely inaccessible with screen readers. In the edit box that appears when it is clicked, text can be typed but the entities with that text do not appear. It is not possible to add entities with a screen reader.
Now it is not possible to use this function by blind users using screen readers.
The same will happen in other possible places where this type of controls have been changed.
I tested it in Windows 10 Pro with JAWS and NVDA and chrome, firefows, edge.

Describe the behavior you expected

Read succesfully with screnreaders.

Steps to reproduce the issue

Use screenreader and try add a new helper and try add new entity.
2.
3.
...

What version of Home Assistant Core has the issue?

Last

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue?

All

Which operating system are you using to run this browser?

Windows 10

State of relevant entities

Problem-relevant frontend configuration

Javascript errors shown in your browser console/inspector

Additional information

I suggest check accessibility before production platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant