dequelabs/axe-core - Open Source PR Review Scorecard

Accessibility engine for automated Web UI testing

C-Rank Grade: A (Welcoming) - 62/100

External PR Merge Rate: 70%

Response Time: 13h

First Timer Success: 63%

Frequently Asked Questions

Is dequelabs/axe-core welcoming to first-time open-source contributors?

dequelabs/axe-core has a recorded first-timer success rate of 62.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in dequelabs/axe-core respond to incoming external pull requests in approximately 12.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 61.8 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 61.8 places dequelabs/axe-core in the A tier.

What is the external contributor pull request merge rate for dequelabs/axe-core?

The external contributor pull request merge rate for dequelabs/axe-core is 70.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in dequelabs/axe-core?

dequelabs/axe-core does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

dequelabs
dequelabs/axe-coreA•Welcoming7.5k
GitHub
Back to Explorer
dequelabs

dequelabs/axe-core

7,472
Active (30d)A•Welcoming(62/100)JavaScript

Accessibility engine for automated Web UI testing

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.4/10
Patience Score
7.8/10
Nitpick Rate
33%

Balanced & professional review environment in dequelabs/axe-core. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
12 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
70.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
62.5%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
32 core
Highly collaborative maintainer core
Diagnostic Health HUD
70.4%
Merge Gauge
62.5%
1st-Timer
Community Vibe67/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for dequelabs/axe-core
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/dequelabs/axe-core)](https://getmerged.abhishekco.de/dequelabs/axe-core?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Product axe-core Product Version 4.12.1 Latest Version I have tested the issue with the latest version of the product Issue Description Expectation p-as-heading should not report a violation for a <p> element that carries an explicit role="heading" with aria-level. Such an element is exposed as a heading in the accessibility tree, and the pattern is ARIA12, a documented sufficient technique for SC 1.3.1. The element should not be matched by the rule at all (expected outcome: inapplicable). Actual The element is reported as a serious violation — "Heading elements should be used instead of styled <p> elements" — regardless of the role or aria-level present on it. How to Reproduce <div id="root"> <p role="heading" aria-level="1" style="font-size: 2em; font-weight: 700;">Section title</p> <p>Body copy that follows the heading.</p> </div> axe.run('#root', { runOnly: ['p-as-heading'] }) .then(results => console.log(results.violations)); Result: one violation, target #root > p:n

📅 Opened Aug 4, 2026💬 2 comments
Quality: 50/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for dequelabs/axe-core

When evaluating whether to contribute to dequelabs/axe-core, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of dequelabs/axe-core acknowledge new external contributions in approximately 12 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to dequelabs/axe-core

01

Is dequelabs/axe-core welcoming to first-time open-source contributors?

dequelabs/axe-core has a recorded first-timer success rate of 62.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~12 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 61.8 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 61.8 places dequelabs/axe-core in the Welcoming tier.

04

What is the external contributor pull request merge rate for dequelabs/axe-core?

The external pull request merge rate is 70.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in dequelabs/axe-core?

dequelabs/axe-core does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for dequelabs/axe-core are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.