Skip to content
https://appscyborg.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✗ Multiple Sizes Missing
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 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
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 footer

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title AppsCyborg | Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Apps Cyborg
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: fullscreen
PWA Install Criteria Not Installable
Name Apps Cyborg ✓192×192 icon ✗512×512 icon ✓Start URL ✗Display Mode fullscreen ✓
Name Apps Cyborg Display Mode fullscreen Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
A+
Heading Hierarchy
15 headings
PASS
15 headings
Info::
Single H1 present
  • H2 Cut Any YouTube Video Directly In Your Browser.
  • H1 78 ESSENTIAL ONLINE APPS for Your Digital Needs!
  • H2 MOST POPULARCYBORG WEB APPS
  • H2 SEARCHFOR A CYBORG WEB APP
  • H2 APPS FOR AUDIO .
  • H2 APPS FOR DOCUMENT .
  • H2 APPS FOR IMAGES .
  • H2 APPS FOR MICROSOFT EXCEL .
  • H2 APPS FOR PDF .
  • H2 APPS FOR SOCIAL NETWORKS .
  • H2 APPS FOR TIME .
  • H2 APPS FOR VIDEO .
  • H2 APPS FOR WEBPAGE .
  • H3 SnipRelay
  • H3 VideoConduit
A+
Alt Text Quality
All 161 images OK
PASS
All 161 images OK
Info::
161 image(s) with good alt text
161 images 161 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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="search" name="search" id="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchsearch(ex: download video)placeholder only

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

<input type="search" name="search" id="search">

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

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 for Your Digital Nee…17.03:13.0:1
#000000
#E2E8F0
Pass
h2 Cut Any YouTube Vide…17.03:13.0:1
#000000
#E2E8F0
Pass
h2 CYBORG WEB APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 FOR A CYBORG WEB APP17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h2 APPS17.03:13.0:1
#000000
#E2E8F0
Pass
h3 SnipRelay17.03:13.0:1
#000000
#E2E8F0
Pass
h3 VideoConduit17.03:13.0:1
#000000
#E2E8F0
Pass
title AppsCyborg: 78+ Priv…21.00:14.5:1
#000000
#FFFFFF
Pass
span Open main menu21.00:14.5:1
#000000
#FFFFFF
Pass
a APPS CYBORG19.93:14.5:1
#000000
#F8F9FB
Pass
a Blog17.03:14.5:1
#000000
#E2E8F0
Pass
a Pricing17.03:14.5:1
#000000
#E2E8F0
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 90/100 — 3 failing, 20 passed
PASS
90

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
YOUTUBE URL div.flex > div.relative > div.flex > label.font-bold
Duration: 30 seconds div.relative > div.flex > div.flex > div.font-medium
5.2 MB div.flex > div.ml-3 > div.flex > span.font-bold
"url": "youtube.com/...", "quality": "720p", "transcribe": true a.flex > div.flex > div.p-4 > div.pl-3
"url" div.flex > div.p-4 > div.pl-3 > span.text-sky-300
"youtube.com/..." div.flex > div.p-4 > div.pl-3 > span.text-emerald-300
"quality" div.flex > div.p-4 > div.pl-3 > span.text-sky-300
"720p" div.flex > div.p-4 > div.pl-3 > span.text-emerald-300
"transcribe" div.flex > div.p-4 > div.pl-3 > span.text-sky-300
true div.flex > div.p-4 > div.pl-3 > span.text-orange-300

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
@appscyborg footer.text-gray-700 > div.container > p.mt-4 > a.ml-1

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.

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
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback