Skip to content
https://reurl.cc

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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
Alt Text Quality
Action
7 of 10 images have issues
FIX
7 of 10 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
7 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 image(s) with good alt text
10 images 3 good alt text 7 missing
IssueCount
missing7 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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-9fkaci
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://reurl.cc/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://reurl.cc/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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 2 pass AA only
title URL Shortener - reurl
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
label Home
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Welcome to reurl.cc17.71:13.0:1
#000000
#E9ECEF
Pass
h2 Developer API17.71:13.0:1
#000000
#E9ECEF
Pass
h2 Browser Extension17.71:13.0:1
#000000
#E9ECEF
Pass
h2 LINE Bot17.71:13.0:1
#000000
#E9ECEF
Pass
h2 FAQ17.71:13.0:1
#000000
#E9ECEF
Pass
h3 Contact us17.71:13.0:1
#000000
#E9ECEF
Pass
title URL Shortener - reur…1.32:14.5:1
#000000
#222222
Fail
label Home1.32:14.5:1
#000000
#222222
Fail
span SignIn10.91:14.5:1
#000000
#80C7C7
Pass
span Language6.79:14.5:1
#000000
#2BA2A2
Pass
span 繁中6.79:14.5:1
#000000
#2BA2A2
Pass
span 简中13.75:14.5:1
#000000
#AADADA
Pass
span English21.00:14.5:1
#000000
#FFFFFF
Pass
span 97661bf9-1cd1-447f-a…21.00:14.5:1
#000000
#FFFFFF
Pass
span Shorten succeeded!21.00:14.5:1
#000000
#FFFFFF
Pass
span Copy succeeded!21.00:14.5:1
#000000
#FFFFFF
Pass
span Page time out, pleas…21.00:14.5:1
#000000
#FFFFFF
Pass
span Too long url (over 7…21.00:14.5:1
#000000
#FFFFFF
Pass
span Connect failed, plea…21.00:14.5:1
#000000
#FFFFFF
Pass
span loading...21.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.

C
Lighthouse Accessibility Audits
Action
Score 70/100 — 9 failing, 19 passed
REVIEW
70

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
ShortenURL Imgus Download youtube div.container > div.row > div.col-12 > ul#typeTab

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.

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#ats-slider-wrapper-7 > div#ats-slider-div-7 > button#ats-slider-button-7 div#ats-slider-wrapper-7 > div#ats-slider-div-7 > button#ats-slider-button-7

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.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img
div.row > div.col-4 > a > img.card-img div.row > div.col-4 > a > img.card-img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > ins.clickforceads > div > iframe#cfadif366 div.col-md-6 > ins.clickforceads > div > iframe#cfadif366
div.col-md-6 > ins.clickforceads > div > iframe#cfadif537 div.col-md-6 > ins.clickforceads > div > iframe#cfadif537
div.container > div.row > div.col-12 > iframe div.container > div.row > div.col-12 > iframe

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.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > a
div.card > div.row > div.col-4 > a div.card > div.row > div.col-4 > 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
Imgus ul#typeTab > li.nav-item > a#image-tab > span.lead
Download youtube ul#typeTab > li.nav-item > a#ytdlp-tab > span.lead
shorten div#url_tab > div.input-group > span.input-group-append > button.btn
View API Documentation div.row > div.col-md-6 > div.api-content > a.btn
Install Chrome Extension div.col-md-6 > div.extension-content > a.btn > span
Add LINE Bot div.col-md-6 > div.linebot-content > a.btn > span
What is a short URL? div.card > div#headingOne > h5.mb-0 > button.btn
What are the benefits of using short URLs? div.card > div#headingTwo > h5.mb-0 > button.btn
How long is a short URL valid? div.card > div#headingThree > h5.mb-0 > button.btn
How can I check the click count of a short URL? div.card > div#headingFour > h5.mb-0 > button.btn
How can I get short URL information without clicking the link? div.card > div#headingFive > h5.mb-0 > button.btn
Why are the preview image and description not showing after using Cloudflare on… div.card > div#headingSix > h5.mb-0 > button.btn
What are the usage limits of the Web API? div.card > div#headingSeven > h5.mb-0 > button.btn
FB page div.contact-form > div.row > div.col-12 > a
admin@reurl.cc div.contact-form > div.row > div.col-12 > a
English div.col-12 > div.row > div.col-8 > a
繁體中文 div.col-12 > div.row > div.col-8 > a
簡體中文 div.col-12 > div.row > div.col-8 > a
Emoji ul > li > a > span.lead
Geo IP ul > li > a > span.lead
Big5/GB Converter ul > li > a > span.lead
QR Code ul > li > a > span.lead
Length Converter ul > li > a > span.lead
Taiwan Company ul > li > a > span.lead
Taiwan Stock ul > li > a > span.lead
Word Counter ul > li > a > span.lead
Date Calculator ul > li > a > span.lead
Lunar Calendar ul > li > a > span.lead
Geo IP ul > li > a > span
Big5/GB Converter ul > li > a > span
QR Code ul > li > a > span
UTM tool ul > li > a > span

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What is a short URL? div#faqAccordion > div.card > div#headingOne > h5.mb-0

These are opportunities to improve keyboard navigation in your application.

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
ShortenURL div.row > div.col-12 > ul#typeTab > li.nav-item
Imgus div.row > div.col-12 > ul#typeTab > li.nav-item
Download youtube div.row > div.col-12 > ul#typeTab > 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
●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
●`[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>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○`<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
○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
13 headings, 1 skip(s)
PASS
13 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Welcome to reurl.cc
  • H2 Developer API
  • H2 Browser Extension
  • H2 LINE Bot
  • H2 FAQ
  • H5 What is a short URL? skipped
  • H5 What are the benefits of using short URLs?
  • H5 How long is a short URL valid?
  • H5 How can I check the click count of a short URL?
  • H5 How can I get short URL information without clicking the link?
  • H5 Why are the preview image and description not showing after using Cloudflare on my website?
  • H5 What are the usage limits of the Web API?
  • H3 Contact us

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
Form Accessibility
1 of 9 controls have issues
PASS
1 of 9 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="shortenBox">
Info::
8 control(s) properly labeled
9 controls
8 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputinputnone
inputinputnone
inputinputnone
inputinputnone
inputinputnone
#contact-nicktextYour namefor/id
#contact-emailemailYour Emailfor/id
#contact-contexttextareaContentfor/id
#shortenBoxtext(Input your url here)placeholder only

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

<input type="text" id="shortenBox">

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

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

Send Feedback