Skip to content
https://csmonitor.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <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
4 headings
REVIEW
4 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H4 Why is Christian Science in our name?
  • H2 Two ways to subscribe
  • H3 Deepen your worldview with Monitor Highlights.
  • H2 We have a new Single Sign On login system

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
Alt Text Quality
3 of 62 images have issues
REVIEW
3 of 62 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
48 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
62 images 11 good alt text 48 decorative 3 missing
IssueCount
missing3 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found - CSMonitor.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
h2 Two ways to subscrib…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We have a new Single…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deepen your worldvie…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 with21.00:13.0:1
#000000
#FFFFFF
Pass
title Christian Science Mo…4.56:14.5:1
#000000
#597897
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main menu21.00:14.5:1
#000000
#FFFFFF
Pass
button Skip to search21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to footer21.00:14.5:1
#000000
#FFFFFF
Pass
strong Why is Christian Sci…21.00:13.0:1
#000000
#FFFFFF
Pass
a Log in21.00:14.5:1
#000000
#FFFFFF
Pass
a Subscribe21.00:14.5:1
#000000
#FFFFFF
Pass
a Log out21.00:14.5:1
#000000
#FFFFFF
Pass
a USA21.00:14.5:1
#000000
#FFFFFF
Pass
a World21.00:14.5:1
#000000
#FFFFFF
Pass
a Editorials21.00:14.5:1
#000000
#FFFFFF
Pass
button The Home Forum21.00:14.5:1
#000000
#FFFFFF
Pass
a All Home Forum21.00:14.5:1
#000000
#FFFFFF
Pass
a A Christian Science …21.00:14.5:1
#000000
#FFFFFF
Pass
a Newsletters21.00:14.5: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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 26 passed
REVIEW
86

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
BEST DEAL div.row > div.ad > div > div.circle
ISSN 2573-3850 (online) body#body-tag > footer > div#issn
Follow us: body#body-tag > footer > div.footer-social-links > div.social-links-text
About div.footer-links > ul.footer-list > li > a
Contact Us div.footer-links > ul.footer-list > li > a
Subscribe div.footer-links > ul.footer-list > li > a
Give a Gift Subscription div.footer-links > ul.footer-list > li > a
Support Monitor Journalism div.footer-links > ul.footer-list > li > a
Free Newsletters div.footer-links > ul.footer-list > li > a
Careers div.footer-links > ul.footer-list > li > a
Social Media div.footer-links > ul.footer-list > li > a
Content Map div.footer-links > ul.footer-list > li > a
Text Edition div.footer-links > ul.footer-list > li > a
RSS div.footer-links > ul.footer-list > li > a
Reprints & Permissions div.footer-links > ul.footer-list > li > a
A Christian Science Perspective div.footer-links > ul.footer-list > li > a
© 1980–2026 The Christian Science Monitor. body#body-tag > footer > div.footer-copyright > a
All Rights Reserved. Terms. body#body-tag > footer > div.footer-copyright > a
Privacy Policy. body#body-tag > footer > div.footer-copyright > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.html-block > div.promo > div.promo-image > img div.html-block > div.promo > div.promo-image > img
div.html-block > div.promo > div.promo-image > img div.html-block > div.promo > div.promo-image > img
div.html-block > div.promo > div.promo-image > img div.html-block > div.promo > div.promo-image > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a
div.footer-social-links > ul.footer-list > li > a div.footer-social-links > ul.footer-list > li > a

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
© 1980–2026 The Christian Science Monitor. body#body-tag > footer > div.footer-copyright > a
All Rights Reserved. Terms. body#body-tag > footer > div.footer-copyright > a
Privacy Policy. body#body-tag > footer > div.footer-copyright > a

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
●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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●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
●Skip links are focusable.
●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
○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.
○`<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.
○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
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Skip links" MAIN ASIDE "Two ways to subscribe" CONTENTINFO footer
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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="submit" name="Submit">
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#main-menu-search-desktoptextSearchfor/id
#main-menu-searchtextSearchfor/id
emailemailYour email addressnone
Submitsubmit(none)none

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

<input type="submit" name="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

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

Send Feedback