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

Using "skip to content" button on search results page clears result counts (staging only) #3940

Closed
sarayourfriend opened this issue Mar 20, 2024 · 0 comments · Fixed by #3942
Assignees
Labels
♿️ aspect: a11y Concerns related to the project's accessibility 🛠 goal: fix Bug fix 🟥 priority: critical Must be addressed ASAP 🧱 stack: frontend Related to the Nuxt frontend

Comments

@sarayourfriend
Copy link
Contributor

Description

During keyboard navigation, using the "skip to content" button on the search page, the page will lose all result counts and say "no results" for all media types.

Reproduction

  1. Navigate to https://staging.openverse.org
  2. Tab once and select "skip to content"
  3. Tab again to enter the search box
  4. Type a search term ("galah" for example) and then enter to start the search
  5. Allow the page to finish loading the results and confirm that there are results and that the result counts on the page reflect the number of results (for galah, that's >10k images and 8 audio). To do so using keyboard navigation and a screen reader, you can tab to the results list without selecting skip to content and read the result counts.
  6. If you tabbed to the results list, tab back to the skip to content button, and select it. If you are on the page without having interacted, tab once and select skip to content.
  7. There will now be "no results" in all places that previously had result counts.

Additional context

This is on staging only right now (I cannot reproduce on openverse.org only staging.openverse.org), but I am marking as critical because we cannot deploy the frontend with this bug.

@sarayourfriend sarayourfriend added 🟥 priority: critical Must be addressed ASAP 🛠 goal: fix Bug fix ♿️ aspect: a11y Concerns related to the project's accessibility 🧱 stack: frontend Related to the Nuxt frontend labels Mar 20, 2024
@obulat obulat self-assigned this Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♿️ aspect: a11y Concerns related to the project's accessibility 🛠 goal: fix Bug fix 🟥 priority: critical Must be addressed ASAP 🧱 stack: frontend Related to the Nuxt frontend
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants