Skip to content
https://deno.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 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-6i9dmp
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.

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://deno.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://deno.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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 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="checkbox" id="menuToggle">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="orama-search-input">; <input type="search" id="orama-search-input">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#orama-search-inputsearch(Search)placeholder only
#orama-search-inputsearch(Search)placeholder only
#menuTogglecheckbox(none)none

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

<input type="checkbox" id="menuToggle">

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

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

<input type="search" id="orama-search-input">; <input type="search" id="orama-search-input">

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
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 25 passed
REVIEW
89

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-full > div.flex > div.w-full > div.rounded-md div.w-full > div.flex > div.w-full > div.rounded-md
div.w-full > div.flex > div.w-full > div.rounded-md div.w-full > div.flex > div.w-full > div.rounded-md

These are opportunities to improve the usage of ARIA in your application which 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
Stars on GitHub div.w-full > ul.w-full > li > div.text-gray-3
Active Deno users div.w-full > ul.w-full > li > div.text-gray-3
Community modules div.w-full > ul.w-full > li > div.text-gray-3
Now offering enterprise support for the Deno runtime div.mx-auto > div.w-full > div.flex > div.!text-gray-3
More is better div.flex > div.w-full > div.border-b > p.text-gray-2
* Ubuntu 22 on ec2 m5.metal; Deno 2.5.2 vs. Node 18.12.1 div.w-full > div.grid > div.flex > small.text-gray-2
Manu (Qwik) div.w-full > div.grid > figure > figcaption.text-gray-2

These are opportunities to improve the legibility of your content.

Internationalization and localization

Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn how to use the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
$ deno lint --watch div.w-full > div.mt-16 > div.border > div.text-gray-50
$ deno test server_test.ts div.mt-16 > div.border > div.-mx-6 > div.text-gray-50
$ deno fmt --line-width=120 div.w-full > div.mt-16 > div.border > div.text-gray-50

These are opportunities to improve the interpretation of your content by users in different locales.

○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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<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
○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
○Links are distinguishable without relying on color.
○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.
○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
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer
A+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 Uncomplicate JavaScript
  • H2 Install Deno 2.7.11
  • H2 Deno is the open-source JavaScript runtime for the modern web.
  • H3 Enterprise-grade JavaScript
  • H2 All your favorite tools, built-in and ready to go
  • H3 Just run
  • H3 Seamless
  • H2 Built on web standards
  • H3 Consistent code from browser to backend
  • H2 Batteries included
  • H3 Code linter
  • H3 Test runner
  • H3 Standalone executables
  • H3 Code formatter
  • H2 Secure by default
  • H3 Prevent supply chain attacks
  • H4 Other runtimes
  • H4 Deno
  • H3 High-performance networking
  • H4 Requests per second*
  • H2 Built for the cloud
  • H3 — Deno runs on —
  • H2 — The cloud built for modern JavaScript —
  • H3 Project hosting made for Deno
  • H3 Unlock the full power of Deno
  • H3 Built for anything built with JavaScript
  • H2 Get the most out of Deno with Fresh 2.0
  • H3 Build fast sites fast
  • H3 Ship less JavaScript
  • H2 Ready to get started with Deno?
  • H2 Open-source
  • H2 Products
  • H2 Deno Resources
  • H2 Company
A+
Alt Text Quality
All 43 images OK
PASS
All 43 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
17 decorative image(s) correctly marked
Info::
25 image(s) with good alt text
43 images 25 good alt text 17 decorative
IssueCount
too long1 image(s)
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
h1 Uncomplicate JavaScr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Install Deno21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deno is the open-sou…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 All your favorite to…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built on web standar…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Batteries included21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure by default21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for the cloud21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get the most out of …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready to get started…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Open-source21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deno Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Enterprise-grade Jav…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Just run21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seamless21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Consistent code from…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Code linter21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Test runner21.00:13.0: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.

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

Send Feedback