Skip to content
https://govdelivery.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Landmark Structure
Action
7 landmarks
FIX
7 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
Heading Hierarchy
Action
32 headings, 5 skip(s)
FIX
32 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Build meaningful connections with every digital interaction
  • H2 Every touchpoint has an impact
  • H3 Serve the whole community where they are, on their terms
  • H6 Learn how Manchester, CT, supercharged their community outreach by 100x using Government Experience Cloud skipped
  • H3 Grow your reach and expand your audience
  • H6 Learn how Veterans Affairs combined Engagement Cloud with GXG to grow subscriptions for critical communications skipped
  • H3 Digital services that deliver for the people
  • H6 Learn how Gainesville, FL, used Service Cloud to increase user satisfaction and employee experience skipped
  • H3 Understand what your community really wants
  • H6 See how Leamington, ON, used Engagement Cloud to understand their community and increase public transportation ridership skipped
  • H3 Do more with what you have
  • H6 Find out how Parachute, CO, used Operations Cloud to save time and money while reducing stress in the clerk’s office skipped
  • H2 Introducing the new AI-powered digital agent for smarter government experiences
  • H2 Innovating with technology
  • H2 Transforming engagement
  • H2 Serving critical communities
  • H2 Connecting everyone
  • H2 Data-driven insights for modern government
  • H3 2026 State of Digital Government Report
  • H3 Trends in public meetings report
  • H3 Trends in public communications report
  • H3 Trends in civic engagement report
  • H3 Trends in short-term rental market report
  • H3 Trends in public records request management report
  • H2 Discover, learn, share
  • H3 Unified = Unstoppable: Granicus Digital Government Award winners for “Total Government Experience”
  • H3 Changing is caring: Granicus Digital Government Award winners for “Changemaker”
  • H3 Websites that wow: Granicus Digital Government Award winners for “Website of the Year”
  • H3 Celebrating excellence in service delivery: Meet the Granicus Digital Government Award winners
  • H3 Blueprints for prize-worthy partnerships: Granicus Digital Government Award winners for “Community Engagement”
  • H3 Citizen-centric care: Granicus Digital Government Award winners for “Trust and Transparency”
  • H2 Ready to deliver exceptional outcomes?

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Granicus ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA
h1 Build meaningful connections with every …
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Every touchpoint has an impact
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing the new AI-powered digital a…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Innovating with technology
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Transforming engagement
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Serving critical communities
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Connecting everyone
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Data-driven insights for modern governme…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Discover, learn, share
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to deliver exceptional outcomes?
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Serve the whole community where they are…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Grow your reach and expand your audience
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Digital services that deliver for the pe…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Understand what your community really wa…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Do more with what you have
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 2026 State of Digital Government Report
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trends in public meetings report
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trends in public communications report
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trends in civic engagement report
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Trends in short-term rental market repor…
1.98:1
#000000
on
#800A20
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Build meaningful con…1.98:13.0:1
#000000
#800A20
Fail
h2 Every touchpoint has…1.98:13.0:1
#000000
#800A20
Fail
h2 Introducing the new …1.98:13.0:1
#000000
#800A20
Fail
h2 Innovating with tech…1.98:13.0:1
#000000
#800A20
Fail
h2 Transforming engagem…1.98:13.0:1
#000000
#800A20
Fail
h2 Serving critical com…1.98:13.0:1
#000000
#800A20
Fail
h2 Connecting everyone1.98:13.0:1
#000000
#800A20
Fail
h2 Data-driven insights…1.98:13.0:1
#000000
#800A20
Fail
h2 Discover, learn, sha…1.98:13.0:1
#000000
#800A20
Fail
h2 Ready to deliver exc…1.98:13.0:1
#000000
#800A20
Fail
h3 Serve the whole comm…1.98:13.0:1
#000000
#800A20
Fail
h3 Grow your reach and …1.98:13.0:1
#000000
#800A20
Fail
h3 Digital services tha…1.98:13.0:1
#000000
#800A20
Fail
h3 Understand what your…1.98:13.0:1
#000000
#800A20
Fail
h3 Do more with what yo…1.98:13.0:1
#000000
#800A20
Fail
h3 2026 State of Digita…1.98:13.0:1
#000000
#800A20
Fail
h3 Trends in public mee…1.98:13.0:1
#000000
#800A20
Fail
h3 Trends in public com…1.98:13.0:1
#000000
#800A20
Fail
h3 Trends in civic enga…1.98:13.0:1
#000000
#800A20
Fail
h3 Trends in short-term…1.98:13.0:1
#000000
#800A20
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 29 passed
REVIEW
88

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Play Video div.image-side > div.relative > div.relative-to-main-image > a.wistia

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy | Powered by: div.wrapper > div > div.footer > div.right
Privacy Policy div > div.footer > div.right > a#privacyPolicyAnchor
Powered by div > div.footer > div.right > label

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Government Experience Cloud p > span.TextRun > span.NormalTextRun > a
Privacy Policy div > div.footer > div.right > a#privacyPolicyAnchor

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div#pop-div2030245139835318113 > div#pop-div308486781072017022 > div#pop-frame016768391341691224 body.home > div#pop-div2030245139835318113 > div#pop-div308486781072017022 > div#pop-frame016768391341691224

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2026 Report: The State of Digital Government div.container > div.columns > div.column > a.hero-alert
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Alt Text Quality
All 127 images OK
PASS
All 127 images OK
Info::
11 image(s) with alt text over 125 characters
Info::
9 decorative image(s) correctly marked
Info::
107 image(s) with good alt text
127 images 107 good alt text 9 decorative
IssueCount
too long11 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectSelect Tabsaria-label
#footer-product-selectselectSelect a Productaria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback