Content suggestion: Aria tabpanel and tablist role

[Ryuno-Ki]

What is the new suggestion?

Our documentation on ARIA tabpanel role is marked as draft and stands out (compared to other ARIA roles documentation).

Why is it important or useful?

How many pages are likely to be needed?

Next to aria-role="tabpanel" information missing for aria-role="tablist".

How much time do you think this work should take? A few hours? A week? A month?

Depends on the author, I guess.

Will the work enable learners or professionals to achieve their goals better?

I'm aware of the first rule of ARIA. Right now, I'd recommend https://inclusive-components.design/tabbed-interfaces/#truetabbedinterfaces

Does it address critical needs in the web industry?

Since the React Testing Library priority guide about queries recommends to use roles (even implicit ones) over unsemantic markup, having these pages documented could help in getting the web more accessible.

Is the work an operational necessity, i.e. is not having it a security risk?

No, it will work (for sighted users) anyway. But we care about all users, right?

Does the content help make the web more ethical?

I hope so!

Other supporting information

The spec is already in the page: https://www.w3.org/TR/wai-aria-1.1/#tabpanel
The second spec should link to https://www.w3.org/TR/wai-aria-practices-1.1/#tabpanel

#366 goes into the same direction, but deals with another page.

[chrisdavidmills]

Thanks for pointing this out @Ryuno-Ki . We've already got an RFC filed for describing work required to sort our ARIA roles docs out: see https://github.com/mdn/content/blob/main/rfcs/aria-roles.md

I'd be happy for you to raise a PR to add a link to this from there, maybe under a heading of "Related issues" or similar?

[Ryuno-Ki]

Ah, the good old spreadsheet :-D

As far as I can tell, the next step would first to create a meta issue to list all the ARIA pages in need of creation / update and then find people willing to fill them with information.

These could be then added as a new section to the RFC (via PR).

I happen to know some accessibility experts and could reach out once there is something concrete.
Otherwise, I'd do research on The Paciello Group, WebAIM, Knowbility and that like.

Does that sound like a plan to you?

[estelle]

https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Tabpanel_Role
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Tabist_Role