-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test Coverage by Domain #15
Comments
I'm now thinking it might be useful to have not only the raw numbers, but also:
|
|
@mgifford Can you please run this request under the |
Hotfix for #15 Signed-off-by: Bentley Hensel <bentleyhensel@gmail.com>
Did I break it? "Cloud Agent Error: Couldn't resolve host. Make sure the domain is publicly accessible or select a different agent." |
I've been horrible about updating Github, but a ton of pushes have been going out lately. I am getting very very close to a massive windfall on these projects. By the end of this week, we will have a system which crawls, uppies, tech, and basic Axe with the new data schema and most of the reports will be active. |
How will I validate that when it is ready? Will it just be on gova11y.io or something I build in Docker? What instructions will be provided for me to follow? |
Question
What is the total number of pages (URLs) that we are currently tracking and evaluating with Axe to prove the comprehensiveness of our accessibility testing?
Target Audience
The intended audience for this report includes web management team, SEO specialists, and stakeholders interested in accessibility compliance.
Input Options
Report Output
The columns this report will output
Team
📊 Domain/URL Analysis
References
Please reference the Accessibility Testing Protocol document and the list of all URLs currently being tracked in our database. Additionally, Axe accessibility evaluation records will help substantiate this report.
The text was updated successfully, but these errors were encountered: