Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Landmark Structure

18 landmarks

PASS

18 landmarks

<main> landmark present

5 <nav> landmark(s) found

1 of 5 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 Welcome to Maryland
H2 Discover all that Maryland offers
H3 Benefits
H3 Services
H3 Visit and explore
H2 Benefits for Marylanders
H2 Grow your career in Maryland
H2 Helping Maryland’s federal public servants
H2 What's happening in Maryland
H3 “Miles for Maryland” Trail Challenge
H3 MVA adds a new butterfly symbol to driver’s licenses
H3 Chesapeake Bay Legacy Act protects the Bay
H2 You deserve a getaway
H2 Your voice, your state: building a better tomorrow
H2 Explore Maryland.gov
H3 Top Benefits and Services
H3 Your Government
H3 Policies
H3 Stay Connected

A+

Alt Text Quality

All 16 images OK

PASS

All 16 images OK

3 decorative image(s) correctly marked

13 image(s) with good alt text

16 images 13 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#header-search-input	search	Search Maryland.gov	for/id
#mobile-search-input	text	Search Maryland.gov	for/id

Link & Button Quality

115 links, 16 buttons — all OK

PASS

115 links, 16 buttons — all OK

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://dnr.maryland.gov/publiclands/Pages/Miles-for-Maryland.aspx"]

114 link(s) with descriptive text

115 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://dnr.maryland.gov/publiclands/Pag…	- To commemorate the MARYLAND…	img no alt	Add alt attribute to the image

130 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://dnr.maryland.gov/publiclands/Pages/Miles-for-Maryland.aspx"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Lock ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Benefits for Marylan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Helping Maryland’s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What's happening in …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You deserve a getawa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your voice, your sta…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Explore Maryland.gov	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Benefits	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Visit and explore	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 “Miles for Marylan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 MVA adds a new butte…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Chesapeake Bay Legac…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Top Benefits and Ser…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Your Government	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Policies	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Stay Connected	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Maryland.gov	18.43:1	4.5:1	#000000	#F0F0F0	Pass
a Skip to main content	18.43:1	4.5:1	#000000	#F0F0F0	Pass
p An official website …	19.95:1	4.5:1	#000000	#F9F9F9	Pass
button Here’s how you kno…	21.00:1	4.5:1	#000000	#FFFFFF	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+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 26 passed

PASS

100

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.

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
“Miles for Maryland” Trail Challenge To commemorate the MARYLAND 250, Maryland… `section.maryland-visual-link-collection > ul.maryland-card-group > li.maryland-card > a.maryland-card__link`
MVA adds a new butterfly symbol to driver’s licenses The symbol supports peopl… `section.maryland-visual-link-collection > ul.maryland-card-group > li.maryland-card > a.maryland-card__link`
Chesapeake Bay Legacy Act protects the Bay The new law sets out to improve Bay… `section.maryland-visual-link-collection > ul.maryland-card-group > li.maryland-card > a.maryland-card__link`

○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

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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 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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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.

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.