2023-08-02 Meeting notes

5-10 mins

Notifications UI

Adam Stankiewicz

Web-based notifications UI: Tabs

Figma

The notification bubble shown above differs from what exists in the implemented Tabs component today (docs):

[curious] Will/should there be a Paragon proposal to update the Tabs component’s notification?

5-10 min

CardGrid new prop

Max Frank

To accommodate the ability to forward props to the Row that is wrapped inside this component.

Here is a GH issue for more detail: https://github.com/openedx/paragon/issues/2478

This will enable us to make expandable CardGrids more accessible: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-expanded

Questions for the group:

1. Should this prod just forward an ID or do we want to support forwarding a list of props to the Row?

2. What should the prop be called?
   

5 min

Potential breaking change to Paragon

Max Frank

PR to add support for aria-labelleby and props-forwarding to the SelectableBoxSet component:
https://github.com/openedx/paragon/pull/2461

There is a discussion going on in the PR about how this is a breaking change because the label is actually required for this component to pass accessibility checks (Jeff or other a11y specialists feel free to jump in on this).

What I need from the group:

• PR is ready for another pass of review

• I will most likely need some guidance in regards to how we handle breaking changes. I can see how to format the commit message, but am wondering if there is any other protocol to follow? Any docs I can look at?

5 mins

Accessibility information for components on the Paragon docs site

Vladyslav Zadorozhnii

I think it is interesting to know what accessibility standards are used for specific component. Also it allows to revisit components accessibility.
Solution: Put accessibility information in the table at the bottom of a component page. Maybe provide separate Accessibility page with basic information.