Skip to content
https://cutt.ly

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
5
PASS
5
INFO
0
Checks
13
5 PASS 5 REVIEW 3 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #1e5af9
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Form Accessibility
Action
5 of 13 controls have issues
REVIEW
5 of 13 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="star1" id="1star5">; <input type="radio" name="star1" id="1star4">; <input type="radio" name="star1" id="1star3">; <input type="radio" name="star1" id="1star2">; <input type="radio" name="star1" id="1star1">
Info::
8 control(s) properly labeled
13 controls
8 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#theme-toggle-checkboxcheckboxLight mode / Dark modearia-label
#linktextPaste a long URL to create a short linkaria-label
#cuttly_more_optionscheckboxmorearia-label
c_cuttly_survradionone
c_cuttly_survradionone
c_cuttly_survradionone
c_cuttly_survradionone
#pay_m_ycheckboxPay monthlyPay yearly - save one monthfor/id
#1star5radio(none)none
#1star4radio(none)none
#1star3radio(none)none
#1star2radio(none)none
#1star1radio(none)none

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

<input type="radio" name="star1" id="1star5">; <input type="radio" name="star1" id="1star4">; <input type="radio" name="star1" id="1star3">; <input type="radio" name="star1" id="1star2">; <input type="radio" name="star1" id="1star1">

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 404 Error - Page Not Found | Cuttly ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
51 headings
PASS
51 headings
Info::
Single H1 present
  • H1 The URL shortener that does more.
  • H2 Shorten long URLs instantly. Branded short links, QR Codes, Link in Bio, Campaigns, Surveys and Teams — your complete link management platform.
  • H2 Create Short link
  • H2 Take it to the next level
  • H2 Why Cuttly?
  • H3 URL Shortener
  • H3 Link analytics
  • H3 Surveys
  • H3 QR Codes
  • H3 Link in Bio
  • H3 Branded domains
  • H3 Branded Short Links
  • H3 Campaigns
  • H3 Robust Link Analytics
  • H3 Team Collaboration
  • H3 API & Integrations
  • H2 Track performance and click-through rate of short links.
  • H2 Discover the possibilities of managing short links.
  • H2 Create your survey!
  • H2 Harness audience insights with Cuttly Surveys.
  • H2 Create stylish and brandedQR codes to grow your business.
  • H2 Create modern Link in Bio pages.
  • H2 Mastering URL Shortening and Digital Strategies
  • H3 URL Shortener for Personal Branding — The Complete 2026 Guide
  • H3 How to Use Short Links in Social Media — The Complete 2026 Guide
  • H3 How to Create a Short Link — The Complete Step-by-Step Guide 2026
  • H3 URL Shortener for Publishers and Media — The Complete 2026 Guide
  • H3 URL Shortener for Recruitment and HR — The Complete 2026 Guide
  • H3 Link in Bio — The Best Tools, Strategies and Setup Guide for 2026
  • H2 Pricing for individuals, businesses, and companies of all sizes.
  • H2 TRAI-Compliant Link Shortening Solutions.
  • H2 TRAI-Compliant URL Shortener
  • H2 Let AI handle your linkswhile you focus on what matters.
  • H2 FAQ
  • H3 What is a URL shortener and how does it work?
  • H3 Is a URL shortener safe to use?
  • H3 Why should I use a URL shortener?
  • H3 What is a branded short link?
  • H3 Is Cuttly a free URL shortener?
  • H3 How long do short URLs created with Cuttly last?
  • H3 Does using a URL shortener affect SEO?
  • H3 What makes Cuttly different from other URL shorteners?
  • H2 Comprehensive URL Shortener and Link Management.
  • H2 Cuttly - Consistently Rated Among Top URL Shorteners.
  • H2 Cutt long links with Cuttly
  • H2 URL Shortener
  • H2 Shortener Comparisons
  • H2 Cuttly Tools
  • H2 Cuttly Resources
  • H2 Legal & Policies
  • H2 Languages
A+
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
28 image(s) with good alt text
28 images 28 good alt text
All images have appropriate alt text.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: css/print.css?v=0412202201
Print Stylesheet ✓ Print Optimized
Print stylesheet css/print.css?v=0412202201 ✓Inline @media print Not detected ✗
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 The URL shortener th…20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Shorten long URLs in…20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Create Short link20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Take it to the next …20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Why Cuttly?20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Track20.63:13.0:1
#000000
#FCFDFF
Pass
h2 and20.63:13.0:1
#000000
#FCFDFF
Pass
h2 of short links20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Discover20.63:13.0:1
#000000
#FCFDFF
Pass
h2 of managing20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Create your survey!20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Harness audience ins…20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Create stylish and20.63:13.0:1
#000000
#FCFDFF
Pass
h2 to grow your busines…20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Create modern20.63:13.0:1
#000000
#FCFDFF
Pass
h2 pages20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Mastering20.63:13.0:1
#000000
#FCFDFF
Pass
h2 and20.63:13.0:1
#000000
#FCFDFF
Pass
h2 for individuals, bus…20.63:13.0:1
#000000
#FCFDFF
Pass
h2 Link Shortening Solu…20.63:13.0:1
#000000
#FCFDFF
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.

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 31 passed
PASS
100

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookies div.footer-menu > ul > li > a
○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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
●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.
●`[lang]` attributes have a valid value
●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 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
○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.
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback