Accessibility

· 21 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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

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

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (29 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (29 below threshold)

29 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.2px ("№ 01"); <p> 11.2px ("/\u00a0 The cutting room"); <span> 11.2px ("№ 03"); <p> 11.2px ("/\u00a0 Also part of AppsGolem"); <span> 11.2px ("tiktok").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found | AppsGolem ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Heading Hierarchy

27 headings, 1 skip(s)

PASS

27 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Cut any YouTube clip up to 4K. Free first cut.
H2 The YouTube clipper creators actually use.
H2 Three more tools, same account.
H3 TikTok video downloader
H3 Twitch VOD downloader
H3 Most-replayed extractor
H2 What people actually do with it.
H3 Clip podcasts
H3 Make 9:16 social clips
H3 Highlight 10-hour streams
H3 Split a lecture
H3 Download a 4K clip
H3 Save Twitch VODs
H2 Three steps. About thirty seconds.
H3 Paste any YouTube link.
H3 Pick start + end.
H3 Get your clip.
H2 There are free alternatives. Here's the trade.
H2 Three plans, no usage caps.
H2 Real users. Real cuts.
H2 What people ask before they sign up.
H2 Cut your first clip — free, in 30 seconds.
H3 Select language.
H5 № Tools skipped
H5 № Use cases
H5 № Resources
H5 № Company

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+

Alt Text Quality

All 60 images OK

PASS

All 60 images OK

1 image(s) with alt text over 125 characters

13 decorative image(s) correctly marked

46 image(s) with good alt text

60 images 46 good alt text 13 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

59 links, 44 buttons — all OK

PASS

59 links, 44 buttons — all OK

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://twitter.com/AppsGolem

58 link(s) with descriptive text

59 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en/	AppsGolem	img no alt	Add alt attribute to the image
/en/cut-youtube-video/	YouTube Cutter …	img no alt	Add alt attribute to the image
/en/download-tik-tok-video/	TikTok Downloader …	img no alt	Add alt attribute to the image
/en/download-twitch-video/	Twitch Downloader …	img no alt	Add alt attribute to the image
/en/download-most-replayed-moment-youtub…	Most Replayed …	img no alt	Add alt attribute to the image
/en/cut-youtube-video/	YouTube Cutter	img no alt	Add alt attribute to the image
/en/download-tik-tok-video/	TikTok Downloader	img no alt	Add alt attribute to the image
/en/download-twitch-video/	Twitch Downloader	img no alt	Add alt attribute to the image
/en/download-most-replayed-moment-youtub…	Most Replayed	img no alt	Add alt attribute to the image
https://twitter.com/AppsGolem	Follow on	new tab	Add '(opens in new tab)' to text
/en/cut-youtube-video/	YouTube cutter	img no alt	Add alt attribute to the image
/en/download-tik-tok-video/	TikTok downloader	img no alt	Add alt attribute to the image
/en/download-twitch-video/	Twitch downloader	img no alt	Add alt attribute to the image
/en/download-most-replayed-moment-youtub…	Most-replayed extractor	img no alt	Add alt attribute to the image

102 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://twitter.com/AppsGolem

Why this matters

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

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)

Element	Ratio	Required	FG	BG	Result
h1 Cut any	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h1 clip up to 4K.	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 The YouTube clipper	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 Three more tools,	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 What people	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 with it.	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 Three steps.	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 There are free	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 alternatives.	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 Three plans,	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 Real users.	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 What people ask	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h2 Cut your first clip …	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 TikTok video downloa…	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Twitch VOD downloade…	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Most-replayed extrac…	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Clip podcasts	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Make 9:16 social cli…	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Highlight 10-hour st…	18.91:1	3.0:1	#000000	#F5F3EC	Pass
h3 Split a lecture	18.91:1	3.0:1	#000000	#F5F3EC	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.

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 23 passed

PASS

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
№ 02 `div.grid > div.md:col-span-5 > p.font-mono > span.text-brand`
№ 04 `div.grid > div.md:col-span-5 > p.font-mono > span.text-brand`
APPSGOLEM `table.w-full > thead > tr.bg-paper-deep > th.px-5`
№ 07 `div.grid > div.md:col-span-7 > p.font-mono > span.text-brand`
№ 10 `div.grid > div.md:col-span-7 > p.font-mono > span.text-brand`

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
№ TOOLS `footer.bg-paper > div.grid > div.md:col-span-2 > h5.mb-4`

These are opportunities to improve keyboard navigation in your application.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FREE DOWNLOADER SITES APPSGOLEM Quality 360p–720p, often re-encoded Up to 4K, … `div.bg-paper > section.px-6 > div.overflow-x-auto > table.w-full`

○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

●Image elements have `[alt]` attributes

●`[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 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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[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

○`<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

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○`<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.

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