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

Epic: Keyboard a11y with arrow keys, Home, and End for components #5470

Open
3 of 6 tasks
geospatialem opened this issue Oct 13, 2022 · 3 comments
Open
3 of 6 tasks
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. Calcite (dev) Issues logged by Calcite developers. docs Issues relating to documentation updates only. enhancement Issues tied to a new feature or request. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. 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. p - low Issue is non core or affecting less that 10% of people using the library spike complete Issues that have a research spike completed and dev work can proceed

Comments

@geospatialem
Copy link
Member

geospatialem commented Oct 13, 2022

Background

This epic organizes components we're seeking to enhance keyboard accessibility using the Home, End, and arrow keys.

This epic across components will provide a better supported behavior for assistive technology and keyboard users.

As opposed to using the Tab and Shift + Tab keys, which shouldn't be the expected behavior with the components listed below.

Came up as a resolution for components when discussing #5113.

Plan of action

Anticipated after the v1.0.0 release

Components

Other potential components

Note: may be solved with the list component refactor.

  • List / List Item Group / List Item
  • Pick List / Pick List Group / Pick List Item - N/A, deprecated
  • Value List / Value List Group / Value List Item - N/A, deprecated

cc @macandcheese for usability feedback considerations

@geospatialem geospatialem added enhancement Issues tied to a new feature or request. docs Issues relating to documentation updates only. design Issues that need design consultation prior to development. a11y Issues related to Accessibility fixes or improvements. 0 - new New issues that need assignment. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. Calcite (dev) Issues logged by Calcite developers. labels Oct 13, 2022
@alisonailea alisonailea added airtable and removed airtable docs Issues relating to documentation updates only. labels Feb 28, 2023
@geospatialem geospatialem added the needs triage Planning workflow - pending design/dev review. label Mar 3, 2023
@geospatialem geospatialem removed airtable design Issues that need design consultation prior to development. labels May 25, 2023
@geospatialem geospatialem added spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. and removed needs triage Planning workflow - pending design/dev review. labels Dec 18, 2023
@geospatialem geospatialem self-assigned this Dec 18, 2023
@geospatialem geospatialem added 1 - assigned Issues that are assigned to a sprint and a team member. and removed 0 - new New issues that need assignment. labels Dec 18, 2023
@geospatialem geospatialem added the p - low Issue is non core or affecting less that 10% of people using the library label Dec 18, 2023
@geospatialem
Copy link
Member Author

Spike to confirm applicable components across the design system for consideration.

@geospatialem geospatialem added the docs Issues relating to documentation updates only. label Dec 19, 2023
@geospatialem
Copy link
Member Author

Confirmed only accordion and pagination should support the home and end keys. The new effort with the carousel component may want to consider the keys if it fits the new design.

Adding the docs label to the above effort ☝🏻 , as once this effort is completed we should also add to the keyboard accessibility section to the component doc pages.

@geospatialem geospatialem added the spike complete Issues that have a research spike completed and dev work can proceed label Dec 19, 2023
@github-actions github-actions bot added 0 - new New issues that need assignment. needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. 1 - assigned Issues that are assigned to a sprint and a team member. labels Dec 19, 2023
Copy link
Contributor

cc @geospatialem, @brittneytewks

@geospatialem geospatialem added the estimate - 3 A day or two of work, likely requires updates to tests. label Dec 19, 2023
@geospatialem geospatialem removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Jan 10, 2024
@geospatialem geospatialem added the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Feb 24, 2025
@DitwanP DitwanP removed this from the 2025-03-25 - 3.1.0 Mar Release milestone Feb 24, 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. Calcite (dev) Issues logged by Calcite developers. docs Issues relating to documentation updates only. enhancement Issues tied to a new feature or request. epic Large scale issues to be broken up into sub-issues and tracked via sprints and/or project. 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. p - low Issue is non core or affecting less that 10% of people using the library spike complete Issues that have a research spike completed and dev work can proceed
Projects
None yet
Development

No branches or pull requests

3 participants