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

calcite-action ARIA attributes #10411

Open
2 of 6 tasks
vivzhang opened this issue Sep 26, 2024 · 2 comments
Open
2 of 6 tasks

calcite-action ARIA attributes #10411

vivzhang opened this issue Sep 26, 2024 · 2 comments
Labels
0 - new New issues that need assignment. a11y Issues related to Accessibility fixes or improvements. ArcGIS Hub Issues logged by ArcGIS Hub team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.

Comments

@vivzhang
Copy link

vivzhang commented Sep 26, 2024

Check existing issues

Summary

Remove the aria-disabled, aria-busy and aria-pressed attributes on calcite-action. Please ignore the request for aria-label, the Hub team will address that by passing in a unique value for the label property for their use case.

Original AMP issues:
11242
11244

Actual Behavior

  1. aria-disabled, aria-busy and aria-pressed attributes rendered on the button inside calcite-action
  2. aria-pressed stays as false even when the button is clicked (via calcite-action: the aria-pressed attribute in the component does n't convey the correct state of the collapse and expand of the calcite-action-group.. #11110):
Screenshot 2024-12-19 at 11 15 49 AM

Expected Behavior

  1. No aria-disabled, aria-busy and aria-pressed rendered on the button inside calcite-action
  2. aria-pressed should convey the correct state. When the collapse /expand is pressed, it should change to true and vice-versa.

Reproduction Sample

https://codepen.io/vivzhang/pen/rNXVWBo

re: item 2 in actual/expected behavior from #11110:

  1. Inspect the calcite-action element
  1. Note element does not provide the correct aria-pressed information on clicking on collapsing /expanding button.

Reproduction Steps

  1. Open the devtool console
  2. Inspect the calcite-action component
  3. You should see the aria-disabled and an aria-busy attributes rendered on the button element

Reproduction Version

3.12.1

Working W3C Example/Tutorial

No response

Relevant Info

related: #10706

Regression?

No response

Priority impact

impact - p3 - 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

Arcgis Hub

@vivzhang vivzhang 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. p - high Issue should be addressed in the current milestone, impacts component or core functionality labels Sep 26, 2024
@github-actions github-actions bot added impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive ArcGIS Hub Issues logged by ArcGIS Hub team members. labels Sep 26, 2024
@jcfranco
Copy link
Member

Some notes:

@driskull
Copy link
Member

driskull commented Nov 6, 2024

I think we need to research more why aria-busy on an action is a problem. Would we need another property added to action to allow aria-busy to be set? like a loadable property?

I would expect this would apply to other components where aria-busy is being used.

@geospatialem geospatialem added spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment. p - medium Issue is non core or affecting less that 60% of people using the library needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. and removed p - high Issue should be addressed in the current milestone, impacts component or core functionality needs triage Planning workflow - pending design/dev review. labels Nov 12, 2024
@DitwanP DitwanP added this to the 2025-06-24 - Jun Milestone milestone Dec 16, 2024
@DitwanP DitwanP removed the needs milestone Planning workflow - pending milestone assignment, has priority and/or estimate. label Dec 16, 2024
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 Hub Issues logged by ArcGIS Hub team members. bug Bug reports for broken functionality. Issues should include a reproduction of the bug. impact - p3 - not time sensitive User set priority impact status of p3 - not time sensitive p - medium Issue is non core or affecting less that 60% of people using the library spike Issues that need quick investigations for time estimations, prioritization, or a quick assessment.
Projects
None yet
Development

No branches or pull requests

5 participants