Allow specifying root selector/element for initial report. Fix #36 - #59
Open
jairovg wants to merge 3 commits into
Open
Allow specifying root selector/element for initial report. Fix #36#59jairovg wants to merge 3 commits into
jairovg wants to merge 3 commits into
Conversation
This element will be used as the default context sent to `axe.run` Fix: vue-a11y#36
…oint It runs the audit against `document` with the manual run to check against an injected bug in the page head
|
Good approach, this will enhance user experience. |
|
Awesome!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
General Notes
This PR allows the set-up of a root element different from the document to run the audit on the first load. Fix #36
NOTE: This element will be used as the default context sent to
axe.run.What kind of change does this PR introduce? (check at least one)
Documentation updated with the new element for the plugin config.
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements: