I am blind and use a screen reader. The current Home Assistant UI is not accessible to people using screen reading technology.
Please make the UI compliant with Web Content Accessibility Guidelines (WCAG) 2.0 specs.
As a start, I would recommend labeling the buttons on the UI. All of them are unlabeled at this time.
I have been able to figure out what most of them do, but I am an advanced screen reader user and the process was tedious at best.
I must admit that i have never tested this with a screenreader. I will put this on my to do list to address.
Do you have a screen reader that you recommend to test with?
Here is a quick video on accessibility in Polymer. https://youtu.be/Lktz1KXbTOU
Hi,
Thanks so much for looking into this!
I primarily use Windows and IOS devices. On Windows, the screen reader I use is called NVDA:
The other one I use is JAWS for Windows, whci his not a free product:
http://www.freedomscientific.com
If you have never interacted with a screen reader before, check this article:
http://webaim.org/articles/nvda/
I’m a very experienced screen reader user. Feel free to ask any questions you might have.
From: Paulus Schoutsen [mailto:[email protected]]
Sent: May 1, 2017 11:49 PM
To: home-assistant/home-assistant-polymer home-assistant-polymer@noreply.github.com
Cc: jfayre jfayre@gmail.com; Author author@noreply.github.com
Subject: Re: [home-assistant/home-assistant-polymer] UI is not accessible to screen reading software (#271)
Do you have a screen reader that you recommend to test with?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant-polymer/issues/271#issuecomment-298490935 , or mute the thread https://github.com/notifications/unsubscribe-auth/AC0Sjk97NLSnYxlMbnogDzbRB1Oic9Bpks5r1qeugaJpZM4NNWi9 . https://github.com/notifications/beacon/AC0SjqowHhCyKG9JI20snxwO3JuHUmWHks5r1qeugaJpZM4NNWi9.gif
Hello,
Do we have any update on this? Last night, I installed hass.io and am still seeing the same accessibility issues.
Sorry, it's still on my to do list 😞
This issue was moved by zsarnett to home-assistant/ui-schema#202.