Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction3 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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
FForm AccessibilityAction7 of 10 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| input | text | none | |
| #custom | text | / | none |
| #save_stats_checkbox | checkbox | Log stats for this link | for/id |
| url | text | (Paste a Long URL) | placeholder only |
| username | text | (Username) | placeholder only |
| (Email) | placeholder only | ||
| input | reset | (none) | none |
| #create-submit | submit | (none) | none |
| #main-menu-checkbox | checkbox | (none) | none |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="checkbox" id="main-menu-checkbox">; <input type="submit" id="create-submit">; <input type="reset">; <input type="submit">
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
Placeholder text disappears on focus and is not a reliable label.
<input type="text" name="url">; <input type="text" name="username">; <input type="email" name="email">
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
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BAlt Text Quality1 of 6 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
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.
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
CLink & Button QualityAction1 issue(s) across 21 links and 3 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://tiny.cc/ | Home page | img no alt | Add alt attribute to the image |
| https://tinycc.com/ | Want more? Try Our Premium Pla… | img no alt | Add alt attribute to the image |
| https://twitter.com/Tiny_URL | new tab | Add '(opens in new tab)' to text | |
| <input> | (empty) | empty | Add button text or aria-label |
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a#home-link2; a[href="https://tinycc.com/"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://twitter.com/Tiny_URL
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
input[type="reset"] (#72 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
C404 Error PageActionHTTP 404, custom pageREVIEW
CFavicon & BrandingAction4 icon(s) detectedREVIEW
BColor Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Shorter URLs | Tinyc… | 7.08:1 | 3.0:1 | #000000 | #9A949B | Pass |
| h2 Register before you … | 7.26:1 | 3.0:1 | #000000 | #9C969D | Pass |
| h2 New Here? | 7.08:1 | 3.0:1 | #000000 | #9A949B | Pass |
| title Tiny URL | Free Shor… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Why us? | 14.43:1 | 4.5:1 | #000000 | #D8D5D8 | Pass |
| a Want more? | 7.35:1 | 4.5:1 | #000000 | #9D979E | Pass |
| a My URLs | 7.26:1 | 4.5:1 | #000000 | #9C969D | Pass |
| a Help | 7.35:1 | 4.5:1 | #000000 | #9D979E | Pass |
| a Log in | 7.08:1 | 4.5:1 | #000000 | #9A949B | Pass |
| a Sign Up | 7.08:1 | 4.5:1 | #000000 | #9A949B | Pass |
| span Optional short link … | 7.35:1 | 4.5:1 | #000000 | #9D979E | Pass |
| label Log stats for this l… | 7.35:1 | 4.5:1 | #000000 | #9D979E | Pass |
| p Note that anonymousl… | 7.26:1 | 4.5:1 | #000000 | #9C969D | Pass |
| a Learn more about URL… | 7.06:1 | 4.5:1 | #000000 | #99949B | Pass |
| div . Shorten URLs with… | 7.17:1 | 4.5:1 | #000000 | #9B959C | Pass |
| a paid plans | 7.35:1 | 4.5:1 | #000000 | #9D979E | Pass |
| b Special discount for… | 7.35:1 | 3.0:1 | #000000 | #9D979E | Pass |
| div Want more? | 7.17:1 | 4.5:1 | #000000 | #9B959C | Pass |
| div Try Our Premium Plan… | 6.91:1 | 4.5:1 | #000000 | #989299 | Pass |
| div Higher limits, bette… | 6.65:1 | 4.5:1 | #000000 | #958F96 | 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+Heading Hierarchy3 headingsPASS
- H1 Shorter URLs | Tinycc Free
- H2 Register before you shorten!
- H2 New Here?
ALighthouse Accessibility AuditsScore 91/100 — 2 failing, 13 passedPASS
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.padded-content > form#create > div.long_url_container > input#create-submit div.padded-content > form#create > div.long_url_container > input#create-submit |
div.padded-content > div.hide-on-recent > form > input.button1 div.padded-content > div.hide-on-recent > form > input.button1 |
Go Pro aside#sidebar > div.info > div.to-front > a.button1 |
These are opportunities to improve the legibility of your content.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.