Skip to content
https://notes.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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-jngfwb
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
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://notes.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://notes.io/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.
C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="button" id="btnShort">; <input type="button" id="btnAccount">; <input type="button">
Info::
1 control(s) properly labeled
4 controls
1 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#notesTextAreaIDtextareanone
#btnAccountbutton(none)none
inputbutton(none)none
#btnShortbutton(none)none

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

<input type="button" id="btnShort">; <input type="button" id="btnAccount">; <input type="button">

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

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

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

1 pass 19 fail WCAG AA
h3 Notes
1.63:1
#000000
on
#542312
needs 3.0:1 (large text)
19px · bottom of viewport
title Notes
2.06:1
#000000
on
#6C2F1A
needs 4.5:1 (normal text)
16px · top of page (header area)
span notes
4.11:1
#000000
on
#896659
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Popular notes
2.28:1
#000000
on
#733621
needs 4.5:1 (normal text)
16px · top of page (header area)
textarea Write a note in this area. It's really …
2.28:1
#000000
on
#733621
needs 4.5:1 (normal text)
16px · above the fold
p Notes is a web-based application for onl…
2.38:1
#000000
on
#763924
needs 4.5:1 (normal text)
16px · above the fold
p With notes.io;
2.50:1
#000000
on
#7A3C23
needs 4.5:1 (normal text)
16px · above the fold
li * You can take a note from anywhere and …
2.45:1
#000000
on
#783B22
needs 4.5:1 (normal text)
16px · above the fold
li * You can share the notes in social plat…
2.49:1
#000000
on
#793C27
needs 4.5:1 (normal text)
16px · above the fold
li * You can quickly share your contents wi…
2.31:1
#000000
on
#743722
needs 4.5:1 (normal text)
16px · above the fold
li * You don't need to create any Account t…
2.13:1
#000000
on
#6C331E
needs 4.5:1 (normal text)
16px · above the fold
li * Notes.io has fabulous infrastructure d…
2.04:1
#000000
on
#69301D
needs 4.5:1 (normal text)
16px · above the fold
b Fast:
1.90:1
#000000
on
#642B18
needs 3.0:1 (large text)
16px · above the fold
p Notes.io is built for speed and performa…
1.87:1
#000000
on
#632A17
needs 4.5:1 (normal text)
16px · mid-page
b Easy:
1.90:1
#000000
on
#642B18
needs 3.0:1 (large text)
16px · mid-page
p Notes.io doesn’t require installation.…
1.82:1
#000000
on
#5E2A15
needs 4.5:1 (normal text)
16px · mid-page
b Short:
1.82:1
#000000
on
#5E2A15
needs 3.0:1 (large text)
16px · mid-page
p Notes.io’s url just 8 character. You…
1.90:1
#000000
on
#612D18
needs 4.5:1 (normal text)
16px · mid-page
a notes.io/q
1.98:1
#000000
on
#64301B
needs 4.5:1 (normal text)
16px · mid-page

1 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
h2 Notes - notes.io9.36:13.0:1
#000000
#ADADAD
Pass
h3 Notes1.63:13.0:1
#000000
#542312
Fail
title Notes2.06:14.5:1
#000000
#6C2F1A
Fail
span notes4.11:14.5:1
#000000
#896659
Fail
a Popular notes2.28:14.5:1
#000000
#733621
Fail
textarea Write a note in this…2.28:14.5:1
#000000
#733621
Fail
p Notes is a web-based…2.38:14.5:1
#000000
#763924
Fail
p With notes.io;2.50:14.5:1
#000000
#7A3C23
Fail
li * You can take a not…2.45:14.5:1
#000000
#783B22
Fail
li * You can share the …2.49:14.5:1
#000000
#793C27
Fail
li * You can quickly sh…2.31:14.5:1
#000000
#743722
Fail
li * You don't need to …2.13:14.5:1
#000000
#6C331E
Fail
li * Notes.io has fabul…2.04:14.5:1
#000000
#69301D
Fail
b Fast:1.90:13.0:1
#000000
#642B18
Fail
p Notes.io is built fo…1.87:14.5:1
#000000
#632A17
Fail
b Easy:1.90:13.0:1
#000000
#642B18
Fail
p Notes.io doesn’t r…1.82:14.5:1
#000000
#5E2A15
Fail
b Short:1.82:13.0:1
#000000
#5E2A15
Fail
p Notes.io’s url jus…1.90:14.5:1
#000000
#612D18
Fail
a notes.io/q1.98:14.5:1
#000000
#64301B
Fail

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 82/100 — 3 failing, 12 passed
REVIEW
82

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

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.programArea > div.notesArea > label > textarea#notesTextAreaID div.programArea > div.notesArea > label > textarea#notesTextAreaID

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
I'm Feeling Lucky body > div.footer > p > a
Tiktok Video Downloader - SaveTik - (free for limited time) body > div.footer > p > a
Paste Keyboard iOS - Quick Replies body > div.footer > p > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○Buttons have an accessible name
○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
○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
○`<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.
○Identical links have the same purpose.
○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
5 headings, 1 skip(s)
PASS
5 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 notes
  • H2 Notes - notes.io
  • H6 Shortened Note Link skipped
  • H6 Long File
  • H3 Notes

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback