Time | Item | Presenter | Notes |
|---|
25 min | Chip component design specifications | Jennifer Gregory | Goal is to review and green-light design specifications for Chip component, including basic and selectable variants, to ready for implementation Particularly interested in a11y related feedback! I have a hard stop at 11:30ET and would like to present first if possible 
Notes: Implementation of Multiselect as designed led to discrepancy between Chip design and its implementation. Basic chip = whole Chip is clickable a11y role = button Outline of the inactive state of basic chip is pretty light, likely doesn’t pass WCAG. Chip should be able to get used either as a button or a hyperlink (e.g., standard hyperlink or React router Link)
How can we tell difference between link vs. interactive button? Do we need to differentiate? Is this more of a usage/pattern guideline? Likely should be flexible as is to use same styles between hyperlink and buttons. Other design systems seem to follow a similar pattern.
Selectable Chip Next STEPS
|
5 min
| Splitting up large PRs
| Brian Smith
| Define: We will split large PRs up into smaller incremental, independently reviewed PRs.
|
10 min | Build and PR a11y testing | Jeff Witt (Deactivated) | axe-core is open source now, but will be $$ in the future
Notes: |
5 min | ariaNotification spec | Jeff Witt (Deactivated) | https://wicg.github.io/aom/notification-api.html feedback is welcome |
10 min | Autosuggest status update | Brian Smith | https://github.com/openedx/paragon/issues/2634 |