Skip to content
https://arkansas.gov

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Alt Text Quality
Action
6 of 60 images have issues
FIX
6 of 60 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
35 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
60 images 18 good alt text 35 decorative 6 missing
IssueCount
missing6 image(s)
too long1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
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 ✗
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" SEARCH 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

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
Navigation UX
Action
2 navigation pattern(s)
REVIEW
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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 Home
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Flag Status
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
32px · bottom of viewport
h2 What can we help you find?
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Welcome to the Natural State
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What can we help you find?
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Real ID
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Income Tax
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile ID
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find Your Next Opportunity
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Child Support
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Brighter Future
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Car Tag Renewal
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Birth Certificates
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Property Tax
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 AR ABLE
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular Services
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Find the Services right for you
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your Elected Officials
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Visit Arkansas
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Arkansas News
1.24:1
#000000
on
#0F1D32
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home1.24:13.0:1
#000000
#0F1D32
Fail
h1 Flag Status1.24:13.0:1
#000000
#0F1D32
Fail
h2 What can we help you…1.24:13.0:1
#000000
#0F1D32
Fail
h2 Welcome to the Natur…1.24:13.0:1
#000000
#0F1D32
Fail
h2 What can we help you…1.24:13.0:1
#000000
#0F1D32
Fail
h2 Real ID1.24:13.0:1
#000000
#0F1D32
Fail
h2 Income Tax1.24:13.0:1
#000000
#0F1D32
Fail
h2 Mobile ID1.24:13.0:1
#000000
#0F1D32
Fail
h2 Find Your Next Oppor…1.24:13.0:1
#000000
#0F1D32
Fail
h2 Child Support1.24:13.0:1
#000000
#0F1D32
Fail
h2 Brighter Future1.24:13.0:1
#000000
#0F1D32
Fail
h2 Car Tag Renewal1.24:13.0:1
#000000
#0F1D32
Fail
h2 Birth Certificates1.24:13.0:1
#000000
#0F1D32
Fail
h2 Property Tax1.24:13.0:1
#000000
#0F1D32
Fail
h2 AR ABLE1.24:13.0:1
#000000
#0F1D32
Fail
h2 Popular Services1.24:13.0:1
#000000
#0F1D32
Fail
h2 Find the Services ri…1.24:13.0:1
#000000
#0F1D32
Fail
h2 Your Elected Officia…1.24:13.0:1
#000000
#0F1D32
Fail
h2 Visit Arkansas1.24:13.0:1
#000000
#0F1D32
Fail
h2 Arkansas News1.24:13.0:1
#000000
#0F1D32
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
Heading Hierarchy
64 headings
PASS
64 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Government Resources
  • H2 Discover More
  • H3 Business Resources
  • H2 Discover More
  • H3 Residents Resources
  • H2 Discover More
  • H3 Visiting Resources
  • H2 Discover More
  • H2 What can we help you find?
  • H1 Home
  • H2 Welcome to the Natural State
  • H2 What can we help you find?
  • H2 Real ID
  • H2 Income Tax
  • H2 Mobile ID
  • H2 Find Your Next Opportunity
  • H2 Child Support
  • H2 Brighter Future
  • H2 Car Tag Renewal
  • H2 Birth Certificates
  • H2 Property Tax
  • H2 AR ABLE
  • H2 Popular Services
  • H2 Find the Services right for you
  • H2 Your Elected Officials
  • H2 Sarah Huckabee Sanders
  • H3 Leslie Rutledge
  • H3 Cole Jester
  • H3 Tim Griffin
  • H3 John Thurston
  • H3 Dennis Milligan
  • H3 Tommy Land
  • H2 Visit Arkansas
  • H3 view the latest
  • H2 Arkansas News
  • H3 Arkansas Century Farm Program Now Accepting 2026 Applications
  • H3 ASP TRAFFIC STOP ON I-57 LEADS TO SEIZURE OF 6 KILOS OF COCAINE
  • H3 ASP CID INVESTIGATING OFFICER-INVOLVED SHOOTING DEATHIN IZARD COUNTY
  • H3 ANNUAL ASP MEMORIAL SERVICE HONORING FALLEN TROOPERS SCHEDULED FOR MAY 6, 2026
  • H3 ASP, WEST MEMPHIS PD STOP SUSPECT FLEEING IN STOLEN AMBULANCE
  • H3 Lane Closure Scheduled on Highway 203 for Pipe Replacement
  • H2 Events
  • H3 Prompt Like a Pro
  • H3 Prompt Like a Pro
  • H3 Child Welfare Agency Review Board
  • H3 Child Welfare Agency Review Board
  • H3 Supervisory Appraiser/Trainee Appraiser Class
  • H3 Supervisory Appraiser/Trainee Appraiser Class
  • H3 Board Members to Attend 2026 NCEES Southern Zone Meeting
  • H3 Board Members to Attend 2026 NCEES Southern Zone Meeting
  • H3 Clinton – North Central Arkansas Career & Resource Fair
  • H3 Clinton – North Central Arkansas Career & Resource Fair
  • H3 Little Rock – Easterseals Hiring Event
  • H3 Little Rock – Easterseals Hiring Event
  • H2 visit us in
  • H2 The Natural State
  • H2 Discover More
  • H3 Was the information on this page helpful?
  • H3 Your Arkansas.gov
  • H3 Top Online Services
  • H3 helpful information
  • H2 Flag Status
  • H1 Flag Status duplicate H1
  • H2 (empty)

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#elementor-search-form-599ee39searchSearchfor/id
#elementor-search-form-47e1d186searchSearchfor/id
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 27 passed
PASS
92

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.

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
LEARN MORE div.elementor-repeater-item-1d0e337 > a.swiper-slide-inner > div.swiper-slide-contents > div.elementor-button
VISIT THE NATURAL STATE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
👍🏻 YES div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
👎🏻 NO div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Security Policy div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a
Transparency div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item > a

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 html

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
●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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○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.
○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