Skip to content
https://hypotheses.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 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-sa1jtn
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://hypotheses.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://hypotheses.org/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
Landmark Structure
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) MAIN CONTENTINFO footer

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

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 5 failing, 22 passed
REVIEW
79

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#ob-header > div.openbarre__container > div.openbarre__right > button.openbarre__right__button div#ob-header > div.openbarre__container > div.openbarre__right > button.openbarre__right__button
div#ob-header > div.openbarre__container > div.openbarre__right > button#all-oe-button div#ob-header > div.openbarre__container > div.openbarre__right > button#all-oe-button

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#ob-header > div.openbarre__container > a.openbarre__link > img.openbarre__link__logo div#ob-header > div.openbarre__container > a.openbarre__link > img.openbarre__link__logo
div.openbarre__container > div.openbarre__right > button.openbarre__right__button > img.openbarre__right__button__icon div.openbarre__container > div.openbarre__right > button.openbarre__right__button > img.openbarre__right__button__icon
div.openbarre__container > div.openbarre__right > button#all-oe-button > img.openbarre__right__button__icon div.openbarre__container > div.openbarre__right > button#all-oe-button > img.openbarre__right__button__icon
div#all-oe-menu > div.openbarre__right__all__menu__networks > a.footer__networks__icon > img.openbarre__right__button__icon div#all-oe-menu > div.openbarre__right__all__menu__networks > a.footer__networks__icon > img.openbarre__right__button__icon
div#all-oe-menu > div.openbarre__right__all__menu__networks > a.footer__networks__icon > img.openbarre__right__button__icon div#all-oe-menu > div.openbarre__right__all__menu__networks > a.footer__networks__icon > img.openbarre__right__button__icon

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.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a
div.wp-block-columns > div.wp-block-column > figure.wp-block-image > a div.wp-block-columns > div.wp-block-column > figure.wp-block-image > 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.

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
SIGNUP div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link
LOGIN div.wp-block-column > div.wp-block-buttons > div.wp-block-button > a.wp-block-button__link

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.nb-3-3-8 > div#ob-header > div.openbarre__container > a.openbarre__link body.nb-3-3-8 > div#ob-header > div.openbarre__container > a.openbarre__link

These are opportunities to improve keyboard navigation in your application.

○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
●`[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
●Touch targets have sufficient size and spacing.
●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
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Oh noes!
A+
Alt Text Quality
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
13 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.

13 pass
Show all checked elements (13)
ElementRatioRequiredFGBGResult
h1 Oh noes!19.07:13.0:1
#000000
#F9F5D7
Pass
title Oh noes!19.07:14.5:1
#000000
#F9F5D7
Pass
p Access Denied: error…19.07:14.5:1
#000000
#F9F5D7
Pass
a Go home19.07:14.5:1
#000000
#F9F5D7
Pass
p Protected by19.07:14.5:1
#000000
#F9F5D7
Pass
a Anubis19.07:14.5:1
#000000
#F9F5D7
Pass
p From19.07:14.5:1
#000000
#F9F5D7
Pass
a Techaro19.07:14.5:1
#000000
#F9F5D7
Pass
p . Made with ❤️ i…19.07:14.5:1
#000000
#F9F5D7
Pass
p Mascot design by19.07:14.5:1
#000000
#F9F5D7
Pass
a CELPHASE19.07:14.5:1
#000000
#F9F5D7
Pass
p This website is runn…19.07:14.5:1
#000000
#F9F5D7
Pass
code 1.25.019.07:14.5:1
#000000
#F9F5D7
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