Skip to content
https://onlamp.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-bcyfuk
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://onlamp.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://onlamp.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Heading Hierarchy
48 headings
REVIEW
48 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Explore Skills
  • H3 Cloud Computing
  • H3 Data Engineering
  • H3 Data Science
  • H3 AI & ML
  • H3 Programming Languages
  • H3 Software Architecture
  • H3 IT/Ops
  • H3 Security
  • H3 Design
  • H3 Business
  • H3 Soft Skills
  • H3 Features
  • H2 Dark Factories: Rise of the Trycycle
  • H2 Scenario Planning for AI and the “Jobless Future”
  • H2 Trial by Fire: Crisis Engineering
  • H2 Generative AI in the Real World: Aishwarya Naresh Reganti on Making AI Work in Production
  • H2 Meet the Scope Creep Kraken
  • H2 AI Is Writing Our Code Faster Than We Can Verify It
  • H2 Grief and the Nonprofessional Programmer
  • H2 Comprehension Debt: The Hidden Cost of AI-Generated Code
  • H2 Agents don’t know what good looks like. And that’s exactly the problem.
  • H2 Fireside Chat with Sam Newman and Neal Ford
  • H2 It’s Not Vibe Coding If You Know What You’re Doing with Jeff Blankenburg
  • H2 Architecture as Code to Teach Humans and Agents About Architecture
  • H2 eBPF and the Future of Runtime Security - In Conversation: Liz Rice and Andrew Martin
  • H2 AI-Infused Development Needs More Than Prompts
  • H2 Posthuman: We All Built Agents. Nobody Built HR.
  • H2 The World Needs More Software Engineers
  • H2 Box’s Strategic Pivot from Content to Context
  • H2 Radar Trends to Watch: April 2026
  • H2 Context Is the Entire Ballgame for Enterprise Agents
  • H2 Try the O’Reilly learning platform
  • H2 Try a course for free
  • H2 Get the Radar Trends newsletter
  • H2 Thank you for subscribing to the O’Reilly Radar Trends to Watch newsletter.
  • H2 About O'Reilly
  • H2 Support
  • H2 International
  • H2 Download the O'Reilly App
  • H2 Watch on Your Big Screen
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Vendors List

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

B
Form Accessibility
2 of 11 controls have issues
REVIEW
2 of 11 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="range">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">
Info::
9 control(s) properly labeled
11 controls
9 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
qsearchSearch for books, courses, events, and morenone
qsearchSearch for books, courses, events, and morenone
#emailaddressemailYour emailfor/id
#countryselectCountryfor/id
#vendor-search-handlertextVendor list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
ssearch(Search)placeholder only
inputrange(none)none

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

<input type="range">

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.

<input type="search" name="s">

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 26 passed
REVIEW
89

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
AI assistant body.home > q-focus-sentinel > div
After AI assistant body.home > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

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.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.item-text > div.audioPlayer-controls > div.player-bars > input.seek-bar div.item-text > div.audioPlayer-controls > div.player-bars > input.seek-bar

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Play div.inner > div.item-text > div.audioPlayer-controls > button.btn
div.item-text > div.audioPlayer-controls > div.player-bars > input.seek-bar div.item-text > div.audioPlayer-controls > div.player-bars > input.seek-bar

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
●`[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.
●Select elements have associated label elements.
●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
●`<frame>` or `<iframe>` elements have a title
●`<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
●Identical links have the same purpose.
○`[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
○`<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
○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.
○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.
A
Landmark Structure
47 landmarks
PASS
47 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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
1 of 27 images have issues
PASS
1 of 27 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
19 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
27 images 7 good alt text 19 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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)
ElementRatioRequiredFGBGResult
h2 Dark Factories: Rise…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scenario Planning fo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trial by Fire: Crisi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Generative AI in the…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet the Scope Creep…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI Is Writing Our Co…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Grief and the Nonpro…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Comprehension Debt: …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Agents don’t know …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Fireside Chat with S…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 It’s Not Vibe Codi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Architecture as Code…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 eBPF and the Future …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AI-Infused Developme…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Posthuman: We All Bu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The World Needs More…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Box’s Strategic Pi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Radar Trends to Watc…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Context Is the Entir…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Try the O’Reilly l…21.00:13.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback