NVDA announces "Authorize Visual Studio Code" button as unavailable on the OAuth authorization page

[accesswatch]

Discussion Type

Bug

Feature/Topic Area

Apps

Body

On the "Authorize Visual Studio Code" page that GitHub opens when you sign in from VS Code, NVDA announces the "Authorize Visual Studio Code" button as unavailable (disabled).

This was reported by a learner in our workshop, GIT Going with GitHub, in Community-Access/git-going-with-github#70: Community-Access/git-going-with-github#70. A second learner commented that they had the same problem.

Environment, from the report: NVDA on Windows 10. The same result in Firefox, Microsoft Edge and Google Chrome.

Steps to reproduce

1. In VS Code, sign in to GitHub from the Accounts menu.
2. In the browser page that opens, choose an account.
3. The authorization page appears, listing the permissions with a "Show more info" button for each, then "Cancel" and "Authorize Visual Studio Code" buttons.
4. Move to the "Authorize Visual Studio Code" button with NVDA.

Expected: the button is announced as an available button and can be pressed.

Actual: NVDA announces the button as unavailable, so the learner could not authorize VS Code, and so could not use GitHub Copilot Chat or GitHub Pull Requests in VS Code.

What got the reporter through: the next day, they removed the GitHub Copilot extension, signed in again, copied the link from the authentication page and opened it in Microsoft Edge, where the button was available. They did not know why it worked that time.

Workarounds we give learners: wait for the page to finish loading and press Enter on the button anyway; reload the page; open the same link in another browser; or sign in with gh auth login instead.

Could the team check whether the button is exposed as disabled to assistive technology while it is still being enabled, and whether that state is updated once it becomes active?

[github-actions[bot]]

Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided.

This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers.