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 1 REVIEW 4 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

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.

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

2 control(s) without accessible label

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

Got: <input type="image">; <input type="submit">

2 control(s) properly labeled

4 controls

2 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#q	text	Search:	for/id
#waveurl	url	Web site address:	for/id
input	image	(none)	none
input	submit	(none)	none

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

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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

1 empty heading(s)

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

H2 (empty)
H2 Main Navigation
H1 We have web accessibility in mind
H2 Accessibility Training
H2 Technical Assistance
H2 Accessibility in Procurement
H2 Evaluation and Reporting
H2 Community
H2 Current Features
H3 The WebAIM Million - 2026 Update
H3 Ask AIMee
H3 Global Digital Accessibility Salary Survey #2
H2 WebAIM Trainings
H2 ©2026 WebAIM
H2 Check Your Accessibility
H2 From the Blog
H2 Popular Resources

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+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Link & Button Quality

42 links, 1 buttons — all OK

PASS

42 links, 1 buttons — all OK

42 link(s) with descriptive text

42 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

43 links and buttons have descriptive text

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 WebAIM: Oh dear, that page cannot be found - Error 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /styles/print.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /styles/print.css ✓Inline @media print Not detected ✗

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
h1 We have web accessib…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Main Navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Current Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 WebAIM Trainings	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ©2026 WebAIM	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Check Your Accessibi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 From the Blog	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Popular Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The WebAIM Million -…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Ask AIMee	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Global Digital Acces…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title WebAIM: Web Accessib…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a skip to main content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Services	18.10:1	4.5:1	#000000	#EEEEEE	Pass
a Articles	17.78:1	4.5:1	#000000	#ECECEC	Pass
a Resources	17.78:1	4.5:1	#000000	#ECECEC	Pass
a Projects	17.62:1	4.5:1	#000000	#EBEBEB	Pass
a Community	14.31:1	4.5:1	#000000	#D6D5D2	Pass
label Search:	11.38:1	4.5:1	#000000	#C3BEB8	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 95/100 — 1 failing, 19 passed

PASS

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

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
services `nav > ul > li > a`
articles `nav > ul > li > a`
resources `nav > ul > li > a`
projects `nav > ul > li > a`
Contact `div#footerlinks > ul > li > a#footercontact`
About `div#footerlinks > ul > li > a#footerabout`
RSS Feeds `div#footerlinks > ul > li > a#footerrss`
LinkedIn `div#footerlinks > ul > li > a#footerli`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●`<input type="image">` elements have `[alt]` 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.

●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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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 use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

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

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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