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

In Graphing mode, the keypad cannot be reached via the Tab key #948

Closed
joshkoon opened this issue Jan 17, 2020 · 3 comments
Closed

In Graphing mode, the keypad cannot be reached via the Tab key #948

joshkoon opened this issue Jan 17, 2020 · 3 comments
Labels
Area: Accessibility Issues with keyboard interactions, screen readers, contrast, font size, and other accessibilty areas by design This issue or pull request already exists

Comments

@joshkoon
Copy link
Member

Describe the bug
In Graphing mode, users cannot use the Tab key to navigate to the keypad.

Steps To Reproduce

  1. Go to Graphing mode
  2. Switch to Equation mode if the window is too small to show all controls.
  3. Use the Tab key to move focus through the app.
  4. Observe that the keypad cannot be reached via the Tab key.

Expected behavior
Keypad should be included in the tab stops for the app. This also impacts navigation under Narrator.

Screenshots

Device and Application Information

  • OS Build: 10.0.19547.0
  • Architecture: x64
  • Application Version: 10.1912.4.0
  • Region: en-US
  • Dev Version Installed:

Additional context

Requested Assignment

I'm just reporting this problem. I don't want to fix it.

@MicrosoftIssueBot
Copy link
Collaborator

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

@MicrosoftIssueBot MicrosoftIssueBot added the Area: Accessibility Issues with keyboard interactions, screen readers, contrast, font size, and other accessibilty areas label Jan 21, 2020
@ghost ghost added the no recent activity label Jan 28, 2020
@ghost
Copy link

ghost commented Jan 28, 2020

This issue has been automatically marked as stale because it has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. Thank you for your contributions to Windows Calculator!

@grochocki
Copy link
Contributor

Thanks for the detailed bug report! This is by design in Graphing Mode.

Unlike other calculator modes where the onscreen keyboard is locked to one display input/output area, Graphing Mode supports free-form input. While we still have the on-screen keyboard, it now behaves more like a SIP and is not intended to receive keyboard or screen reader focus. All operations available in the SIP can be entered with standard keyboard input. The SIP is still available for simpler pointer input.

Free-from input in other modes is tracked by #620.

@grochocki grochocki added by design This issue or pull request already exists and removed investigate labels Jan 30, 2020
@MicrosoftIssueBot MicrosoftIssueBot removed the Bug Issue is a bug label Jan 30, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Area: Accessibility Issues with keyboard interactions, screen readers, contrast, font size, and other accessibilty areas by design This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants