Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 3 REVIEW 8 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) 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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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 ✗

Lighthouse Accessibility Audits

Action

Score 63/100 — 4 failing, 6 passed

FIX

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
Become a registrar `div.header > div.menu > div.item > a`
Rules domain `div.header > div.menu > div.item > a`
activate domain `div.header > div.menu > div.item > a`
how can register `div.header > div.menu > div.item > a`
Why this domain to other people: `body > div.center > div.qwote > div.title`
Accredited registrars: `body > div.center > div.partners > div.title`
registrars `div.center > div.partners > div.title > a`
registrars `div.fb > div.question > p > a`
Want to stay up to date? `div.bx > div.fb > div.tweeter > div.time`
Follow us on Twitter `div.fb > div.tweeter > div.link > a`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Names and labels

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
body > div.header > div.logo > a `body > div.header > div.logo > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`
div.center > div.partners > div.list > a `div.center > div.partners > div.list > a`

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.

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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●The page contains a heading, skip link, or landmark region

○`[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-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has a valid value for its `[lang]` attribute

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

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

○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Link & Button Quality

Action

8 issue(s) across 25 links and 1 buttons

REVIEW

8 issue(s) across 25 links and 1 buttons

8 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /eng/index.html; https://nic.ua; https://regnames.com.ua/; https://pg.zp.ua; https://hostpro.ua; https://mesto.zp.ua; https://ukrhosting.com; https://prostohosting.com

7 link(s) open in new tab without warning

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

Got: http://dig.ua; https://drs.ua/en/registrars/; https://dig.ua; https://dig.ua; https://www.so.ua; https://www.psyho.ua; https://twitter.com/pp_ua

10 link(s) with descriptive text

25 links

8 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/eng/index.html	(empty)	empty	Add link text or aria-label
http://dig.ua	dig.ua	new tab	Add '(opens in new tab)' to text
https://drs.ua/en/registrars/	Accredited registrars	new tab	Add '(opens in new tab)' to text
https://dig.ua	check another domain	new tab	Add '(opens in new tab)' to text
https://dig.ua	is your domain	new tab	Add '(opens in new tab)' to text
https://nic.ua	(empty)	empty	Add link text or aria-label
https://regnames.com.ua/	(empty)	empty	Add link text or aria-label
https://pg.zp.ua	(empty)	empty	Add link text or aria-label
https://hostpro.ua	(empty)	empty	Add link text or aria-label
https://mesto.zp.ua	(empty)	empty	Add link text or aria-label
https://ukrhosting.com	(empty)	empty	Add link text or aria-label
https://prostohosting.com	(empty)	empty	Add link text or aria-label
https://www.so.ua	SO	new tab	Add '(opens in new tab)' to text
https://www.psyho.ua	PSYHO	new tab	Add '(opens in new tab)' to text
https://twitter.com/pp_ua	Follow us on Twitter	new tab	Add '(opens in new tab)' to text

11 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/eng/index.html; https://nic.ua; https://regnames.com.ua/; https://pg.zp.ua; https://hostpro.ua; https://mesto.zp.ua; https://ukrhosting.com; https://prostohosting.com

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

http://dig.ua; https://drs.ua/en/registrars/; https://dig.ua; https://dig.ua; https://www.so.ua; https://www.psyho.ua; https://twitter.com/pp_ua

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

a новий модуль активаці…

3.59:1

#258CC7

#FCFBF9

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title pp.ua - free domain …	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a Become	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a a registrar	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a Rules	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a domain	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a activate	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a domain	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a how can	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a register	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p To register a domain…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a dig.ua	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p . If the domain does…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p A domain available f…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a Accredited registrar…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p . Choose the regist…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p Once you have regist…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a have confirmed the d…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p . A confirmation cod…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
p Для актива�…	20.31:1	4.5:1	#000000	#FCFBF9	Pass
a новий моду�…	3.59:1	4.5:1	#258CC7	#FCFBF9	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 34 images OK

PASS

All 34 images OK

32 decorative image(s) correctly marked

2 image(s) with good alt text

34 images 2 good alt text 32 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="button">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	button	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

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

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