frontend
frontend copied to clipboard
Setting location is not accessible
Checklist
- [x] I have updated to the latest available Home Assistant version.
- [x] I have cleared the cache of my browser.
- [x] I have tried a different browser to see if it is related to my browser.
The problem
The current method for setting the location via the UI requires visual interaction with a pointer to set latitude and longitude. This is not accessible for screen reader users or other assistive technology requiring keyboard control.
Expected behavior
There needs to be a keyboard only method for setting location either via coordinates or physical address.
Steps to reproduce
N/A
Environment
- Home Assistant release with the issue: Issue started with intro of map method for location and persists in latest release.
- Browser and browser version: N/A
- Operating system: N/A
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, this is certainly still an issue.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, still an issue. And could probably be easily solved simply by adding input fields to show/edit the longitude and latitude coordinates.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yep, still an issue.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Please re-open. This is still an issue.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yes, still an issue.
@matthiasdebaat Any ideas how to best handle this?
We could use the same pattern as we have in the onboarding? Where there's a button to detect your location.
Sorry for the dutch language

I just thought about it some more: What if the home location cannot reliably be detected automatically? Not sure how often that happens though.
For manually created zones, we have this UI where you have input fields:

It's good to offer this option, this helps a user to specify his exact location. I think it's a bit hard to use this with screen reader or other assistive technology. @steverep do you have experience with this?
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Can we stop the bot from closing this?
By responding before it closes :)
It's Home Assistant not Home Ruler. Playing by the bot's rules makes for a boring movie plot.
Please re-open. This is certainly still an issue.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Yup, still a problem.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
It is still an issue
This looks like it has been an issue for a while. Is anybody looking into it?
@joshms123 there are quite a few accessibility issues, some hanging around for a while like this one. I've been trying to improve accessibility one issue at a time through various contributions, but I'm not part of the HA team so my time is limited. At least this one has a workaround to use Yaml.
Specific to this issue,inputting coordinates is a start and is possible in the latest version, but I wouldn't regard it as equal access until I can search for an address via keyboard.
@bramkragten @zsarnett can fixing this finally be made a priority? The ability to add/edit zone locations by inputting latitude and longitude now exists for other zones, but cannot be done for the home zone. That seems pretty silly.
Since the focus of this year is supposed to be streamlining experiences, it would be nice to simply be able to quickly enter physical addresses rather than fumbling through a map. This is one of the first things new HA users need to do, so it should be as easy and accessible as possible.
Am I missing a technical hurdle?
I agree, this "should" be fixed as new HA users (and old ones like me) really like to control this - preferably without yaml-code. The radius parameter is really something very useful, and especialy for your primary location as home... 😁
I hope this is not too hard as all other zones got this?
@johanhallberg agreed. It's astounding to me that this isn't an option, and even more incomprehensible that it was in the past and then somehow the decision was made to deliberately cripple and remove functionality for apparently no reason at all. It's the sort of thing I'd expect from Apple perhaps before they sell you a new device with the crippled feature re-added at extra cost.
The default size of the "home" zone is positively enormous too. Unless you live in the midwest on some acreage that's going to be several houses or an entire city block.
It doesn't take much to solve this problem. All that's needed is the ability to enter the latitude and longitude. This can be done for other locations, but there has never been such an option for home location. The problem is very old. Maybe it's time to finally solve it?
Wasn't there a new location picker that made this accessible?