Skip to content
https://ucoz.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
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.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) 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 header NAV MAIN CONTENTINFO (missing!)

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
Heading Hierarchy
10 headings
REVIEW
10 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Build Your Website Yourself
  • H3 uKit
  • H3 uCoz
  • H3 Telegram Shop
  • H2 Build it yourself
  • H2 uKit
  • H2 Online Stores
  • H2 Calculators by
  • H2 Create a Store in Telegram and Start Selling in Just a Few Clicks 🔥 😌
  • H2 Turnkey Web Services

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 HTTP 404 Resource not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Build Your Website Yourself
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · mid-page
h2 Build it yourself
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h2 uKit
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Online Stores
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Calculators by
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Create a Store in Telegram and Start Sel…
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Turnkey Web Services
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
24px · bottom of viewport
h3 uKit
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
19px · mid-page
h3 uCoz
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Telegram Shop
1.32:1
#000000
on
#132239
needs 3.0:1 (large text)
19px · bottom of viewport
title Build Your Own Website with uCoz — Fre…
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · top of page (header area)
a uCoz
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · top of page (header area)
a uCoz News
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · top of page (header area)
a uCoz Community Chat
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pricing
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
a Contact Us
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
a uCoz
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
span English
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
a Arabic
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
a Deutsch
1.32:1
#000000
on
#132239
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Build Your Website Y…1.32:13.0:1
#000000
#132239
Fail
h2 Build it yourself1.32:13.0:1
#000000
#132239
Fail
h2 uKit1.32:13.0:1
#000000
#132239
Fail
h2 Online Stores1.32:13.0:1
#000000
#132239
Fail
h2 Calculators by1.32:13.0:1
#000000
#132239
Fail
h2 Create a Store in Te…1.32:13.0:1
#000000
#132239
Fail
h2 Turnkey Web Services1.32:13.0:1
#000000
#132239
Fail
h3 uKit1.32:13.0:1
#000000
#132239
Fail
h3 uCoz1.32:13.0:1
#000000
#132239
Fail
h3 Telegram Shop1.32:13.0:1
#000000
#132239
Fail
title Build Your Own Websi…1.32:14.5:1
#000000
#132239
Fail
a uCoz1.32:14.5:1
#000000
#132239
Fail
a uCoz News1.32:14.5:1
#000000
#132239
Fail
a uCoz Community Chat1.32:14.5:1
#000000
#132239
Fail
a Pricing1.32:14.5:1
#000000
#132239
Fail
a Contact Us1.32:14.5:1
#000000
#132239
Fail
a uCoz1.32:14.5:1
#000000
#132239
Fail
span English1.32:14.5:1
#000000
#132239
Fail
a Arabic1.32:14.5:1
#000000
#132239
Fail
a Deutsch1.32:14.5:1
#000000
#132239
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 3 failing, 12 passed
REVIEW
78

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > button.menu-btn-v5 body > button.menu-btn-v5

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.choice-container > header.choice-header > div.choice-actions > a.choice-btn div.choice-container > header.choice-header > div.choice-actions > a.choice-btn

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
Website Builder for Business. Start from Scratch or Choose a Template div.card-wrapper > div.card > div.card-body > p
LLC Ucoz Media div.row > div.column-logo > div.copy-subtitle > p
Copyright © 2005-2026 div.row > div.column-logo > div.copy-subtitle > p

These are opportunities to improve the legibility of your content.

○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-hidden="true"]` is not present on the document `<body>`
●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-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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.
A+
Alt Text Quality
All 5 images OK
PASS
All 5 images OK
Info::
5 image(s) with good alt text
5 images 5 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback