You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are cases when you want to exclude some areas from the page to be checked. I'm running axe-scan in a testing pipeline and I'm triggering a failure when there are violations. But the pages from certain URLs might contain user content with A11Y violations and that is something we can't control/enforce, thus we want to exclude from scan
Hi @claudiu-cristea, thank you for a great suggestion!
Adding the exclude option seems relatively straightforward. I'll see if I can add them in the coming updates 👍
Problem
There are cases when you want to exclude some areas from the page to be checked. I'm running
axe-scan
in a testing pipeline and I'm triggering a failure when there are violations. But the pages from certain URLs might contain user content with A11Y violations and that is something we can't control/enforce, thus we want to exclude from scanProposal
axe-core
knows to exclude areas from a11y compliance check, see https://github.com/dequelabs/axe-core/blob/develop/doc/context.md#exclude-elements-from-testaxe-core-npm
also knows to pass such options, see https://github.com/dequelabs/axe-core-npm/tree/develop/packages/puppeteer#axepuppeteerexcludeselector-string--stringaxe-scan.config.json
, a list of CSS selectors to be excluded from checkThe text was updated successfully, but these errors were encountered: