Skip to content
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

macOS Home Assistant Companion App: No Accessibility Features #3327

Open
misterbond007 opened this issue Jan 12, 2025 · 10 comments
Open

macOS Home Assistant Companion App: No Accessibility Features #3327

misterbond007 opened this issue Jan 12, 2025 · 10 comments

Comments

@misterbond007
Copy link

Device model, version and app version

Model Name: Mac mini 2024 Apple M4
macOS Version: macOS Sequoia 15.2
App Version: Home Assistant Companion App version 2024.12.2 (2024.1058)
Safari Version: Version 18.2 (20620.1.16.11.8)

Home Assistant Core Version

2025.1.2

Describe the bug
Home Assistant does not correctly report the focused UI element using Apple's Accessibility features. When a text field in Home Assistance has keyboard focus, the Accessibility API does not report a UI element with the role “text field” or “text area” as having focus, but rather a generic group. This prevents Accessibility-enabled tools from being able to detect when a user might need assistance typing into a text field.

Specifically, the issue is that, when a text field is focused in Home Assistant, the "AXFocusedUIElement" attribute of the system-wide UI element does not indicate a UI element with the role “AXTextField” or “AXTextArea” is focused.

To Reproduce
Install macOS 15.2
Install Home Assistant Companion App version 2024.12.2 (2024.1058)
On a touch screen set the focus into a text field

Expected behavior
When a text field in Home Assistance Companion has keyboard focus, the Accessibility API should report a UI element with the role “text field” or “text area” as having focus.

@bgoncal
Copy link
Member

bgoncal commented Jan 13, 2025

Thanks for reporting the issue, currently the App only displays a webview with Home Assistant frontend inside, so I'd recommend reporting this in the frontend repo since the App is not in control on what displays in the webview.

@bgoncal bgoncal closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2025
@bgoncal bgoncal self-assigned this Jan 13, 2025
@misterbond007
Copy link
Author

I have reported it in the frontend repo, but they said, I should post it here :-)

@bgoncal
Copy link
Member

bgoncal commented Jan 13, 2025

Could you link me to the frontend issue?

@misterbond007
Copy link
Author

@bgoncal
Copy link
Member

bgoncal commented Jan 13, 2025

Thanks, I wrote a comment there.

@misterbond007
Copy link
Author

misterbond007 commented Jan 13, 2025

Don't you think the issue is because of the webview, that the macOS accesibilty feature only sees a "group", but not a text field? I'm pretty sure, it's an issue with the macOS app, not the frontend, because in the Firefox Browser I don't have any problems.

@bgoncal
Copy link
Member

bgoncal commented Jan 13, 2025

You need to compare to Safari to evaluate that, but in the App can't you focus on anything inside the webview? a button for example.

@misterbond007
Copy link
Author

misterbond007 commented Jan 13, 2025

I have tested it now in Safari too, without any problems: the accesibilty feature works (the text field is recognized as a text field).

I can focus on buttons and on everything in the macOS App. But as described, the accessibility feature doesn't recognize the items correctly.

@bgoncal bgoncal reopened this Jan 13, 2025
@bgoncal
Copy link
Member

bgoncal commented Jan 13, 2025

Ok, then this will need further investigation since it looks like a bug on the webview (WKWebView) itself, the behavior should be the same as Safari.
Please let me know all differences you have noticed between safari and the app and when I have time I'll investigate this.

@misterbond007
Copy link
Author

misterbond007 commented Jan 13, 2025

Ok, thank you.
As I know, the accesibility feature sees everything as a "Group", but not as the correct specific item (e.g. text field).

The issue is that, when a text field is focused in Home Assistant, the "AXFocusedUIElement" attribute of the system-wide UI element does not indicate a UI element with the role “AXTextField” or “AXTextArea” is focused.

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

No branches or pull requests

2 participants