Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Form Accessibility

Action

4 of 7 controls have issues

FIX

4 of 7 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="submit" name="op" id="edit-submit-desktop">; <input type="submit" name="op" id="edit-submit-mobile">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="query" id="query-desktop">; <input type="text" name="query" id="query-mobile">

3 control(s) properly labeled

7 controls

3 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#question_option_88294	radio	Yes	for/id
#question_option_88297	radio	No	for/id
#question_58160_answer_02	textarea	How could we improve this page?	for/id
#query-mobile	text	(Site Search)	placeholder only
#query-desktop	text	(Site Search)	placeholder only
#edit-submit-mobile	submit	(none)	none
#edit-submit-desktop	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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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.

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 ✗

Link & Button Quality

3 issue(s) across 250 links and 38 buttons

REVIEW

3 issue(s) across 250 links and 38 buttons

1 link(s) with no accessible text

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

Got: a#main-content

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /press-release/interior-generates-over-163-million-national-petroleum-reserve… ("Learn more"); /press-release/interior-generates-over-163-million-national-petroleum-reserve… ("Learn more")

1 link(s) open in new tab without warning

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

Got: https://touchpoints.digital.gov

246 link(s) with descriptive text

250 links

1 empty

2 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/press-release/interior-generates-over-1…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Interior Generates Over 163 Million National Petroleum Reserve Alaska Oil And Gas
/press-release/interior-generates-over-1…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Interior Generates Over 163 Million National Petroleum Reserve Alaska Oil And Gas
https://touchpoints.digital.gov	Touchpoints	new tab	Add '(opens in new tab)' to text

284 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

Generic link text like 'click here' doesn't describe the destination.

/press-release/interior-generates-over-163-million-national-petroleum-reserve… ("Learn more"); /press-release/interior-generates-over-163-million-national-petroleum-reserve… ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://touchpoints.digital.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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

13 icon(s) detected

REVIEW

13 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

Landmark Structure

22 landmarks

PASS

22 landmarks

<main> landmark present

7 <nav> landmark(s) found

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

Heading Hierarchy

42 headings

PASS

42 headings

Multiple H1 headings (12 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H2 Home
H1 Coal Leasing
H1 BLM launches new web tool to expand grazing opportunities and support healthier public lands duplicate H1
H1 Interior generates over $163 million from National Petroleum Reserve in Alaska oil and gas lease sale duplicate H1
H1 Celebrate Freedom 250 duplicate H1
H1 Energy and Minerals duplicate H1
H1 Coal Leasing duplicate H1
H1 BLM launches new web tool to expand grazing opportunities and support healthier public lands duplicate H1
H1 Interior generates over $163 million from National Petroleum Reserve in Alaska oil and gas lease sale duplicate H1
H1 Celebrate Freedom 250 duplicate H1
H1 Energy and Minerals duplicate H1
H1 Coal Leasing duplicate H1
H1 The Bureau of Land Management duplicate H1
H2 Spotlight News & Announcements
H2 Information Center
H2 Public Input & Actions
H3 BLM approves access road right-of-way
H3 BLM approves oil well drilling permit
H3 Burns District Office issues Skull 120 Route Change Categorical Exclusion
H2 Events & Meetings
H3 Apr 22: Earth Day event in Painted Canyon
H3 Apr 22: Canyons of the Ancients partners in clean-up event
H3 Apr 23 - Oct 17: BLM brings Oregon folklife programming to National Historic Oregon Trail Interpretive Center
H2 Press Releases
H3 BLM seeks initial input for December 2026 sale of oil and gas leases in Wyoming
H3 BLM launches Freedom 250 Volunteer Celebration
H3 BLM seeks input on proposed Castle Mountain Mine expansion in southern California
H2 Our Stories
H3 A Legacy in the Saddle: Three Riders, One Wild Beginning
H3 Stewardship partnerships protect irreplaceable cultural resources at Richardson Homestead in Arizona
H3 Students remove 300 pounds of invasive plants at Jupiter Inlet Lighthouse Outstanding Natural Area
H2 Quick Facts
H2 245
H2 97K
H2 30%
H2 $245.4
H2 Featured Places
H2 Featured Topics
H2 Popular Links
H2 Success
H2 Error
H2 Footer Utility

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

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

3 decorative image(s) correctly marked

37 image(s) with good alt text

40 images 37 good alt text 3 decorative

All images have appropriate alt text.

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 Coal Leasing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 BLM launches new web…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Interior generates o…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Celebrate Freedom 25…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Energy and Minerals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Coal Leasing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 BLM launches new web…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Interior generates o…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Celebrate Freedom 25…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Energy and Minerals	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Coal Leasing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 The Bureau of Land M…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Spotlight News & Ann…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Information Center	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick Facts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 245	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 97K	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 30%	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 $245.4	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured Places	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+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 29 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
Open Search `div#block-mobilesearchbutton-2 > div.field > p > a#mobile-search-button`

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

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○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

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