Skip to content

calcite-pagination navigation buttons does not shift focus to the first focusable element #11920

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

Closed
2 of 5 tasks
minhiu opened this issue Apr 10, 2025 · 0 comments
Closed
2 of 5 tasks
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs triage Planning workflow - pending design/dev review.

Comments

@minhiu
Copy link

minhiu commented Apr 10, 2025

Check existing issues

Summary

Issue
There are interactive elements in page content that do not receive focus when the next/previous button in Pagination is activated.

User Impact
Screen reader users will be unable to determine that these page content has changed unless they review the entire page. Keyboard-only users will have difficulty navigating into the page content.

Recommendation
Ensure that when the "next page" button in a pagination component is activated, the focus moves to the first interactive element on the new page. Use the JavaScript focus() method to move keyboard focus to the first interactive element.

Actual Behavior

  • After hitting "Next" or "Previous" Pagination button, the focus stays the same.
  • Keyboard users stay "stuck" there and might not realize the content has changed.
  • Screen readers may not announce the new content unless focus moves or there's a screen reader cue.

Expected Behavior

After loading new paginated content (say, a new list of results), programmatically move focus to the first interactive element (like a link or button) or to a heading that introduces the content.

Reproduction Sample

https://developers.arcgis.com/calcite-design-system/components/pagination/

Reproduction Steps

  1. Locate the pagination component.
  2. Navigate the page using tab key.
  3. Activate the "next page" button to move to the next set of content.
  4. Observe the behavior of the focus after the new page loads.

Reproduction Version

3.0.0

Working W3C Example/Tutorial

No response

Relevant Info

No response

Regression?

No response

Priority impact

impact - p2 - want for an upcoming milestone

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Business/Community Analyst

@minhiu minhiu added 0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. needs triage Planning workflow - pending design/dev review. labels Apr 10, 2025
@github-actions github-actions bot added ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone labels Apr 10, 2025
@minhiu minhiu closed this as completed Apr 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. ArcGIS Business/Community Analyst Issues logged by ArcGIS Business/Community Analyst team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. impact - p2 - want for an upcoming milestone User set priority impact status of p2 - want for an upcoming milestone needs triage Planning workflow - pending design/dev review.
Projects
None yet
Development

No branches or pull requests

1 participant