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 · 0 comments
Open

macOS Home Assistant Companion App: No Accessibility Features #3327

misterbond007 opened this issue Jan 12, 2025 · 0 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.

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

1 participant