Skip to content
https://rentry.co

Accessibility

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

D
Favicon & Branding
Action
19 icon(s) detected
FIX
19 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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
4 of 6 controls have issues
REVIEW
4 of 6 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="text" id="id_text">; <input type="checkbox">; <input type="checkbox">; <textarea name="metadata" id="metadata_text">
Info::
2 control(s) properly labeled
6 controls
2 labeled
0 placeholder only
4 unlabeled
ControlTypeLabelMethod
#id_edit_codetextCustom edit codearia-label
#id_urltextCustom urlaria-label
inputcheckbox(none)none
#metadata_texttextarea(none)none
#id_texttextarea(none)none
inputcheckbox(none)none

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

<textarea name="text" id="id_text">; <input type="checkbox">; <input type="checkbox">; <textarea name="metadata" id="metadata_text">

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

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 Error ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Lighthouse Accessibility Audits
Action
Score 76/100 — 6 failing, 17 passed
REVIEW
76

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Text Preview How div.col-12 > form#entry-form > div.my-2 > ul#textTab

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Text div.my-2 > ul#textTab > li.nav-item > a#text-tab
Preview div.my-2 > ul#textTab > li.nav-item > a#preview-tab
How div.my-2 > ul#textTab > li.nav-item > a#how-tab

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
Preview div.my-2 > ul#textTab > li.nav-item > a#preview-tab
How div.my-2 > ul#textTab > li.nav-item > a#how-tab
new div.text-center > div.bottom-links > div.link-container > a.mr-1
what div.text-center > div.bottom-links > div.link-container > a.mx-1
how div.text-center > div.bottom-links > div.link-container > a.mx-1
langs div.text-center > div.bottom-links > div.link-container > a.mx-1
contacts div.text-center > div.bottom-links > div.link-container > a.mx-1
login div.text-center > div.bottom-links > div.link-container > a.ml-1
Rentry.co - Markdown Paste Service div.col-12 > form#entry-form > div.text-center > h1.mb-0

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Text form#entry-form > div.my-2 > ul#textTab > li.nav-item
Preview form#entry-form > div.my-2 > ul#textTab > li.nav-item
How form#entry-form > div.my-2 > ul#textTab > li.nav-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

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-*]` 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
●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
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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 a valid value for its `[lang]` attribute
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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
78 headings
PASS
78 headings
Info::
Single H1 present
  • H2 Rentry Metadata Docs
  • H3 General Use
  • H3 Validations
  • H3 Tips
  • H3 Metadata Options
  • H4 GROUP: PAGE
  • H5 PAGE_TITLE
  • H5 PAGE_DESCRIPTION
  • H5 PAGE_IMAGE
  • H5 PAGE_ICON
  • H4 GROUP: SHARE
  • H5 SHARE_TITLE
  • H5 SHARE_DESCRIPTION
  • H5 SHARE_IMAGE
  • H5 SHARE_TWITTER_TITLE
  • H5 SHARE_TWITTER_DESCRIPTION
  • H5 SHARE_TWITTER_IMAGE
  • H4 GROUP: OPTION
  • H5 OPTION_DISABLE_VIEWS
  • H5 OPTION_DISABLE_SEARCH_ENGINE
  • H5 OPTION_USE_ORIGINAL_PUB_DATE
  • H4 GROUP: ACCESS
  • H5 ACCESS_RECOMMENDED_THEME
  • H5 ACCESS_EASY_READ
  • H4 GROUP: SECRET
  • H5 SECRET_VERIFY
  • H5 SECRET_RAW_ACCESS_CODE
  • H5 SECRET_EMAIL_ADDRESS
  • H4 GROUP: SAFETY
  • H5 SAFETY_PAGE_WARNING
  • H5 SAFETY_PAGE_WARNING_DESCRIPTION
  • H5 SAFETY_MEDIA_BLUR
  • H5 SAFETY_LINK_WARNING
  • H5 SAFETY_LINK_WARNING_DESCRIPTION
  • H5 SAFETY_PAGE_FLAG
  • H4 GROUP: CONTAINER
  • H5 CONTAINER_PADDING
  • H5 CONTAINER_MAX_WIDTH
  • H5 CONTAINER_INNER_FOREGROUND_COLOR
  • H5 CONTAINER_INNER_BACKGROUND_COLOR
  • H5 CONTAINER_INNER_BACKGROUND_IMAGE
  • H5 CONTAINER_INNER_BACKGROUND_IMAGE_REPEAT
  • H5 CONTAINER_INNER_BACKGROUND_IMAGE_POSITION
  • H5 CONTAINER_INNER_BACKGROUND_IMAGE_SIZE
  • H5 CONTAINER_OUTER_FOREGROUND_COLOR
  • H5 CONTAINER_OUTER_BACKGROUND_COLOR
  • H5 CONTAINER_OUTER_BACKGROUND_IMAGE
  • H5 CONTAINER_OUTER_BACKGROUND_IMAGE_REPEAT
  • H5 CONTAINER_OUTER_BACKGROUND_IMAGE_POSITION
  • H5 CONTAINER_OUTER_BACKGROUND_IMAGE_SIZE
  • H5 CONTAINER_BORDER_IMAGE
  • H5 CONTAINER_BORDER_IMAGE_SLICE
  • H5 CONTAINER_BORDER_IMAGE_WIDTH
  • H5 CONTAINER_BORDER_IMAGE_OUTSET
  • H5 CONTAINER_BORDER_IMAGE_REPEAT
  • H5 CONTAINER_BORDER_COLOR
  • H5 CONTAINER_BORDER_WIDTH
  • H5 CONTAINER_BORDER_STYLE
  • H5 CONTAINER_BORDER_RADIUS
  • H5 CONTAINER_SHADOW_COLOR
  • H5 CONTAINER_SHADOW_OFFSET
  • H5 CONTAINER_SHADOW_SPREAD
  • H5 CONTAINER_SHADOW_BLUR
  • H4 GROUP: CONTENT
  • H5 CONTENT_FONT
  • H5 CONTENT_FONT_WEIGHT
  • H5 CONTENT_TEXT_DIRECTION
  • H5 CONTENT_TEXT_SIZE
  • H5 CONTENT_TEXT_ALIGN
  • H5 CONTENT_TEXT_SHADOW_COLOR
  • H5 CONTENT_TEXT_SHADOW_OFFSET
  • H5 CONTENT_TEXT_SHADOW_BLUR
  • H5 CONTENT_TEXT_COLOR
  • H5 CONTENT_LINK_COLOR
  • H5 CONTENT_BULLET_COLOR
  • H5 CONTENT_LINK_BEHAVIOR
  • H3 Glossary
  • H1 Rentry.co - Markdown Paste Service
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.
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Rentry.co - Markdown Paste Service
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Rentry.co - Markdown Paste Service ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name Rentry.co - Markdown Paste Service Display Mode standalone Theme Color #ffffff Background Color #edeef0 Icons 18 icon(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 Rentry.co - Markdown…18.09:13.0:1
#000000
#EDEEF0
Pass
h2 Rentry Metadata Docs18.09:13.0:1
#000000
#EDEEF0
Pass
h3 General Use18.09:13.0:1
#000000
#EDEEF0
Pass
h3 Validations18.09:13.0:1
#000000
#EDEEF0
Pass
h3 Tips18.09:13.0:1
#000000
#EDEEF0
Pass
h3 Metadata Options18.09:13.0:1
#000000
#EDEEF0
Pass
h3 Glossary18.09:13.0:1
#000000
#EDEEF0
Pass
title Rentry.co - Markdown…18.09:14.5:1
#000000
#EDEEF0
Pass
a Text19.24:14.5:1
#000000
#F4F5F6
Pass
a Preview21.00:14.5:1
#000000
#FFFFFF
Pass
a How21.00:14.5:1
#000000
#FFFFFF
Pass
span ​21.00:14.5:1
#000000
#FFFFFF
Pass
span ​21.00:14.5:1
#000000
#FFFFFF
Pass
th What you type21.00:13.0:1
#000000
#FFFFFF
Pass
th What will be publish…21.00:13.0:1
#000000
#FFFFFF
Pass
td # Header 121.00:14.5:1
#000000
#FFFFFF
Pass
td ## Header 221.00:14.5:1
#000000
#FFFFFF
Pass
span And so on up to 6.21.00:14.5:1
#000000
#FFFFFF
Pass
p Header 121.00:14.5:1
#000000
#FFFFFF
Pass
p Header 221.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.

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

Send Feedback