Accessibility: document tabs — div children in ul (axe list), Versions tab label does not contain its text (label-content-name-mismatch)

Open Beginner friendly
#19,832 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active

Research direction

Search @payloadcms/ui for the doc-tabs__tabs class name to find the tab strip component, then look at how each tab is rendered: the container is a ul but children are div, and the Versions tab gets an aria-label that omits the count it displays. Confirm the current markup by opening a document edit screen in the admin and inspecting the tab strip, or by running the existing Playwright/axe setup. Done looks like li children (or dropped list semantics) plus an accessible name that starts with the visible text, with no new axe list or label-content-name-mismatch violations.

Written by the indexing model from the issue text.

Description

Bug Payload OSS

Payload version: 3.91.0 (@payloadcms/ui, @payloadcms/next, @payloadcms/richtext-lexical 3.91.0), Next.js 16.4.2, @payloadcms/db-postgres. The same component code is unchanged in the published 3.94.1 packages (checked by inspecting dist, not by running 3.94.1).

How found: axe-core via @axe-core/playwright (default rules), on the admin with seeded content, signed in as an admin, 1600×900.

Rules: list (serious), label-content-name-mismatch (serious). WCAG 2.2 SC 1.3.1 and 2.5.3.

On every document edit screen, the Edit / Versions / API tab strip:

  1. <ul class="doc-tabs__tabs"> contains div elements directly instead of li, so assistive technology reports a broken list.
  2. The Versions tab is <a ... aria-label="Versions" class="btn doc-tab ..."> while its visible text includes the version count. The accessible name does not contain the visible text, so a voice-control user saying what they see (e.g. "click Versions 3") may not match.

Steps: open any document in a collection with versions; run axe, or inspect .doc-tabs__tabs.

Expected: li children (or no list semantics), and the Versions tab's accessible name starting with its visible text (or no aria-label overriding it).

Dominant language
TypeScript
Stars
45.8k
Forks
4.4k
Avg merge
3d 4h
Merged PRs (30d)
210

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from payloadcms/payload

All issues in payloadcms/payload

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.