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

Need: ~"User Agents MAY ignore user-triggered changes to live regions, such as typing in text fields." #72

Closed
cookiecrook opened this issue Jul 15, 2015 · 4 comments · Fixed by #1820
Assignees
Milestone

Comments

@cookiecrook
Copy link
Contributor

We've gotten a bug report against WebKit that VO repeats every character of a text field on Facebook.com. After investigating, the text field is placed inside an ARIA live region.

The spec ~"every change that affects the accessible label" should trigger a live region alert, but I think there should be an exception for user triggered changed like typing.

This is probably an single-sentence "User Agents MAY" change.

@jnurthen jnurthen added this to the ARIA 1.3 milestone Nov 29, 2018
@jnurthen jnurthen added this to Needs triage in Live Region updates Mar 18, 2020
@jnurthen jnurthen moved this from Needs triage to High priority in Live Region updates May 21, 2020
@jnurthen jnurthen modified the milestones: ARIA 1.3, ARIA 1.4 Mar 4, 2021
@jnurthen
Copy link
Member

jnurthen commented Mar 4, 2021

moving to 1.4 and grouping all live region updates

@adampage adampage self-assigned this Sep 27, 2022
@adampage
Copy link
Member

Hi @cookiecrook , I’m 7 years late to this party 😅 but am wondering if you might be able to point me to the WebKit bug report that kicked off this issue so I can get the full background and see any follow-up activity?

In the meantime, I’ll review all aria-live-related statements in the 1.3 draft to see where we could integrate this change.

@cookiecrook
Copy link
Contributor Author

wondering if you might be able to point me to the WebKit bug report that kicked off this issue so I can get the full background and see any follow-up activity?

Oh gosh! I feel like the search may be an exercise in futility. I wasn’t the originator, and I didn’t store the title or tracking number in this issue. I looked briefly by keywords, but didn’t find anything obvious, and don’t feel the need to dig further.

I expect we fixed that in WebKit at the time. If it’s obviously a bug implementers don’t usually wait on “permission” from the spec.

@cookiecrook
Copy link
Contributor Author

For future reference the bug number was rdar://18175382 but that won’t be publicly visible. It was only ever in the internal tracker, and ultimately resulted in a change to VO, not WebKit.

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

Successfully merging a pull request may close this issue.

3 participants