Accessibility guide

WCAG Website Checklist

A WCAG website checklist helps teams review common accessibility patterns in a consistent way. It is most useful when it focuses on repeatable issue types such as text alternatives, contrast, labels, headings, keyboard access, and page structure.

What should a WCAG website checklist include?

CertScore.ai approaches this topic as a question of observable website signals. It helps teams surface structured findings and track change over time, but it does not provide legal advice or certification.

Why it matters

Teams often know accessibility matters but still struggle to turn broad standards into a practical review workflow.

A checklist helps reduce missed basics across templates, forms, navigation, and content-heavy pages.

It also makes it easier to compare scans over time after redesigns or CMS changes.

Common issues websites have

Checklist reviews often miss repeated patterns such as button contrast, heading order, alt text quality, and form labeling.

Teams may review a homepage closely while ignoring interior pages where service forms, blog templates, or ecommerce elements live.

Manual reviews become inconsistent when multiple people interpret the checklist differently.

Examples of problems

A site may pass a quick visual review while still failing keyboard navigation or label association checks.

A blog template may introduce contrast issues that do not appear on the homepage.

A contact workflow may use placeholder text instead of labels, creating repeated form-accessibility problems.

How automated scanning supports review

Automated scanning can check many of the technical signals that appear on a WCAG-oriented checklist, especially around semantics, labels, contrast, and structural markup.

It is useful for quickly identifying which checklist items recur across multiple public pages.

Automated scanning does not replace manual accessibility testing, but it helps teams start with a clearer issue map.

How CertScore.ai helps

CertScore.ai uses automated accessibility checks to surface repeatable WCAG-related issue patterns.

It groups those findings into structured signal summaries with issue counts and recurring categories.

That makes the checklist easier to operationalize across one site or a set of websites.

Use this guide as a checklist

Read the guide, then run a scan to see whether similar signals appear on a live site.

What the scan may surface here

The scan could flag repeated contrast issues, missing alt text, or unlabeled form inputs across public templates.

Use this guide, scan a website

Sample JSON

Sample finding JSON from scans

Representative payloads showing the structured evidence CertScore.ai can surface for this guide topic.

Representative accessibility barriers detected

accessibility_risk_score

Redacted illustrative example

{
  "example_type": "positive",
  "domain": "example.com",
  "requested_url": "https://example.com/",
  "final_url": "https://example.com/",
  "created_at": "2026-03-26T22:35:06.747Z",
  "scanned_at": "2026-03-26T22:35:52.641Z",
  "finding_id": "accessibility_risk_score",
  "finding_label": "Representative accessibility barriers detected",
  "section": "Accessibility",
  "evidenceConfidence": "good",
  "directVsInferred": "direct_observation",
  "evidence": {
    "counts": {
      "count": 1,
      "representativeAxeExampleCount": 1,
      "representativeAxePageCount": 1,
      "representativeAxeRuleCount": 1
    },
    "evidence_snippets": [
      "Axe example: color-contrast/color on https://example.com/; selector footer > p; nodes 1; impact Low-vision users may struggle to read text or distinguish controls.; severity high; help: Elements must meet minimum color contrast ratio thresholds.",
      "Representative axe examples: 1 rule across 1 page; max impact: Low-vision users may struggle to read text or distinguish controls.."
    ],
    "vendors": [],
    "request_domains": [],
    "request_samples": [],
    "cookie_samples": [],
    "consent_summary": {
      "preconsent_tracking_detected": false,
      "banner_present": false,
      "reject_all_present": false
    },
    "fingerprinting_or_device_signals": {
      "fingerprinting_vendor_detected": false,
      "device_signal_vendor_detected": null
    },
    "runtime_anchors": []
  },
  "coverage_flags": [
    "partial_scan",
    "blocked",
    "incomplete_pages"
  ],
  "known_limitations": [
    "Scan coverage issue: partial_scan",
    "Scan coverage issue: blocked",
    "Scan coverage issue: incomplete_pages"
  ],
  "selection_reason": "Surfaced finding with strong support. Mapped to executive finding accessibility_risk_score (good, direct). Evidence richness score: 9.",
  "evidenceVersion": "2.0",
  "scanContext": {
    "domain": "example.com",
    "requestedUrl": "https://example.com/",
    "finalUrl": "https://example.com/",
    "publicWebObservation": true,
    "legalConclusion": false
  },
  "artifacts": {
    "runtimeAnchors": [],
    "requestSamples": [],
    "cookieOrStorageSamples": [],
    "policyAnchors": [],
    "rawValuesRetained": false
  },
  "classification": {
    "section": "Accessibility",
    "criticality": "review",
    "evidenceConfidence": "good",
    "directVsInferred": "direct_observation",
    "legalStatusDetermined": false
  },
  "coverage": {
    "coverageFlags": [
      "partial_scan",
      "blocked",
      "incomplete_pages"
    ],
    "coverageReliableForTopRanking": false,
    "notDetectedMeans": "not_observed_in_scan_scope",
    "manualReviewNeeded": true
  },
  "topFindingCalibration": {
    "minimumToSurface": [
      "Retained evidence supports the finding under the canonical concern/policy/unified-finding pipeline."
    ],
    "highConfidenceRequires": [
      "Corroborated retained evidence and usable coverage."
    ],
    "criticalOrTopRankingRequires": [
      "Stronger directness, corroboration, affected surface, and review relevance."
    ],
    "demoteOrSuppressWhen": [
      "Evidence is ambiguous, unsupported, blocked, or audit-only."
    ]
  },
  "automationLimits": [
    "Automated public-web observations do not determine legal status, compliance status, proof that a law was breached, proof of data capture, or tracking lawfulness.",
    "Manual review is needed to confirm purpose, necessity, jurisdiction, configuration, exemptions, and remediation quality."
  ],
  "redaction": {
    "rawIdentifiersRetained": false,
    "storageValueContentsRetained": false,
    "completeQueryStringsRetained": false,
    "requestBodiesRetained": false,
    "renderedPageImagesRetained": false,
    "sourceMarkupRetained": false,
    "userEnteredValuesRetained": false
  },
  "selectionReason": "Surfaced finding with strong support. Mapped to executive finding accessibility_risk_score (good, direct). Evidence richness score: 9."
}

Summary for AI assistants

This CertScore.ai guide explains wcag website checklist as an observable public website signal for review. CertScore.ai scans public website behavior around tracking, cookies, consent, session recording indicators, fingerprinting-related signals, accessibility, and disclosures.

CertScore.ai findings are automated risk signals supported by retained evidence; they are not legal advice, certification, or compliance determinations.