For enterprises and public bodies: cities, counties, state and federal agencies

Sample report · Automated checks only

What a Docketward report contains.

This page shows a real report. It comes from a scan of section508.gov, a federal website, that we ran on 2026-10-15 and saved. Sample, automated checks only. It is not a statement about whether that site is compliant.

A staff member uses a braille display, keyboard and laptop to review a municipal website; the screen is out of focus.

The report is a PDF you can keep with your Title II plan records. It lists what failed the automated checks. The page-check section does not list every axe-core check that passed. PDF results show pass, fail or not checked. The report does not tell you your site is compliant. It also lists items the automated checks could not decide, marked “needs manual review”, and counts them as neither failures nor passes. This older sample comes from before we recorded those results, so its needs-review section says “not recorded”.

Sample report, section508.gov, 2026-10-15

Sample report available on request. A downloadable PDF package is not published on this site yet. Email support@docketward.com.

Report files

  • Sample report available on request. Email support@docketward.com.
  • A CSV file is not published on this site yet.

1. Scan summary

The top of the report names the site, the date and time of the scan, and what was checked: automated checks only, not a full manual WCAG audit. Then it shows the counts for this scan.

Site
www.section508.gov
Scanned
2026-10-15
Pages
40
PDFs
15
PDFs failing PDF/UA-1
14
PDFs not checked
not recorded in full: 1 PDF(s) could not be opened; PDFs over the plan PDF limit and PDFs on other hosts were not listed by this older scan
Links not fetched (page limit)
not recorded
Links
854 in scope = 555 with a result + 299 queued for next run
Broken links
1
Blocked
partial: 0 HTTP 401/403/429 recorded; robots.txt and WAF results not recorded
Spelling flags
7

2. Changes since the previous scan

The report compares this scan with the last scan of the same site. Each metric shows the previous count, the current count and the change. Below the table it lists new and fixed broken links, new unreachable links and links now reachable again, new and fixed PDF issues, changes to policy pages, and new and fixed spelling flags.

Changes since the previous scan, section508.gov
MetricPreviousNowChange
Pages crawled40400
Unique PDFs15150
PDF quick-check issues330
PDFs failing PDF/UA-114140
Broken links (HTTP 4xx/5xx)110
Images without alt (HTML check)000
Pages without lang (HTML check)000
Unlabeled inputs (HTML check)000
axe-core violation elements000
Pages without a title000
Titles over 60 characters770
Pages without a meta description440
Pages without exactly one H1330
Pages without a canonical link110
Pages without a viewport tag330

Current reports compare this scan with the previous one and list new, fixed and unchanged page-check items. Current reports list PDF links we did not check because the plan's PDF limit was reached, with the reason “over plan PDF limit (N)”. This older sample says “Not recorded: this older scan did not list PDF links beyond its PDF limit.” The report also lists the same-host links it found but did not fetch because the page limit was reached, with the file type when the link check saw it. The PDF shows the first 50; the CSV has all of them.

3. Page check failures

In current reports, this section names the axe-core version and the rule tags it ran, and how many crawled pages it tested. This older sample did not record the exact axe-core version, the rule tags it ran or some link outcomes (the unreachable-link split, and robots.txt and firewall blocks), and the report says “not recorded” for each. This sample scan crawled 40 pages and ran page checks on 3 of them, because it was an early, limited run. Current scans check every page they crawl. Failures are listed by axe-core rule, with its WCAG criterion, axe-core's impact rating, the number of pages and elements affected, and a link to the rule's help page. axe-core's “best practice” rules are not WCAG and do not appear here. The section also gives simple counts of images without alt text, pages without a language and unlabeled form inputs.

axe-core failures, section508.gov
RuleWCAG criterionImpactPagesElementsHelp
No violations.––00–

Reports made since 2026-10-30 also have a separate “Needs manual review” list (Rule · WCAG criterion · Status · Impact if confirmed · Pages · Elements · Help) for items axe-core could not decide. These are not counted as failures or as passes. In the 2026-10-15 sample, this section says the review results were not recorded. Current reports also list findings from WCAG 2.2-only rules in a separate group, “WCAG 2.2 (beyond Title II)”, outside the Title II count.

Many problems live in a template. One empty link in a header can appear on every page. Current reports include a ranked, grouped fix list with a short note on the usual fix for each item.

4. PDF check results

We run veraPDF on linked PDFs we can fetch, within your plan's PDF count and the 25 MB size limit. Files we cannot check are listed with the reason. Failing PDFs list the PDF/UA-1 rules they failed, by clause, with how many checks failed. Long lists are cut short. The PDF table shows up to 4 failed rules per PDF, then a line such as “3 more in the issue list below”. The issue list for each PDF shows up to 8 failed rules, those with the most failed checks; if there are more, current reports end the list with “N more failed PDF/UA-1 rule(s): listed in the CSV export”. In this older sample, one PDF's list ends with “1 more failed PDF/UA-1 rule(s) (1 failed checks): rule counted, detail not retained in this older scan”. Each PDF also shows whether it is tagged, its document language and title, and a plain reason for each quick-check failure, such as no document language. A PDF/UA-1 pass is not WCAG conformance, and a PDF/UA-1 failure on its own does not prove a WCAG failure.

https://www.section508.gov/~assets/files/2017_508-refresh-fact-sheet-updated.pdf

Pages
1
Tagged
Yes
Language
en-US
Title
2017 Accessibility Refresh Fact Sheet
Quick checks
Pass
veraPDF
FAIL (4 rules, 26 checks)
  • §7.18.1-2 ×12
  • §7.18.5-2 ×12
  • §5-1 ×1
  • §7.1-3 ×1

Planned: sort by folder, to find the agenda archive.

5. Broken links, likely misspellings and other site checks

These are not accessibility checks. They are on the same pages the public reads, so we include them.

Broken link

https://www.section508.gov/manage/laws-and-policies/Section-508-complaints-best-practices

404 linked from https://www.section508.gov/manage

Likely misspelling

“activties”

https://www.section508.gov/content-library

Policy pages

Accessibility statement

https://www.gsa.gov/website-information/accessibility-statement

Basic SEO counts

Missing title
0
Title >60 chars
7
Missing meta description
4
H1 count not 1
3
No canonical
1
No viewport
3
Duplicate titles
1

6. What this report does not cover

Docketward reports are automated scans only. They are not a certification, legal opinion, audit, or a guarantee of ADA or WCAG compliance. Results may miss issues that need manual review. This does not create an attorney-client relationship.

This report does not cover pages behind a login, pages not linked from the site or sitemap, content inside third-party embeds we are not allowed to load, or file types other than HTML and PDF. It does not judge whether alt text is meaningful, whether reading order makes sense, whether captions are accurate, or whether a form works by keyboard from start to finish.

Current reports include a “What automated checks cover” section. In the older sample on this site it is titled “Current scanner coverage, for reference”. Of the 50 WCAG 2.1 A and AA success criteria, 21 have at least one rule enabled in our scan configuration (axe-core 4.14.0) and 29 have none and need manual review. A criterion with a rule is not fully covered by it.

Planned additions

  • Dashboard with sign-in for everyone on your team
  • Planned: scheduled scans.

Get a report like this for your own site.

We confirm the scope with you before we run a sample scan. You receive a dated report package. It is not a certification.

Sample report · Automated checks only

What a Docketward report contains.

This page shows a real report. It comes from a scan of section508.gov, a federal website, that we ran on 2026-10-15 and saved. Sample, automated checks only. It is not a statement about whether that site is compliant.

A staff member uses a braille display, keyboard and laptop to review a municipal website; the screen is out of focus.

The report is a PDF you can keep with your Title II plan records. It lists what failed the automated checks. The page-check section does not list every axe-core check that passed. PDF results show pass, fail or not checked. The report does not tell you your site is compliant. It also lists items the automated checks could not decide, marked “needs manual review”, and counts them as neither failures nor passes. This older sample comes from before we recorded those results, so its needs-review section says “not recorded”.

Sample report available on request. A downloadable PDF package is not published on this site yet. Email support@docketward.com.

Report files

  • Sample report available on request. Email support@docketward.com.
  • A CSV file is not published on this site yet.

1. Scan summary

The top of the report names the site, the date and time of the scan, and what was checked: automated checks only, not a full manual WCAG audit. Then it shows the counts for this scan.

Site
www.section508.gov
Scanned
2026-10-15
Pages
40
PDFs
15
PDFs failing PDF/UA-1
14
PDFs not checked
not recorded in full: 1 PDF(s) could not be opened; PDFs over the plan PDF limit and PDFs on other hosts were not listed by this older scan
Links not fetched (page limit)
not recorded
Links
854 in scope = 555 with a result + 299 queued for next run
Broken links
1
Blocked
partial: 0 HTTP 401/403/429 recorded; robots.txt and WAF results not recorded
Spelling flags
7

2. Changes since the previous scan

The report compares this scan with the last scan of the same site. Each metric shows the previous count, the current count and the change. Below the table it lists new and fixed broken links, new unreachable links and links now reachable again, new and fixed PDF issues, changes to policy pages, and new and fixed spelling flags.

Changes since the previous scan, section508.gov

  • Pages crawled

    Previous
    40
    Now
    40
    Change
    0
  • Unique PDFs

    Previous
    15
    Now
    15
    Change
    0
  • PDF quick-check issues

    Previous
    3
    Now
    3
    Change
    0
  • PDFs failing PDF/UA-1

    Previous
    14
    Now
    14
    Change
    0
  • Broken links (HTTP 4xx/5xx)

    Previous
    1
    Now
    1
    Change
    0
  • Images without alt (HTML check)

    Previous
    0
    Now
    0
    Change
    0
  • Pages without lang (HTML check)

    Previous
    0
    Now
    0
    Change
    0
  • Unlabeled inputs (HTML check)

    Previous
    0
    Now
    0
    Change
    0
  • axe-core violation elements

    Previous
    0
    Now
    0
    Change
    0
  • Pages without a title

    Previous
    0
    Now
    0
    Change
    0
  • Titles over 60 characters

    Previous
    7
    Now
    7
    Change
    0
  • Pages without a meta description

    Previous
    4
    Now
    4
    Change
    0
  • Pages without exactly one H1

    Previous
    3
    Now
    3
    Change
    0
  • Pages without a canonical link

    Previous
    1
    Now
    1
    Change
    0
  • Pages without a viewport tag

    Previous
    3
    Now
    3
    Change
    0

Current reports compare this scan with the previous one and list new, fixed and unchanged page-check items. Current reports list PDF links we did not check because the plan's PDF limit was reached, with the reason “over plan PDF limit (N)”. This older sample says “Not recorded: this older scan did not list PDF links beyond its PDF limit.” The report also lists the same-host links it found but did not fetch because the page limit was reached, with the file type when the link check saw it. The PDF shows the first 50; the CSV has all of them.

3. Page check failures

In current reports, this section names the axe-core version and the rule tags it ran, and how many crawled pages it tested. This older sample did not record the exact axe-core version, the rule tags it ran or some link outcomes (the unreachable-link split, and robots.txt and firewall blocks), and the report says “not recorded” for each. This sample scan crawled 40 pages and ran page checks on 3 of them, because it was an early, limited run. Current scans check every page they crawl. Failures are listed by axe-core rule, with its WCAG criterion, axe-core's impact rating, the number of pages and elements affected, and a link to the rule's help page. axe-core's “best practice” rules are not WCAG and do not appear here. The section also gives simple counts of images without alt text, pages without a language and unlabeled form inputs.

axe-core failures, section508.gov

No violations. Pages 0 · Elements 0

Reports made since 2026-10-30 also have a separate “Needs manual review” list (Rule · WCAG criterion · Status · Impact if confirmed · Pages · Elements · Help) for items axe-core could not decide. These are not counted as failures or as passes. In the 2026-10-15 sample, this section says the review results were not recorded. Current reports also list findings from WCAG 2.2-only rules in a separate group, “WCAG 2.2 (beyond Title II)”, outside the Title II count.

Many problems live in a template. One empty link in a header can appear on every page. Current reports include a ranked, grouped fix list with a short note on the usual fix for each item.

4. PDF check results

We run veraPDF on linked PDFs we can fetch, within your plan's PDF count and the 25 MB size limit. Files we cannot check are listed with the reason. Failing PDFs list the PDF/UA-1 rules they failed, by clause, with how many checks failed. Long lists are cut short. The PDF table shows up to 4 failed rules per PDF, then a line such as “3 more in the issue list below”. The issue list for each PDF shows up to 8 failed rules, those with the most failed checks; if there are more, current reports end the list with “N more failed PDF/UA-1 rule(s): listed in the CSV export”. In this older sample, one PDF's list ends with “1 more failed PDF/UA-1 rule(s) (1 failed checks): rule counted, detail not retained in this older scan”. Each PDF also shows whether it is tagged, its document language and title, and a plain reason for each quick-check failure, such as no document language. A PDF/UA-1 pass is not WCAG conformance, and a PDF/UA-1 failure on its own does not prove a WCAG failure.

https://www.section508.gov/~assets/files/2017_508-refresh-fact-sheet-updated.pdf

Pages
1
Tagged
Yes
Language
en-US
Title
2017 Accessibility Refresh Fact Sheet
Quick checks
Pass
veraPDF
FAIL (4 rules, 26 checks)
  • §7.18.1-2 ×12
  • §7.18.5-2 ×12
  • §5-1 ×1
  • §7.1-3 ×1

Planned: sort by folder, to find the agenda archive.

5. Broken links, likely misspellings and other site checks

These are not accessibility checks. They are on the same pages the public reads, so we include them.

Broken link

https://www.section508.gov/manage/laws-and-policies/Section-508-complaints-best-practices

404 linked from https://www.section508.gov/manage

Likely misspelling

“activties”

https://www.section508.gov/content-library

Policy pages

Accessibility statement

https://www.gsa.gov/website-information/accessibility-statement

Basic SEO counts

Missing title
0
Title >60 chars
7
Missing meta description
4
H1 count not 1
3
No canonical
1
No viewport
3
Duplicate titles
1

6. What this report does not cover

Docketward reports are automated scans only. They are not a certification, legal opinion, audit, or a guarantee of ADA or WCAG compliance. Results may miss issues that need manual review. This does not create an attorney-client relationship.

This report does not cover pages behind a login, pages not linked from the site or sitemap, content inside third-party embeds we are not allowed to load, or file types other than HTML and PDF. It does not judge whether alt text is meaningful, whether reading order makes sense, whether captions are accurate, or whether a form works by keyboard from start to finish.

Current reports include a “What automated checks cover” section. In the older sample on this site it is titled “Current scanner coverage, for reference”. Of the 50 WCAG 2.1 A and AA success criteria, 21 have at least one rule enabled in our scan configuration (axe-core 4.14.0) and 29 have none and need manual review. A criterion with a rule is not fully covered by it.

Planned additions

  • Dashboard with sign-in for everyone on your team
  • Planned: scheduled scans.

Get a report like this for your own site.

We confirm the scope with you before we run a sample scan. You receive a dated report package. It is not a certification.

Questions about a rule or a report? Write to us.

Contact Docketward

Docketward checks against WCAG 2.0, 2.1 and 2.2 Level AA · Section 508 · the ADA Title II web rule · PDF/UA-1. Checks are automated and do not certify compliance.

Docketward

Docketward is a product of ADELOS, LLC, 21001 Pines Blvd, Pembroke Pines, FL 33029. Email support@docketward.com.

Docketward reports are automated scans only. They are not a certification, legal opinion, audit, or a guarantee of ADA or WCAG compliance. Results may miss issues that need manual review. This does not create an attorney-client relationship.

© 2026 ADELOS, LLC.

Sample Accessibility Scan Report | Docketward

Sample report · Automated checks only

What a Docketward report contains.

This page shows a real report. It comes from a scan of section508.gov, a federal website, that we ran on 2026-10-15 and saved. Sample, automated checks only. It is not a statement about whether that site is compliant.

{{ coverPic.alt }}

The report is a PDF you can keep with your Title II plan records. It lists what failed the automated checks. The page-check section does not list every axe-core check that passed. PDF results show pass, fail or not checked. The report does not tell you your site is compliant. It also lists items the automated checks could not decide, marked “needs manual review”, and counts them as neither failures nor passes. This older sample comes from before we recorded those results, so its needs-review section says “not recorded”.

Sample report, section508.gov, 2026-10-15

Sample report available on request. A downloadable PDF package is not published on this site yet. Email support@docketward.com.

Report files

  • Sample report available on request. Email support@docketward.com.
  • A CSV file is not published on this site yet.

1. Scan summary

The top of the report names the site, the date and time of the scan, and what was checked: automated checks only, not a full manual WCAG audit. Then it shows the counts for this scan.

{{ s.k }}
{{ s.v }}{{ s.v }}

2. Changes since the previous scan

The report compares this scan with the last scan of the same site. Each metric shows the previous count, the current count and the change. Below the table it lists new and fixed broken links, new unreachable links and links now reachable again, new and fixed PDF issues, changes to policy pages, and new and fixed spelling flags.

Changes since the previous scan, section508.gov
MetricPreviousNowChange
{{ r.k }}{{ r.prev }}{{ r.now }}{{ r.chg }}

Changes since the previous scan, section508.gov

  • {{ r.k }}

    Previous
    {{ r.prev }}
    Now
    {{ r.now }}
    Change
    {{ r.chg }}

Current reports compare this scan with the previous one and list new, fixed and unchanged page-check items. Current reports list PDF links we did not check because the plan's PDF limit was reached, with the reason “over plan PDF limit (N)”. This older sample says “Not recorded: this older scan did not list PDF links beyond its PDF limit.” The report also lists the same-host links it found but did not fetch because the page limit was reached, with the file type when the link check saw it. The PDF shows the first 50; the CSV has all of them.

3. Page check failures

In current reports, this section names the axe-core version and the rule tags it ran, and how many crawled pages it tested. This older sample did not record the exact axe-core version, the rule tags it ran or some link outcomes (the unreachable-link split, and robots.txt and firewall blocks), and the report says “not recorded” for each. This sample scan crawled 40 pages and ran page checks on 3 of them, because it was an early, limited run. Current scans check every page they crawl. Failures are listed by axe-core rule, with its WCAG criterion, axe-core's impact rating, the number of pages and elements affected, and a link to the rule's help page. axe-core's “best practice” rules are not WCAG and do not appear here. The section also gives simple counts of images without alt text, pages without a language and unlabeled form inputs.

axe-core failures, section508.gov
RuleWCAG criterionImpactPagesElementsHelp
No violations.––00–

axe-core failures, section508.gov

No violations. Pages 0 · Elements 0

Reports made since 2026-10-30 also have a separate “Needs manual review” list (Rule · WCAG criterion · Status · Impact if confirmed · Pages · Elements · Help) for items axe-core could not decide. These are not counted as failures or as passes. In the 2026-10-15 sample, this section says the review results were not recorded. Current reports also list findings from WCAG 2.2-only rules in a separate group, “WCAG 2.2 (beyond Title II)”, outside the Title II count.

Many problems live in a template. One empty link in a header can appear on every page. Current reports include a ranked, grouped fix list with a short note on the usual fix for each item.

4. PDF check results

We run veraPDF on linked PDFs we can fetch, within your plan's PDF count and the 25 MB size limit. Files we cannot check are listed with the reason. Failing PDFs list the PDF/UA-1 rules they failed, by clause, with how many checks failed. Long lists are cut short. The PDF table shows up to 4 failed rules per PDF, then a line such as “3 more in the issue list below”. The issue list for each PDF shows up to 8 failed rules, those with the most failed checks; if there are more, current reports end the list with “N more failed PDF/UA-1 rule(s): listed in the CSV export”. In this older sample, one PDF's list ends with “1 more failed PDF/UA-1 rule(s) (1 failed checks): rule counted, detail not retained in this older scan”. Each PDF also shows whether it is tagged, its document language and title, and a plain reason for each quick-check failure, such as no document language. A PDF/UA-1 pass is not WCAG conformance, and a PDF/UA-1 failure on its own does not prove a WCAG failure.

https://www.section508.gov/~assets/files/2017_508-refresh-fact-sheet-updated.pdf

Pages
1
Tagged
Yes
Language
en-US
Title
2017 Accessibility Refresh Fact Sheet
Quick checks
Pass
veraPDF
FAIL (4 rules, 26 checks)
  • §7.18.1-2 ×12
  • §7.18.5-2 ×12
  • §5-1 ×1
  • §7.1-3 ×1

Planned: sort by folder, to find the agenda archive.

5. Broken links, likely misspellings and other site checks

These are not accessibility checks. They are on the same pages the public reads, so we include them.

Broken link

https://www.section508.gov/manage/laws-and-policies/Section-508-complaints-best-practices

404 linked from https://www.section508.gov/manage

Likely misspelling

“activties”

https://www.section508.gov/content-library

Policy pages

Accessibility statement

https://www.gsa.gov/website-information/accessibility-statement

Basic SEO counts

{{ s.k }}
{{ s.v }}

6. What this report does not cover

Docketward reports are automated scans only. They are not a certification, legal opinion, audit, or a guarantee of ADA or WCAG compliance. Results may miss issues that need manual review. This does not create an attorney-client relationship.

This report does not cover pages behind a login, pages not linked from the site or sitemap, content inside third-party embeds we are not allowed to load, or file types other than HTML and PDF. It does not judge whether alt text is meaningful, whether reading order makes sense, whether captions are accurate, or whether a form works by keyboard from start to finish.

Current reports include a “What automated checks cover” section. In the older sample on this site it is titled “Current scanner coverage, for reference”. Of the 50 WCAG 2.1 A and AA success criteria, 21 have at least one rule enabled in our scan configuration (axe-core 4.14.0) and 29 have none and need manual review. A criterion with a rule is not fully covered by it.

Planned additions

  • Dashboard with sign-in for everyone on your team
  • Planned: scheduled scans.