Skip to content

compiler: Add missing accessible-enabled property and don't activate accessible-action-default when disabled - #13436

Open
Montel wants to merge 1 commit into
slint-ui:masterfrom
Montel:add_accessibility_enabled
Open

Montel wants to merge 1 commit into
slint-ui:masterfrom
Montel:add_accessibility_enabled

Conversation

@Montel

@Montel Montel commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

No description provided.

accessible-enabled: root.enabled;
accessible-label: root.text;
accessible-action-default => { touch-area.clicked(); }
accessible-action-default => { if (root.enabled) { touch-area.clicked(); } }

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @DataTriny Do you know if this is needed or if it's fair to assume that accessible-action-default be invoked on elements where accessible-enabled is false?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tronical AFAIK platform accessibility stacks don't really care, AccessKit (inconsistently for now) enforce this check when the API wants a confirmation, but in any case we take decision based on the latest tree update we received from Slint, which may not reflect the current state. Therefore it's safer to do this check at the toolkit level.

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

Successfully merging this pull request may close these issues.

3 participants