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

[Accessibility] Python Native repl does not announce executed output #233237

Open
Tracked by #209140
jooyoungseo opened this issue Nov 6, 2024 · 3 comments · May be fixed by #233372
Open
Tracked by #209140

[Accessibility] Python Native repl does not announce executed output #233237

jooyoungseo opened this issue Nov 6, 2024 · 3 comments · May be fixed by #233372
Assignees

Comments

@jooyoungseo
Copy link

CC @meganrogge

When you execute code in Python native repl, the executed output is not announced to screen reader via aria alert.

Reproducible Steps

  1. Enable screen reader

  2. Create Python native repl

  3. In the input, type print("hello")

  4. Hit Enter to execute

Current Behavior

Executed result is not announced.

Expected Behavior

The executed result needs to be announced via aria alert.

@amunger
Copy link
Contributor

amunger commented Nov 7, 2024

@jooyoungseo - My plan was to just auto focus the item that was added, but from there, you would need to open the a11y view to get the output. Should this aria-alert be done instead of that? Or perhaps as an alternate?

related issue: #229182

@jooyoungseo
Copy link
Author

@amunger Moving focus after execution may cause some confusion. We don't move focus for Jupyter Notebooks and Copilot Chat, either. I would rather use aria-live alert to announce the executed output.

@amunger
Copy link
Contributor

amunger commented Nov 7, 2024

Thanks for the feedback, that makes sense.

@amunger amunger linked a pull request Nov 7, 2024 that will close this issue
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.

4 participants