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

Create New TabGroup KComponent #385

Closed
marcellamaki opened this issue Nov 21, 2022 · 1 comment
Closed

Create New TabGroup KComponent #385

marcellamaki opened this issue Nov 21, 2022 · 1 comment
Assignees
Labels
P0 - critical Priority: Release blocker or regression

Comments

@marcellamaki
Copy link
Member

marcellamaki commented Nov 21, 2022

Product

Kolibri

Specifically, this issue is blocking: learningequality/kolibri#9849

Desired behavior

We should create a new TabGroup component for proper accessible handling of tab that are used at the top of many components and pages. Currently, although our tabs are configured successfully to be keyboard navigable, they do not follow WCAG criteria for creating a coherent experience, especially for the screen-reader user. Tab groups should have the relevant information so context is carried over throughout navigation, and they are still experienced as a "group" in the same way they can be perceived visually.

This can be used across Kolibri for accessibility remediation, and can be used to more quickly build accessible pages in the future.

The component should essentially be a Vue implementation of the HTML pattern explained in this example from W3C.

The component should have a header, a customizable number of tabs, and any content for the active tab that can be set through a slot. Proper aria-labelledby and aria-selected should be implemented.

Any questions or concerns during planning, please consult with @radinamatic and @marcellamaki

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 - critical Priority: Release blocker or regression
Projects
None yet
Development

No branches or pull requests

2 participants