Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 4 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email" id="email0">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="email0">

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-u3znox

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.myhealth.va.gov/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.myhealth.va.gov/manifest.json

Manifest contains invalid JSON.

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 ✗

Heading Hierarchy

Action

9 headings, 1 skip(s)

REVIEW

9 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H5 The .gov means it's official.
H5 The site is secure.
H4 My HealtheVet has moved to VA.gov
H2 In the Spotlight
H4 VA Resources skipped
H4 Policies
H4 Important Links
H3 Subscribe to Receive My HealtheVet Updates
H3 We're here anytime, day or night - 24/7

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

1 issue(s) across 34 links and 12 buttons

REVIEW

1 issue(s) across 34 links and 12 buttons

1 link(s) with no accessible text

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

Got: a (#208 on page)

9 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.va.gov/; https://vacareers.va.gov/; https://www.va.gov/find-forms/; https://www.va.gov/privacy-policy/ ; https://www.va.gov/terms-of-use; https://digital.va.gov/web-governance/standards-and-policies/web-policies/; https://www.va.gov/find-locations/; https://mobile.va.gov/appstore?filter%5Bapp_audience%5D=25; https://www.whitehouse.gov/

24 link(s) with descriptive text

34 links

1 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.va.gov/	VA Home	new tab	Add '(opens in new tab)' to text
https://vacareers.va.gov/	Careers at VA	new tab	Add '(opens in new tab)' to text
https://www.va.gov/find-forms/	Find a VA Form	new tab	Add '(opens in new tab)' to text
https://www.va.gov/privacy-policy/	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.va.gov/terms-of-use	Terms & Conditions	new tab	Add '(opens in new tab)' to text
https://digital.va.gov/web-governance/st…	Web Policies	new tab	Add '(opens in new tab)' to text
https://www.va.gov/find-locations/	Facility and Service Locator	new tab	Add '(opens in new tab)' to text
https://mobile.va.gov/appstore?filter%5B…	Mobile Apps	new tab	Add '(opens in new tab)' to text
https://www.whitehouse.gov/	White House	new tab	Add '(opens in new tab)' to text

36 links and buttons have descriptive text

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

a (#208 on page)

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

Add '(opens in new tab)' to link text or aria-label.

https://www.va.gov/; https://vacareers.va.gov/; https://www.va.gov/find-forms/; https://www.va.gov/privacy-policy/ ; https://www.va.gov/terms-of-use; https://digital.va.gov/web-governance/standards-and-policies/web-policies/; https://www.va.gov/find-locations/; https://mobile.va.gov/appstore?filter%5Bapp_audience%5D=25; https://www.whitehouse.gov/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

10 icon(s) detected

REVIEW

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA 1 pass AA only

p An official website of the United States…

1.81:1

#000000

#622332

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span Here's how you know

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · above the fold

p ensures that you're …

4.09:1

#000000

#0071BC

needs 4.5:1 (normal text)

16px · above the fold

span Talk to the

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · above the fold

strong Veterans Crisis Line

1.53:1

#000000

#112E51

needs 3.0:1 (large text)

16px · above the fold

span now

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

span My HealtheVet

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

button Menu

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

span Search

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

label Search:

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

span Search

1.53:1

#000000

#112E51

needs 4.5:1 (normal text)

16px · mid-page

1 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
h2 In the Spotlight	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Subscribe to Receive…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 We're here anytime, …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Home - My HealtheVet…	18.59:1	4.5:1	#000000	#F1F1F1	Pass
a Skip to Content	18.59:1	4.5:1	#000000	#F1F1F1	Pass
div An issue has occurre…	8.77:1	4.5:1	#000000	#CD9B9D	Pass
p An official website …	1.81:1	4.5:1	#000000	#622332	Fail
span Here's how you know	1.53:1	4.5:1	#000000	#112E51	Fail
p Federal government w…	17.71:1	4.5:1	#000000	#E9ECEF	Pass
p The	17.71:1	4.5:1	#000000	#E9ECEF	Pass
strong https://	4.09:1	3.0:1	#000000	#0071BC	Pass
p ensures that you're …	4.09:1	4.5:1	#000000	#0071BC	Fail
span Talk to the	1.53:1	4.5:1	#000000	#112E51	Fail
strong Veterans Crisis Line	1.53:1	3.0:1	#000000	#112E51	Fail
span now	1.53:1	4.5:1	#000000	#112E51	Fail
span My HealtheVet	1.53:1	4.5:1	#000000	#112E51	Fail
button Menu	1.53:1	4.5:1	#000000	#112E51	Fail
span Search	1.53:1	4.5:1	#000000	#112E51	Fail
label Search:	1.53:1	4.5:1	#000000	#112E51	Fail
span Search	1.53:1	4.5:1	#000000	#112E51	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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 Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

4 decorative image(s) correctly marked

2 image(s) with good alt text

6 images 2 good alt text 4 decorative

All images have appropriate alt text.

Form Accessibility

1 of 4 controls have issues

PASS

1 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit" name="commit">

3 control(s) properly labeled

4 controls

3 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#_com_liferay_portal_search_web_portlet_SearchPortlet_keywords2	text	Search:	for/id
#_com_liferay_portal_search_web_portlet_SearchPortlet_keywords	text	Search:	for/id
#email0	email	Your email address	for/id
commit	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

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

Input "query" should use type="search" (currently type="text")

Field name "query" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

4 form control(s) checked, no input-semantic issues

PASS

4 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

8 explicit tabindex attribute(s) checked, no anti-patterns

PASS

8 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 39 visible text node(s) render at >= 12 CSS pixels

PASS

All 39 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 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.

○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

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

●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

●Elements with visible text labels have matching accessible names.

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

○Image elements have `[alt]` attributes

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

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