Skip to content
https://compuserve.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

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-h1ygkn
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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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 Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://compuserve.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://compuserve.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
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
14 headings
REVIEW
14 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 News
  • H4 Chemical leak at a West Virginia plant kills 2 people and sends 19 more to hospital, officials say
  • H3 World
  • H4 Iran fires on 3 ships in the Strait of Hormuz as US maintains blockade and diplomacy stalls
  • H3 Business
  • H4 The Iran war could drive up costs for petroleum-derived products like clothes and crayons
  • H3 Weather
  • H3 Pop Culture
  • H4 Inside the Kennedy Center as it prepares for a 2-year renovation
  • H3 Sports
  • H4 Road teams pushing back in early days of NBA playoffs, stealing away the home-court advantages
  • H3 Member Center
  • H3 Channels
  • H3 Tools

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

C
Form Accessibility
Action
4 of 4 controls have issues
REVIEW
4 of 4 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q" id="hdrSrchText">; <input type="submit" id="hdrSrchBtn">; <input type="text" name="q">; <input type="submit">
4 controls
0 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#hdrSrchTexttext(none)none
#hdrSrchBtnsubmit(none)none
qtext(none)none
inputsubmit(none)none

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

<input type="text" name="q" id="hdrSrchText">; <input type="submit" id="hdrSrchBtn">; <input type="text" name="q">; <input type="submit">

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

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 News7.39:13.0:1
#000000
#43A1DE
Pass
h3 World21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Business21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Weather21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pop Culture21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sports21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Member Center21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Channels21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Tools21.00:13.0:1
#000000
#FFFFFF
Pass
title CompuServe.com - Hom…5.61:14.5:1
#000000
#2789D3
Pass
a Chemical leak at a W…9.70:14.5:1
#000000
#61BAE8
Pass
a Authorities say a ch…14.10:14.5:1
#000000
#AFDAEF
Pass
a Celeste Rivas Hernan…19.96:14.5:1
#000000
#F4FAFF
Pass
a Wildfires across Geo…10.56:14.5:1
#000000
#86BEE9
Pass
a Heavy rain and snowm…15.54:14.5:1
#000000
#D3DFEC
Pass
a Democrats win in Vir…12.55:14.5:1
#000000
#B7CAE1
Pass
a Searchers find the b…11.13:14.5:1
#000000
#A8BFDA
Pass
a Immigration officer …16.81:14.5:1
#000000
#DEE7F1
Pass
a Climate doom and glo…21.00:14.5:1
#000000
#FFFFFF
Pass
a More kids than ever …19.90:14.5:1
#000000
#F7F9FB
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 3 failing, 12 passed
REVIEW
83

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Enter City or Zip: div.tileOutline > div.wxWrapper > form > p.input
Member Center div#main > div#nav > div.menuBlk > h3.menu
My Account div.menuBlk > ul > li > a
About CompuServe div.menuBlk > ul > li > a
Get Help div.menuBlk > ul > li > a
Channels div#main > div#nav > div.menuBlk > h3.menu
Autos div.menuBlk > ul > li > a
Careers div.menuBlk > ul > li > a
Entertainment div.menuBlk > ul > li > a
Fun & Games div.menuBlk > ul > li > a
Gadgets & Tech div.menuBlk > ul > li > a
Home & Living div.menuBlk > ul > li > a
Money & Business div.menuBlk > ul > li > a
News div.menuBlk > ul > li > a
Shopping div.menuBlk > ul > li > a
Sports div.menuBlk > ul > li > a
Travel div.menuBlk > ul > li > a
Weather div.menuBlk > ul > li > a
Tools div#main > div#nav > div.menuBlk > h3.menu
Maps div.menuBlk > ul > li > a
Search div.menuBlk > ul > li > a
Look for a Job div.menuBlk > ul > li > a

These are opportunities to improve the legibility of your content.

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
EU close to approving a $106B loan for Ukraine after months of deadlock div.tileOutline > ul > li > a
Ukraine wants a Zelenskyy-Putin summit to jolt stalled US-led peace efforts div.tileOutline > ul > li > a
EU close to approving a $106B loan for Ukraine after months of deadlock div.tileOutline > ul > li > a
UK inflation rises as prices at the pump spike after Iran war div.tileOutline > ul > li > a
Terms of Service div#cpyrText > ul#ftLnks > li > a
Privacy Policy div#cpyrText > ul#ftLnks > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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>`
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●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
●Identical links have the same purpose.
○`[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
○Deprecated ARIA roles were not used
○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
○`[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
○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.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
1 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
9 images 8 good alt text 1 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback