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 3 REVIEW 2 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ 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

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: only light

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta only light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Navigation UX

Action

2 navigation pattern(s)

REVIEW

2 navigation pattern(s)

Search functionality detected

Got: role-search

Skip navigation link detected

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search role='search' landmark

Skip Link Skip link detected

Labeled Navigation 5 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA 6 pass AA only

h1 Home

1.40:1

#000000

#092940

needs 3.0:1 (large text)

32px · bottom of viewport · over background image/gradient

h2 Utility Menu

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Popular Topics

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h2 In the Spotlight

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From the Mountains to the Coast

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 nc.gov

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Us

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Network Menu

1.40:1

#000000

#092940

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Join Team North Carolina

1.40:1

#000000

#092940

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Celebrate America 250 NC

1.40:1

#000000

#092940

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Start Exploring NC Today

1.40:1

#000000

#092940

needs 3.0:1 (large text)

19px · bottom of viewport

span How you know

2.00:1

#000000

#553926

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

3 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)

Element	Ratio	Required	FG	BG	Result
h1 Home	1.40:1	3.0:1	#000000	#092940	Fail
h2 Utility Menu	5.04:1	3.0:1	#000000	#6B7F8C	Pass
h2 Utility Menu	1.40:1	3.0:1	#000000	#092940	Fail
h2 Popular Topics	1.40:1	3.0:1	#000000	#092940	Fail
h2 In the Spotlight	1.40:1	3.0:1	#000000	#092940	Fail
h2 From the Mountains t…	1.40:1	3.0:1	#000000	#092940	Fail
h2 nc.gov	1.40:1	3.0:1	#000000	#092940	Fail
h2 Contact Us	1.40:1	3.0:1	#000000	#092940	Fail
h2 Network Menu	1.40:1	3.0:1	#000000	#092940	Fail
h3 Join Team North Caro…	1.40:1	3.0:1	#000000	#092940	Fail
h3 Celebrate America 25…	1.40:1	3.0:1	#000000	#092940	Fail
h3 Start Exploring NC T…	1.40:1	3.0:1	#000000	#092940	Fail
title Home \| nc.gov	4.61:1	4.5:1	#000000	#C65200	Pass
a Skip to main content	4.61:1	4.5:1	#000000	#C65200	Pass
strong TAX SCAM ALERT	4.61:1	3.0:1	#000000	#C65200	Pass
p Beware of fake text …	4.61:1	4.5:1	#000000	#C65200	Pass
a Read more about prot…	4.61:1	4.5:1	#000000	#C65200	Pass
span An official website …	4.61:1	4.5:1	#000000	#C65200	Pass
span An official website …	4.61:1	4.5:1	#000000	#C65200	Pass
span How you know	2.00:1	4.5:1	#000000	#553926	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.

A+

Landmark Structure

12 landmarks

PASS

12 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Search landmark present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

15 headings

PASS

15 headings

Single H1 present

H2 Utility Menu
H2 Utility Menu
H1 Home
H2 Popular Topics
H2 In the Spotlight
H3 Join Team North Carolina
H3 Celebrate America 250 NC
H3 Start Exploring NC Today
H2 The Latest
H3 Governor Stein Announces Budget to Keep North Carolina Strong
H2 The Latest
H2 From the Mountains to the Coast
H2 nc.gov
H2 Contact Us
H2 Network Menu

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

3 decorative image(s) correctly marked

4 image(s) with good alt text

7 images 4 good alt text 3 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	language	aria-label
#edit-keys	search	Search	for/id
#search-button	submit	search	aria-label
#edit-keys	search	Search	for/id
#search-button	submit	search	aria-label

Link & Button Quality

1 issue(s) across 85 links and 5 buttons

PASS

1 issue(s) across 85 links and 5 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

84 link(s) with descriptive text

85 links

1 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/exploring	Start Exploring NC Today …	img no alt	Add alt attribute to the image

89 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

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 Page Not Found | nc.gov ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css_m0ZXrSNO79cNs_FXzXD7XhXSftGy5NwKJZWJolJ8DCE.css?delta=3&language=en&theme=nc_barrio&include=eJx9kOFuwyAMhF-IhEeKDDgJm8HINlvz9ou6rOkaqb-M7judfUBKxlA3D8djnIWrucBsagJtCiCS2c8s5aouxAFoUNso1-XKKyd0kQV95NK4YjUdX13DULD2i63GBwexHAmnCJLe-RSjZa5vLY2N8rLaO5Ph7eBJegMa4QNu_4SUgXhxe-vP1qWxoqccBGRzBXfo50yGMkZo94se4f5sH9OznnCGTjbZigWf9JcvPsFXxm-dzgI7AkIxf0x1DQSWfdOqf2efythr64GyrpicbmpYfABFd4_9DR8Lp074A6Lj1gk

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_m0ZXrSNO79cNs_FXzXD7XhXSftGy5NwKJZWJolJ8DCE.css?delta=3&language=en&theme=nc_barrio&include=eJx9kOFuwyAMhF-IhEeKDDgJm8HINlvz9ou6rOkaqb-M7judfUBKxlA3D8djnIWrucBsagJtCiCS2c8s5aouxAFoUNso1-XKKyd0kQV95NK4YjUdX13DULD2i63GBwexHAmnCJLe-RSjZa5vLY2N8rLaO5Ph7eBJegMa4QNu_4SUgXhxe-vP1qWxoqccBGRzBXfo50yGMkZo94se4f5sH9OznnCGTjbZigWf9JcvPsFXxm-dzgI7AkIxf0x1DQSWfdOqf2efythr64GyrpicbmpYfABFd4_9DR8Lp074A6Lj1gk ✓Inline @media print Not detected ✗

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 30 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
Read more about protecting your personal information `div#fc4494db2108dcc5ab54d55998b4b5aafb8035927fa130fd78480489b6ff35f0 > div.message > p > a.alert-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

●Input buttons have discernible text.

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

●Select elements have associated label elements.

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

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

○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 type="image">` elements have `[alt]` text

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

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

○Identical links have the same purpose.

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