dequelabs/axe-core

Expose a rule's `enabled` property in the official API

Chiusa

#5116 aperta il 24 mag 2026

Vedi su GitHubGuida contributor
 (2 commenti) (0 reazioni) (0 assegnatari)JavaScript (783 fork)batch import
feathelp wanted

Metriche repository

Star
 (5457 stelle)
Metriche merge PR
 (Merge medio 6g) (21 PR mergiate in 30 g)

Descrizione

Product

axe-core

Feature Description

To my knowledge, there's currently no official way to get the list of rules that are enabled when axe.run() is called with no options.

There's an axe.getRules() method, but that returns all rules, including the ones that are disabled by default.

There is an undocumented way to get such a list today (axe._audit.rules.filter(rule => rule.enabled)).

It would be great to expose the ability to filter rules by whether they're enabled as part of the official API, for example by adding the enabled key to the rule objects returned by axe.getRules(), or by introducing a new method.

Guida contributor

Direzione di ricerca
Start by examining the existing `axe.getRules()` method in `doc/API.md` and its implementation. Look at how rules are stored in `axe. audit.rules` and how the `enabled` property is used. The goal is to add `enabled` to the returned rule objects or create a new method. Check any related issues or PRs for context.
Tech stack
javascript
Dominio
apiaccessibilitytesting
Tipo issue
Funzionalità
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 ore
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Nuova
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Chiara
Prerequisiti
JavaScriptFamiliarity with axe core API
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
75