Skip to content
https://universetoday.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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 Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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

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

B
Heading Hierarchy
20 headings
REVIEW
20 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 MSL Curiosity Found New Organic Chemicals On Mars, Proof That The Planet Can Preserve Ancient Biosignatures
  • H2 Tracking Changes in the Trifid Nebula With the Hubble
  • H2 Mars Didn't Have Bathtubs, It Had Shelves
  • H2 Stellar Flares May Expand Habitable Zones Around Small Stars
  • H2 Scientists Connect Sub-extreme Solar Outbursts to Tree Rings via Poetry
  • H2 Which Types of Civilizations Collapse and Which Can Endure?
  • H2 China Unveils a Massive 5-Meter Composite Module for its Next-Generation Reusable Rocket
  • H2 Behold, the Solar System in All its X-ray Glory
  • H2 Exoplanets Without Lots of Water Can't Maintain Their Carbon Cycles
  • H2 NASA’s SPHEREx Telescope Just Mapped the Cosmic Ices That Will Someday Build Planets
  • H2 The Vera C. Rubin Observatory has Discovered 11,000 New Asteroids, and It's Barely Even Started!
  • H2 What Happens When Light Goes Boom? Part 4: What Brad Bradington Is Good For
  • H2 "Immature" Lunar Soil Could Be Suitable for Roadways on the Moon
  • H2 What Happens When Light Goes Boom? Part 3: Brad Bradington Sprints
  • H2 How a Black Hole and a Shredded Star Could Light Up a Galaxy
  • H2 Small Trojan Asteroids Defy Expectations
  • H2 Life Beyond Biosignatures: A New Method In The Search For Life
  • H2 Comet R3 PanSTARRS at Perihelion
  • H2 To Survive Deep Space, Astronauts May Owe a Debt to Microscopic Worms
  • H2 Watch This Dark Volcanic Ash Creep Across the Red Planet

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
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 Page Not Found - Universe Today ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Alt Text Quality
All 21 images OK
PASS
All 21 images OK
Info::
20 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
21 images 1 good alt text 20 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(Search...)placeholder only

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

<input type="text" name="q">

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

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
title Universe Today - Spa…21.00:14.5:1
#000000
#FFFFFF
Pass
a Universe Today21.00:14.5:1
#000000
#FFFFFF
Pass
a Home21.00:14.5:1
#000000
#FFFFFF
Pass
a Videos21.00:14.5:1
#000000
#FFFFFF
Pass
a Podcast21.00:14.5:1
#000000
#FFFFFF
Pass
a Newsletter21.00:14.5:1
#000000
#FFFFFF
Pass
a Join the Club21.00:14.5:1
#000000
#FFFFFF
Pass
a RSS Feed21.00:14.5:1
#000000
#FFFFFF
Pass
a MSL Curiosity Found …21.00:14.5:1
#000000
#FFFFFF
Pass
a Evan Gough21.00:14.5:1
#000000
#FFFFFF
Pass
span - April 22, 2026 06:…21.00:14.5:1
#000000
#FFFFFF
Pass
a Astrobiology21.00:14.5:1
#000000
#FFFFFF
Pass
div MSL Curiosity found …21.00:14.5:1
#000000
#FFFFFF
Pass
a Continue reading21.00:14.5:1
#000000
#FFFFFF
Pass
a Tracking Changes in …21.00:14.5:1
#000000
#FFFFFF
Pass
a Evan Gough21.00:14.5:1
#000000
#FFFFFF
Pass
span - April 22, 2026 02:…21.00:14.5:1
#000000
#FFFFFF
Pass
a Stars21.00:14.5:1
#000000
#FFFFFF
Pass
div Back in 1997, the Hu…21.00:14.5:1
#000000
#FFFFFF
Pass
a Continue reading21.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.

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 18 passed
PASS
91

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
← Previous Page section.recent-articles > nav.pagination > div.pagination-nav > span.pagination-disabled

These are opportunities to improve the legibility of your content.

Names and labels

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
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > a
section.recent-articles > div.article-grid > article.article-card > a section.recent-articles > div.article-grid > article.article-card > 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.

○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>`
●`[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
●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.
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback