Skip to content
https://aeon.co

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 429 ✗Page Title Vercel Security Checkpoint ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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
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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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
Form Accessibility
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input type="search" name="q">; <input name="email" id="_r_1_">
Info::
2 control(s) properly labeled
5 controls
2 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
#_r_3_checkboxnone
#_r_4_checkboxnone
#_r_1_input(Your email address)placeholder only
qsearch(SEARCH)placeholder only
qsearch(SEARCH)placeholder only

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

<input type="search" name="q">; <input type="search" name="q">; <input name="email" id="_r_1_">

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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: only light
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #9d120d
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta only light ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 2 pass AA only
a Psychology
1.00:1
#940B52
on
#5C482E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Society
2.30:1
#9D120D
on
#A1824F
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Culture
1.03:1
#C16E15
on
#A17A3D
needs 4.5:1 (normal text)
16px · above the fold
a Essays
3.03:1
#000000
on
#725431
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Justice is geometric13.52:13.0:1
#000000
#B9D5D3
Pass
h2 Where centralised so…12.16:13.0:1
#000000
#DEBCCB
Pass
h2 Popular this month21.00:13.0:1
#000000
#FFFFFF
Pass
title Aeon | a world of id…21.00:14.5:1
#000000
#FFFFFF
Pass
button CLOSE21.00:14.5:1
#000000
#FFFFFF
Pass
a Philosophy5.42:14.5:1
#0C776D
#FFFFFF
Pass
a Science7.81:14.5:1
#035A6D
#FFFFFF
Pass
a Psychology1.00:14.5:1
#940B52
#5C482E
Fail
a Society2.30:14.5:1
#9D120D
#A1824F
Fail
a Culture1.03:14.5:1
#C16E15
#A17A3D
Fail
a Essays3.03:14.5:1
#000000
#725431
Fail
a Videos5.14:14.5:1
#000000
#A2744C
Pass
a Popular7.16:14.5:1
#000000
#B7905D
Pass
a About11.94:14.5:1
#000000
#CFC1B4
Pass
a DONATE21.00:14.5:1
#000000
#FFFFFF
Pass
a NEWSLETTER21.00:14.5:1
#000000
#FFFFFF
Pass
button MENU21.00:14.5:1
#000000
#FFFFFF
Pass
a DONATE21.00:14.5:1
#000000
#FFFFFF
Pass
a NEWSLETTER21.00:14.5:1
#000000
#FFFFFF
Pass
span SIGN IN21.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 85/100 — 3 failing, 23 passed
REVIEW
85

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mx-auto > div.flex > div.flex > button.hover:opacity-70 div.mx-auto > div.flex > div.flex > button.hover:opacity-70

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.space-y-1 > label.flex > label.flex > input#_r_3_ div.space-y-1 > label.flex > label.flex > input#_r_3_
div.space-y-1 > label.flex > label.flex > input#_r_4_ div.space-y-1 > label.flex > label.flex > input#_r_4_

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
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group
Save div.group/card > div.relative > div.flex > button.group

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
●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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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
○`<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
○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+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 Justice is geometric
  • H2 Where centralised societies excel at extraction, African fractal systems allow for circulation, reciprocity and return
  • H2 Popular this month
A
Alt Text Quality
All 30 images OK
PASS
All 30 images OK
Info::
4 image(s) with alt text over 125 characters
Info::
26 image(s) with good alt text
30 images 26 good alt text
IssueCount
too long4 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback