MeckNC accessibility content errors

WCAG 2.2 AA results from Acquia Web Governance for the Drupal sites on mecknc.gov, with shared template issues and documents (PDFs and Widen files) set aside. — of — sites have no content errors, and the top 4 sites hold — of the errors that remain.

—Drupal sites on mecknc.gov in scope
—Sites with content errors
—Content error instances (unique HTML snippets)
—Pages with content errors, of — scanned

Errors by type

High-severity errors first. Click an error to see which sites have it. An instance is one failing HTML snippet on one site; the same snippet can appear on several pages.

Error WCAG Severity Instances Pages Sites References

Sites

Sorted by content error instances. Several small sites were scanned on only a few pages, so a zero there means little was checked.

Site Instances Pages with errors Pages scanned Most common errors

Issue list

Every content error with an example page and the failing HTML. Click a site in the Sites panel to see only its issues, or filter by site, severity or any text.

— issues shown
No statuses marked yet

Mark each issue's status as you work. Statuses are saved in this browser only. When you're ready, export them and send the file to the report owner to update Web Governance.

Status Site Error Severity WCAG Pages Example page References Failing HTML

Set aside for the redesign

Markup that fails identically on 3 or more sites, a theme component that renders an empty element, or a social icon link (an SVG inside a link) with no accessible name, counts as template and is left out above. Errors from PDFs opened in the browser's PDF viewer, and from documents hosted on mecknc.widen.net, are also left out. These are documents rather than webpages and need fixing in the files themselves.

What Type Distinct snippets Sites

Snapshot exported from the Acquia Web Governance API on November 2, 2026. Download the data: sites, errors by type, issue list, set-aside items.