Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs Bug] Configuration of axe is wrong or misleading #4487

Open
masi opened this issue Apr 17, 2021 · 1 comment
Open

[Docs Bug] Configuration of axe is wrong or misleading #4487

masi opened this issue Apr 17, 2021 · 1 comment

Comments

@masi
Copy link

masi commented Apr 17, 2021

📚 Request documentation enhancements

Description

https://webhint.io/docs/user-guide/hints/hint-axe/#can-the-hint-be-configured

It says:

You can modify what rules or categories are executed via an options object that follows axe’s documentation.

Then an example follows that does not look at all like a real axe configuration. It is completely unclear how options can be passed to axe.

I am not even sure if options refers to the second parameter of the axe.run() method or all of them.

In particular I want to set the "exclude" options for a part of the page that is not accessible and cannot (sad but true) be fixed. For that I need to use the first parameter of axe.run(), which is called context.

https://github.com/dequelabs/axe-core/blob/develop/doc/API.md#context-parameter
https://github.com/dequelabs/axe-core/blob/develop/doc/API.md#options-parameter

@hxlnt
Copy link
Member

hxlnt commented Apr 23, 2021

Thanks for filing the issue. You're right--this is a docs bug. We don't currently support passing the axe configuration. However, we'll fix the docs and open a new bug to track excluding part of the page as a feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants