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

Keyboard focus resets on invoking 'using the components' link to first interactive element of the page. #9163

Open
2 of 7 tasks
msftedad opened this issue Jul 21, 2023 · 3 comments
Labels
bug An error in the Docusaurus core causing instability or issues with its execution domain: a11y Related to accessibility concerns of the default theme

Comments

@msftedad
Copy link

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
  • I have tried creating a repro with https://new.docusaurus.io.
  • I have read the console error message carefully (if applicable).

Description

Keyboard focus resets on invoking 'using the components' link to first interactive element of the page.

On invoking 'using the components' link Keyboard focus resets to first interactive element of the page.

Keyboard focus resets on invoking 'using the components' link to first interactive element of the page.

User with motor impairment who rely on keyboard technology will face difficulties if keyboard focus resets on invoking navigation link 'Using the components' link

Focus.resets.webm

Reproducible demo

No response

Steps to reproduce

Repro Steps:

  1. Open https://www.fast.design/ URL.
  2. Navigate to link ‘Documentation’ and invoke it.
  3. Navigate to navigation link 'using the components' and invoke it.
  4. Observe the keyboard focus.

Expected behavior

Keyboard focus should not reset to first interactive element of the page on invoking 'Using the components' link, instead focus should land to main landmark first interactive element i.e., 'Quick Start'.

Actual behavior

Keyboard focus resets on invoking 'using the components' link to first interactive element of the page.

Your environment

  • Public source code:
  • Public site URL: https://www.fast.design/
  • Docusaurus version used: Version: 2.4.1
  • Environment name and version (e.g. Chrome 89, Node.js 16.4): Microsoft Edge
    Version 114.0.1823.86 (Official build) (64-bit)
  • Operating system and version (e.g. Ubuntu 20.04.2 LTS): OS Name: Microsoft Windows 11 Enterprise
    Version: 10.0.22621 Build 22621

Self-service

  • I'd be willing to fix this bug myself.
@msftedad msftedad added bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Jul 21, 2023
@slorber slorber added domain: a11y Related to accessibility concerns of the default theme and removed status: needs triage This issue has not been triaged by maintainers labels Jul 21, 2023
@kemilbeltre
Copy link

I'm not a11y expert, but I think this is the "natural" behavior of websites. If you open a new page, the keyboard focus is automatically reset because you will probably have a different layout.

@msftedad
Copy link
Author

Hi @kemilbeltre, we have discussed with PO team and we got a reply that

We have agreed to the comment, but focus can only be reset when if the invoked element is opened new tab. But here it is opening in the same page not in new page (Tab). So, focus should not get reset if the invoked element is opened in the same page.

Can you please look into this comment and let us know if you need more information. Thanks.

@msftedad
Copy link
Author

Hi @kemilbeltre, Any update on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An error in the Docusaurus core causing instability or issues with its execution domain: a11y Related to accessibility concerns of the default theme
Projects
None yet
Development

No branches or pull requests

3 participants