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

Unable to reach search facet using the keyboard #2013

Open
shreyansh23 opened this issue Mar 27, 2019 · 3 comments
Open

Unable to reach search facet using the keyboard #2013

shreyansh23 opened this issue Mar 27, 2019 · 3 comments
Labels
Affects: UI Issues with the web site's user interface. [managed] Lead: @jdlrobson Issues overseen by Jon (Front-end Lead) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Accessibility Work related to disability accessibility. [managed] Type: Bug Something isn't working. [managed]
Projects

Comments

@shreyansh23
Copy link
Contributor

shreyansh23 commented Mar 27, 2019

Child issue of #2011
Sibling issues: #2014, #2015

Description
In order to reach the search facet one must tab through all the search results on the page. This effects keyboard users/screen readers.

Relevant url?
https://openlibrary.org/search?q=hello&mode=ebooks&m=edit&m=edit&has_fulltext=true

Expectation
The user should not need to tab through all the search results.

Proposed solution
To place the search facet before search results in the DOM and give a user the option to "Skip to search results" OR Give a user the option to "Skip to filters". An implementation of a "Skip to ___" option can be seen at archive.org

Additional suggestion
Should we reduce the number of book results shown on a page to save loading and traversing so many books at once?

Stakeholders
@mekarpeles @koderjoker

Issue credit: @koderjoker

@brad2014 brad2014 added Affects: UI Issues with the web site's user interface. [managed] Theme: Accessibility Work related to disability accessibility. [managed] Type: Bug Something isn't working. [managed] labels Jun 6, 2019
@jdlrobson jdlrobson added the Priority: 3 Issues that we can consider at our leisure. [managed] label Aug 1, 2019
@xayhewalo xayhewalo added this to Un-Triaged in Triage Oct 20, 2019
@xayhewalo
Copy link
Collaborator

@shreyansh23 Is this issue still relevant? The parent issue is closed.

@xayhewalo xayhewalo moved this from Un-Triaged to Needs: Assessment in Triage Nov 19, 2019
@xayhewalo xayhewalo added the Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] label Nov 19, 2019
@tfmorris
Copy link
Contributor

The parent was closed because @shreyansh23 split @koderjoker's list of problems into individual tickets.

@xayhewalo xayhewalo added Lead: @jdlrobson Issues overseen by Jon (Front-end Lead) [managed] and removed Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Dec 24, 2019
@xayhewalo xayhewalo moved this from Needs: Assessment to Triaged in Triage Dec 24, 2019
Copy link

Assignees removed automatically after 14 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: UI Issues with the web site's user interface. [managed] Lead: @jdlrobson Issues overseen by Jon (Front-end Lead) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Theme: Accessibility Work related to disability accessibility. [managed] Type: Bug Something isn't working. [managed]
Projects
No open projects
Triage
  
Triaged
Development

No branches or pull requests

6 participants
@tfmorris @jdlrobson @brad2014 @xayhewalo @shreyansh23 and others