Skip to content

Conversation

@lukewarlow
Copy link
Contributor

@lukewarlow lukewarlow commented Nov 13, 2025

Fixes #640

@lukewarlow lukewarlow force-pushed the aria-properties-windows branch from df26e01 to b470d44 Compare November 13, 2025 21:58
@lukewarlow lukewarlow force-pushed the aria-properties-windows branch from b470d44 to 4431bff Compare November 13, 2025 21:58
@lukewarlow lukewarlow changed the title feature: Expose most state aria_properties to UIA feat: Expose most state aria properties to UIA Nov 13, 2025
@DataTriny
Copy link
Member

I think Microsoft recommends to only include here properties or states that don't have a clear mapping to UIA. Is there added value in setting as many properties as possible?

@lukewarlow
Copy link
Contributor Author

This is largely based on https://learn.microsoft.com/en-us/windows/win32/winauto/uiauto-ariaspecification#w3c-aria-states-and-properties-mapped-to-microsoft-active-accessibility-and-ui-automation

But also https://w3c.github.io/core-aam/#mapping_nodirect which says UAs are allowed to set them even if they do map already.

Chromium maps many if not all of these properties and states too.

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.

UIA_AriaPropertiesPropertyId property should be set for windows adaptor

2 participants