Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

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-lue9u1

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://scotusblog.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://scotusblog.com/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

27 headings

REVIEW

27 headings

No H1 heading found

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

H2 SCOTUSblog’s new look
H3 Court to hear argument on law enforcement’s use of “geofence warrants”
H3 Opinions for Wednesday, April 22
H4 The emergency docket’s mistaken birthday
H4 Court appears skeptical of right to jury trial in FCC proceedings
H4 What the New York Times got wrong – and right – about the emergency docket
H4 A big day for SCOTUSblog
H2 Upcoming
H3 Opinions
H3 Arguments
H3 Conference
H3 Orders
H2 April Sitting
H3 Justices debate the relationship between state and federal courts
H4 Court appears skeptical of right to jury trial in FCC proceedings
H4 Justices seem receptive to SEC’s use of disgorgement in securities enforcement
H4 Court to consider rights of lawful permanent residents accused of committing a crime
H2 October Term 2025
H2 Latest from our authors
H3 Court to hear argument on law enforcement’s use of “geofence warrants”
H3 The Brazilian Federal Supreme Court
H3 A big day for SCOTUSblog
H3 Court adds two cases to 2026-27 docket
H3 Justices seem receptive to SEC’s use of disgorgement in securities enforcement
H3 “Universal” pre-K causes court to re-re-reconsider major religious precedent
H3 Trump attends birthright citizenship argument
H2 Welcome

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

5 <nav> landmark(s) found

1 of 5 <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+

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

11 image(s) with good alt text

11 images 11 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#_r_1_	text	First name *	for/id
#_r_2_	text	Last name *	for/id
#_r_3_	select	Job title (optional)	for/id
#_r_4_	text	Company (optional)	for/id

Link & Button Quality

119 links, 46 buttons — all OK

PASS

119 links, 46 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://www.scotusblog.com/interim-docket-blog/; https://www.scotusblog.com/interim-docket-blog/; https://akhilamar.com/podcast-2/; https://dividedargument.com/episodes/; https://akhilamar.com/podcast-2/; https://dividedargument.com/episodes/

113 link(s) with descriptive text

119 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.scotusblog.com/interim-docke…	Interim Docket Blog	new tab	Add '(opens in new tab)' to text
https://www.scotusblog.com/interim-docke…	Interim Docket Blog	new tab	Add '(opens in new tab)' to text
https://akhilamar.com/podcast-2/	Amarica's Constitution	new tab	Add '(opens in new tab)' to text
https://dividedargument.com/episodes/	Divided Argument	new tab	Add '(opens in new tab)' to text
https://akhilamar.com/podcast-2/	Amarica's Constitution	new tab	Add '(opens in new tab)' to text
https://dividedargument.com/episodes/	Divided Argument	new tab	Add '(opens in new tab)' to text

159 links and buttons have descriptive text

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

https://www.scotusblog.com/interim-docket-blog/; https://www.scotusblog.com/interim-docket-blog/; https://akhilamar.com/podcast-2/; https://dividedargument.com/episodes/; https://akhilamar.com/podcast-2/; https://dividedargument.com/episodes/

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

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
h2 SCOTUSblog’s new l…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Upcoming	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 April Sitting	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 October Term 2025	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Latest from our auth…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Welcome	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Court to hear argume…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Opinions for Wednesd…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Opinions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Arguments	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Conference	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Orders	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Justices debate the …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Court to hear argume…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Brazilian Federa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 A big day for SCOTUS…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Court adds two cases…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Justices seem recept…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 “Universal” pre-…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Trump attends birthr…	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, 30 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Creative Commons `div.content-width > div.flex > div.flex > span.size-[34px]`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of 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

●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

●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

●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

●Identical links have the same purpose.

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

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

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