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

Accessibility: tab test fails when trying to select Generic Work from the Work Type modal #6890

Closed
1 task
eporter23 opened this issue Aug 16, 2024 · 4 comments

Comments

@eporter23
Copy link
Contributor

Descriptive summary

As part of general testing from the QA worksheet with Hyrax 5.0.1, a user cannot successfully tab to the Generic Work selection option, but only can tab to the Monograph option.

Steps to reproduce the behavior in User Interface (UI)

See also steps in test A_1.6 from the Hyrax Maintenance working group QA worksheet.

  1. Login as a user with deposit priveleges
  2. Navigate to the homepage
  3. Use the keyboard to tab to Share your Work
  4. In the modal window, tab to Generic Work
  5. Observe that you cannot tab past the Monograph work type

Actual behavior (include screenshots if available)

Hyrax 5.0.1 - Sirenia docker image (main)

Acceptance Criteria/Expected Behavior

  • A user should be able to tab to select any Work Type listed

Rationale (for feature request only)

Provide the rationale or user story that describes "why" this issue should be addressed. Especially if this is a new feature or significant change to the existing implementation.

Hyrax should support standard accessibility features including tab-based navigation

Related work

Link to related issues or prior related work here.

@aahurford
Copy link

I'm seeing that you can tab to the generic work (the first option) but not past it.

Image

@jlhardes
Copy link
Contributor

Using the Tab key doesn't seem to be the way to work through that list of options when selecting a work type. You use the Tab key to get into the list and then the up and down arrow keys to move down through the options. I can do this now in both dev.nurax and pg.nurax. I will also test locally but I think this actually does pass keyboard accessibility.

@jlhardes
Copy link
Contributor

Testing on a local build is showing the same result - tabbing works to get into the Work Type list and then the up and down arrow keys are used to move through the list options. I don't think there is anything to change here for keyboard accessibility.

@christhepianist
Copy link

I agree with Julie. The important thing is that it is keyboard-accessible and it is. This is not a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Ready for Dev/Doc (priority ordered)
Development

No branches or pull requests

4 participants