primefaces / primefaces/primereact

Accessiblity WCAG 2.2

Open
#1,887 17 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Accessibility Type: Enhancement
Dominant language
CSS
Stars
8.3k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

I am just trying out PrimeReact and noticed a lot of the component do not meet the WCAG 2.1 standards.
An example is the Tabs where it is not keyboard accessible and it is not a 1 tab stop.

Are there any plans to make this WCAG 2.1 compliant?

Contributor guide

Open the contributing guide

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.

Research direction

Start with the Tabs component and reproduce the reported keyboard-navigation and tab-stop behavior. Compare the current behavior with the relevant WCAG 2.1/2.2 requirements, then determine the scope across the other components mentioned in the issue. Done requires an agreed component list and verified accessibility improvements, but no files or tests are named.

Written by the indexing model from the issue text.

Assessment

Tech stack
react
Domain
accessibility, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.