Skip to content
https://tinyurl.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Heading Hierarchy
Action
33 headings, 5 skip(s)
FIX
33 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Cookie Consent
  • H1 URL Shortener, Branded Short Links & Analytics
  • H5 Your Recent Links: skipped
  • H3 TinyURL Plans Include:
  • H5 Detailed Link Analytics skipped
  • H5 Fully Branded Domains
  • H5 Bulk Short URLs
  • H5 Link Management
  • H2 Link Shortening Done Quick and Easy
  • H3 Your One-Stop Solution for Branding and Managing Links
  • H5 Unlimited Tracked Clicks skipped
  • H5 Detailed Link Analytics
  • H5 Branded Domains
  • H5 Fully Custom Links
  • H5 Bulk Short URLs
  • H5 Link Management
  • H2 Transforming the Digital Landscape Since ‘02
  • H3 Billions
  • H3 24 years
  • H3 31,291,190,032
  • H3 Frequently Asked Questions
  • H6 What Is a URL Shortener? skipped
  • H6 How Does a URL Shortener Work?
  • H6 What Are the Benefits of Using a Short URL?
  • H6 What Is a Custom URL Shortener?
  • H6 How Do I Shorten a URL for Free?
  • H6 How Do I Know Your Service Is Reliable and Scalable?
  • H6 Can I Use a Domain I Already Own?
  • H2 Ready for Shorter, Smarter Links?
  • H5 Features skipped
  • H5 Resources
  • H5 Contact Us
  • H5 Legal

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

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

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

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

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

D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Pushnami
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Pushnami ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Pushnami Display Mode standalone
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.
B
Landmark Structure
17 landmarks
REVIEW
17 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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 Menu" MAIN CONTENTINFO footer

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

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 URL Shortener, Branded Short Links & Analytics | TinyURL ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
h1 URL Shortener, Branded Short Links & Ana…
1.32:1
#000000
on
#002342
needs 3.0:1 (large text)
32px · above the fold
title URL Shortener, Branded Short Links & Ana…
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · top of page (header area)
span Cookie Consent
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · top of page (header area)
p We use cookies to enhance your experienc…
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · top of page (header area)
a Cookie Policy.
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · top of page (header area)
span Allow Only Necessary
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · above the fold
span Allow All Cookies
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · above the fold
span Welcome to the original link shortener …
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · above the fold
span You can use branded domains for fully cu…
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · above the fold
span View Plans
1.32:1
#000000
on
#002342
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 URL Shortener, Brand…1.32:13.0:1
#000000
#002342
Fail
h2 Link Shortening Done…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Transforming the Dig…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready for Shorter, S…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 TinyURL Plans Includ…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Your One-Stop Soluti…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Billions21.00:13.0:1
#000000
#FFFFFF
Pass
h3 24 years21.00:13.0:1
#000000
#FFFFFF
Pass
h3 31,291,190,03221.00:13.0:1
#000000
#FFFFFF
Pass
h3 Frequently21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Asked Questions21.00:13.0:1
#000000
#FFFFFF
Pass
title URL Shortener, Brand…1.32:14.5:1
#000000
#002342
Fail
span Cookie Consent1.32:14.5:1
#000000
#002342
Fail
p We use cookies to en…1.32:14.5:1
#000000
#002342
Fail
a Cookie Policy.1.32:14.5:1
#000000
#002342
Fail
span Allow Only Necessary1.32:14.5:1
#000000
#002342
Fail
span Allow All Cookies1.32:14.5:1
#000000
#002342
Fail
span Welcome to the origi…1.32:14.5:1
#000000
#002342
Fail
span You can use branded …1.32:14.5:1
#000000
#002342
Fail
span View Plans1.32:14.5:1
#000000
#002342
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.

A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#urltextLong URL *for/id
#aliastextAlias (optional)for/id
A+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 27 passed
PASS
95

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.

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
Your Recent Links: div.tu-section-wrapper > div.tu-section-wrapper__content > div#recent-links > h5.shortener-section__url-stack-title
Detailed Link Analytics div.plan-banner__plans > div.tu-information-card > div.tu-information-card__text-content > h5.tu-information-card__title
Unlimited Tracked Clicks div.tu-carousel__item > div.tu-colored-card > section.tu-colored-card__content > h5.tu-colored-card__title
What Is a URL Shortener? section.faq-section > div.tu-accordion > div.tu-accordion__item > h6.tu-accordion__item-header-title
Contact Us footer.tu-footer__content > div.tu-footer__columns > div.tu-footer__link-column > h5#footer-link-title-2

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
No links yet in your history div.tu-section-wrapper > div.tu-section-wrapper__content > div#recent-links > ul.tu-shorten-url-stack

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

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
tinyurl.com div.tu-shortener-request-form__optional-inputs > div.tu-input-select > div.tu-input-select__input-wrapper > button#domain
○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
●`[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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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 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.
○`[lang]` attributes have a valid value
○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.
○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