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

Component Accessibility Status: Final Dev Deliverable #3519

Closed
3 tasks
laurenmrice opened this issue May 1, 2023 · 4 comments
Closed
3 tasks

Component Accessibility Status: Final Dev Deliverable #3519

laurenmrice opened this issue May 1, 2023 · 4 comments
Labels

Comments

@laurenmrice
Copy link
Member

laurenmrice commented May 1, 2023

Developer | Will work on showing this final design on the website while working closely with a designer (Thy)

  • Task 1 (dev defines the work here)
  • Task 2 (dev defines the work here)
  • Task 3 (dev defines the work here)
@laurenmrice laurenmrice added this to the 2023 Q2 milestone May 1, 2023
@sstrubberg sstrubberg added type: docs 📖 role: design ✏️ adopter: strategic-product Work-stream that directly effects the Product-led Growth initiative. type: a11y ♿ labels May 1, 2023
@sstrubberg sstrubberg changed the title Design: finalize design spec Component Accessibility Status: finalize design spec May 1, 2023
@sstrubberg sstrubberg modified the milestones: 2023 Q2, 2023 Q3 Jun 27, 2023
@sstrubberg sstrubberg changed the title Component Accessibility Status: finalize design spec Component Accessibility Status: prototyping Jul 11, 2023
@tay1orjones
Copy link
Member

tay1orjones commented Aug 9, 2023

As part of this, dev should explore how to surface reporting of what types of tests a component has via playwright's grep tags. We may need to add new tags, @avt, @avt-complex-states, @avt-keyboard-nav, @vrt, etc.

By gathering these tests per-component we should be able to produce a JSON file or something that contains data giving us the ability to build a table something like

Component @avt @avt-complex-states other tags ...etc
Dropdown 🚫 ...
MultiSelect ...
Button 🚫 ...

@tay1orjones
Copy link
Member

Another concern brought up was that as we look at this, we should take into account that these tests are only for @carbon/react and the design needs to scale to include other framework implementations, such as @carbon/web-components.

@sstrubberg sstrubberg modified the milestones: 2023 Q3, 2023 Q4 Oct 2, 2023
@tay1orjones
Copy link
Member

Looking forward, this issue will contain the work that comes out of the design explorations:

@sstrubberg sstrubberg changed the title Component Accessibility Status: prototyping Component Accessibility Status: flejfie Nov 14, 2023
@sstrubberg sstrubberg changed the title Component Accessibility Status: flejfie Component Accessibility Status: Final Final FINAL Nov 14, 2023
@thyhmdo thyhmdo changed the title Component Accessibility Status: Final Final FINAL Component Accessibility Status: Final Dev Deliverable Nov 15, 2023
@sstrubberg
Copy link
Member

closing in favor of the issues created yesterday in refinement.

@sstrubberg sstrubberg closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants