Skip to content
https://virginia.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) 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
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #183055
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 ModePartial Dark Mode
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Virginia.gov
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Virginia.gov ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Virginia.gov Display Mode standalone Theme Color #183055 Background Color #183055 Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
h1 Virginia.gov
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Welcome to Virginia.gov
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 How can we help you?
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h2 Top Services
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Services & Resources
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Happening in Virginia
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your Government
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Commonwealth Calendar
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Join us in celebrating National Voluntee…
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Early season produce and garden-ready pl…
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Celebrate Virginia Culture and History
1.12:1
#000000
on
#03122A
needs 3.0:1 (large text)
19px · bottom of viewport
title Home | Virginia.gov
1.30:1
#000000
on
#212121
needs 4.5:1 (normal text)
16px · top of page (header area)
a Virginia.gov
1.48:1
#000000
on
#2A2B2B
needs 4.5:1 (normal text)
16px · top of page (header area)
span An official website of the Commonwealth …
1.81:1
#000000
on
#383939
needs 4.5:1 (normal text)
16px · top of page (header area)

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Virginia.gov1.12:13.0:1
#000000
#03122A
Fail
h1 Welcome to Virginia.…1.12:13.0:1
#000000
#03122A
Fail
h2 How can we help you?1.12:13.0:1
#000000
#03122A
Fail
h2 Top Services1.12:13.0:1
#000000
#03122A
Fail
h2 Services & Resources1.12:13.0:1
#000000
#03122A
Fail
h2 Happening in Virgini…1.12:13.0:1
#000000
#03122A
Fail
h2 Your Government1.12:13.0:1
#000000
#03122A
Fail
h2 Commonwealth Calenda…1.12:13.0:1
#000000
#03122A
Fail
h3 Join us in celebrati…1.12:13.0:1
#000000
#03122A
Fail
h3 Early season produce…1.12:13.0:1
#000000
#03122A
Fail
h3 Celebrate Virginia C…1.12:13.0:1
#000000
#03122A
Fail
title Home | Virginia.gov1.30:14.5:1
#000000
#212121
Fail
a Virginia.gov1.48:14.5:1
#000000
#2A2B2B
Fail
span An official website …1.81:14.5:1
#000000
#383939
Fail
a Here's how you know21.00:14.5:1
#000000
#FFFFFF
Pass
span An official website21.00:14.5:1
#000000
#FFFFFF
Pass
a Here's how you know21.00:14.5:1
#000000
#FFFFFF
Pass
span To ensure accurate s…20.82:14.5:1
#000000
#FEFEFE
Pass
button English20.82:14.5:1
#000000
#FEFEFE
Pass
span ▼20.82:14.5:1
#000000
#FEFEFE
Pass

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.

A
Heading Hierarchy
35 headings
PASS
35 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Virginia.gov
  • H1 Welcome to Virginia.gov duplicate H1
  • H2 How can we help you?
  • H2 Top Services
  • H2 Celebrate National Volunteer Week
  • H3 Join us in celebrating National Volunteer Week by giving back to your community, whether it's helping at a local food bank or cleaning up a state park. Visit Serve Virginia to find volunteer opportuni
  • H2 Services & Resources
  • H3 Business
  • H3 Economy
  • H3 Education
  • H3 Employment
  • H3 Environment & Natural Resources
  • H3 Family & Health
  • H3 Finance
  • H3 Government
  • H3 Licenses & Permits
  • H3 Public Safety
  • H3 Recreation & Culture
  • H3 Transportation
  • H2 Explore Virginia's Local Harvest
  • H3 Early season produce and garden-ready plants are popping up across Virginia. Use the Virginia Grown website to explore what's in season and find local farms, markets, and producers near you.
  • H2 Happening in Virginia
  • H3 Online Driver's License Renewals
  • H3 Reserve Your Cabin
  • H3 Find needed social services
  • H3 State Fraud, Waste & Abuse Hotline
  • H3 Celebrate Virginia Culture and History
  • H3 Month of November CelebrationNative American Heritage Month
  • H3 Month of February CelebrationBlack History Month
  • H3 Month of March CelebrationWomen's History Month
  • H2 Your Government
  • H3 GovernorAbigail Spanberger
  • H3 Lieutenant GovernorGhazala Hashmi
  • H3 Attorney GeneralJay Jones
  • H2 Commonwealth Calendar

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
16 image(s) with good alt text
17 images 16 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#js-vagov-searchinputSearch Virginia.govfor/id
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 25 passed
PASS
98

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

○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
●`[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
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback