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

Maintain Focus After Filter Selection #3140

Open
4 tasks
SamiyahKey opened this issue Nov 26, 2024 · 1 comment
Open
4 tasks

Maintain Focus After Filter Selection #3140

SamiyahKey opened this issue Nov 26, 2024 · 1 comment
Labels
accessibility pertains to Section 508 compliance or other accessibility needs blocked Is dependent on another issue and cannot be worked 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant compliance indicates that the issue is required to satisfy a necessary compliance req dev issue is for the dev team story User stories

Comments

@SamiyahKey
Copy link

SamiyahKey commented Nov 26, 2024

Story

As a user relying on keyboard navigation or assistive technologies,
I need the focus to remain on the selected filter after a page reload,
so that I can continue my interaction seamlessly without unnecessary navigation back to my previous position.

URL: Domain Request
https://getgov-staging.app.cloud.gov/admin/registrar/domainrequest/

Acceptance Criteria

  • When a user selects a filter, the focus remains on the filter after the page reloads.
  • The implementation preserves logical focus order, ensuring users can continue navigating smoothly.
  • Screen readers should announce the updated page state and confirm the selected filter.
  • Confirm with a designer that the focus behavior adheres to WCAG 2.1 Standards 2.4.3 and 3.2.2.

Additional Context

  • Add a script to dynamically set focus back to the filter element after the page reload.
  • Include announcements for screen readers using ARIA live regions or similar mechanisms to inform users of the state change.
  • Test with a variety of assistive technologies to ensure compatibility.

Issue Links

@SamiyahKey SamiyahKey added design issue is for the design team story User stories labels Nov 26, 2024
@SamiyahKey SamiyahKey self-assigned this Nov 26, 2024
@SamiyahKey SamiyahKey added compliance indicates that the issue is required to satisfy a necessary compliance req accessibility pertains to Section 508 compliance or other accessibility needs blocked Is dependent on another issue and cannot be worked dev issue is for the dev team and removed design issue is for the design team labels Nov 26, 2024
@SamiyahKey SamiyahKey removed their assignment Dec 4, 2024
@katypies katypies moved this from 👶 New to 🍦 Backlog in .gov Product Board Jan 14, 2025
@zandercymatics
Copy link
Contributor

zandercymatics commented Jan 23, 2025

@CocoByte This will be a big one - this behavior exists basically on all tables, so we'd either need a way to apply this changes across all tables or go in by hand and do it one-by-one (with the former obviously being better)

This also seems like something that should be done with this ticket:
#3144

@zandercymatics zandercymatics added the 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility pertains to Section 508 compliance or other accessibility needs blocked Is dependent on another issue and cannot be worked 👥 Pod:Accessibility Compliance Describes work needed for get.gov and manage.get.gov to be Section 508 Compliant compliance indicates that the issue is required to satisfy a necessary compliance req dev issue is for the dev team story User stories
Projects
Status: 🍦 Backlog
Development

No branches or pull requests

2 participants