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.

Sign up for GitHub

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

Jump to bottom

[Table] When interactionMode="interactive", restrict Tab use within Table #8912

Open
2 of 6 tasks
macandcheese opened this issue Mar 8, 2024 · 1 comment
Open
2 of 6 tasks

[Table] When interactionMode="interactive", restrict Tab use within Table #8912

macandcheese opened this issue Mar 8, 2024 · 1 comment
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. blocked This issue is blocked by another issue. Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - low Issue is non core or affecting less that 10% of people using the library
Milestone
Stalled

Comments

@macandcheese
Copy link
Contributor

macandcheese commented Mar 8, 2024 •
edited
Loading

Check existing issues

Description

When Table is in interactionMode="interactive" (default) - navigation should only occur with arrow keys / home / end / etc. Tab and Shift Tab should only be used to enter / exit the Table body (and move to Pagination / selection controls / slotted actions if applicable)

Acceptance Criteria

Shift / Shift Tab are not used to navigate individual cells within Table

Relevant Info

cc @geospatialem for a11y confirmation

Which Component

Table

Example Use Case

No response

Priority impact

p4 - not time sensitive

Calcite package

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

Esri team

Calcite (design)
@macandcheese macandcheese added enhancement Issues tied to a new feature or request. 0 - new New issues that need assignment. needs triage Planning workflow - pending design/dev review. labels Mar 8, 2024
@github-actions github-actions bot added Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive labels Mar 8, 2024
@macandcheese macandcheese mentioned this issue Mar 8, 2024
Closed
3 tasks
@geospatialem geospatialem added a11y Issues related to Accessibility fixes or improvements. p - low Issue is non core or affecting less that 10% of people using the library estimate - 3 A day or two of work, likely requires updates to tests. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed needs triage Planning workflow - pending design/dev review. labels Aug 27, 2024
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Sep 10, 2024
@macandcheese
Copy link
Contributor Author

Blocked by #6646

@geospatialem geospatialem mentioned this issue Oct 16, 2024
Open
@geospatialem geospatialem added the blocked This issue is blocked by another issue. label Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. blocked This issue is blocked by another issue. Calcite (design) Issues logged by Calcite designers. calcite-components Issues specific to the @esri/calcite-components package. enhancement Issues tied to a new feature or request. estimate - 3 A day or two of work, likely requires updates to tests. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - low Issue is non core or affecting less that 10% of people using the library
Projects
None yet
Milestone
Stalled
Development

No branches or pull requests
2 participants
@macandcheese @geospatialem