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

aria-readonly: Consider explicitly calling out UIA mapping for controls that don't follow the ValuePattern #127

Closed
sivakusayan opened this issue Jul 3, 2022 · 1 comment · Fixed by #203
Assignees
Milestone

Comments

@sivakusayan
Copy link
Contributor

As discussed in w3c/aria#1309 (comment), UIA doesn't have a mapping for readonly checkboxes, even though aria-readonly is allowed on checkboxes. Readonly semantics end up being exposed through the AriaProperties property instead. Should the AAM be updated to call this out in the aria-readonly table? It seems like that is done for cases like aria-sort.

@spectranaut spectranaut self-assigned this Jul 7, 2022
@spectranaut spectranaut added this to the 1.3 milestone Jul 7, 2022
@spectranaut
Copy link
Contributor

spectranaut commented Aug 25, 2023

Sorry for only replying to this one as well, a year later! This is also a reasonable and useful change. Let me know if you would like to open a PR with the change, otherwise I'll put it on my to dos.

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 a pull request may close this issue.

2 participants