Accessibility

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

No <nav> landmark found

No contentinfo (footer) landmark

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

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

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

C

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA

h2 Geospatial AI delivers deeper insights a…

1.48:1

#000000

on

#2B2B2B

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Esri builds ArcGIS, the world’s leadin…

1.48:1

#000000

on

#2B2B2B

needs 3.0:1 (large text)

24px · above the fold

h2 Who uses Esri technology?

1.65:1

#000000

on

#28324B

needs 3.0:1 (large text)

24px · mid-page

h3 ArcGIS overview

1.48:1

#000000

on

#2B2B2B

needs 3.0:1 (large text)

19px · above the fold

h3 What is GIS?

1.60:1

#000000

on

#2A2F4A

needs 3.0:1 (large text)

19px · above the fold

h3 About Esri

1.90:1

#000000

on

#283872

needs 3.0:1 (large text)

19px · above the fold

h3 Maps and analytics guide a $12 billion i…

1.48:1

#000000

on

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 GIS Software for Map…	5.32:1	3.0:1	#000000	#808080	Pass
h2 Geospatial AI delive…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h2 Esri builds ArcGIS, …	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h2 Who uses Esri techno…	1.65:1	3.0:1	#000000	#28324B	Fail
h2 Trending insights on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 New and newsworthy	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 ArcGIS overview	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 What is GIS?	1.60:1	3.0:1	#000000	#2A2F4A	Fail
h3 About Esri	1.90:1	3.0:1	#000000	#283872	Fail
h3 Maps and analytics g…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Designing and buildi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Mapping a critical l…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Inside Jackson Hole�…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How Virginia Beach t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A coveted metal for …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Don’t wait to migr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Esri and Amazon Web …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Transform how you th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Esri and Microsoft	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Learn how to combine…	21.00:1	3.0: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+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 GIS Software for Mapping and Spatial Analytics | Esri
H2 Geospatial AI delivers deeper insights at scale
H2 Esri builds ArcGIS, the world’s leading GIS mapping software.
H3 ArcGIS overview
H3 What is GIS?
H3 About Esri
H2 Who uses Esri technology?
H3 Maps and analytics guide a $12 billion investment in new homes
H3 Designing and building for a sustainable future
H3 Mapping a critical link between ebony trees and elephants
H2 Trending insights on the power of GIS technology
H3 Inside Jackson Hole’s mission to reduce avalanche risk
H3 How Virginia Beach transformed its emergency response platform
H3 A coveted metal for an electrified future
H2 New and newsworthy
H3 Don’t wait to migrate
H3 Esri and Amazon Web Services
H3 Transform how you think about energy
H3 Esri and Microsoft
H3 Learn how to combine imagery, GIS, and AI

A

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

3 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

11 image(s) with good alt text

15 images 11 good alt text 1 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

14 links, 2 buttons — all OK

PASS

14 links, 2 buttons — all OK

14 link(s) with descriptive text

14 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

16 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 28 passed

PASS

97

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search `div.gnav_top-nav_full-wrapper > div.gnav_top-nav_wrapper > nav.gnav_top-nav_navigation-internal-wrapper > ul.gnav_top-nav_user-actions-wrapper`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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

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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Elements with visible text labels have matching accessible names.

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

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

○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

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

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