Skip to content
https://www.weston.com.ua

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 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

D
Mobile Keyboard & Autofill
Action
6/7 eligible field(s) missing autocomplete or inputmode
FIX
6/7 eligible field(s) missing autocomplete or inputmode
Warning::
5 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: username, email, current-password.
Got: <input type="text" name="username">, <input type="email" id="rememberMe">, <input type="text" name="username">, <input type="text" name="username" id="modlgn-username">, <input type="password" name="password" id="modlgn-passwd">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" id="rememberMe">
F
404 Error Page
Action
HTTP 508, custom page
FIX
HTTP 508, custom page
Warning::
Unexpected status code: HTTP 508
Expected HTTP 404 but received 508. This may confuse search engine crawlers.
Got: HTTP 508
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 508 ✗Page Title 508 Resource Limit Is Reached ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 62/100 — 5 failing, 11 passed
FIX
62

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

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#item-14960529412 > div#item-1667589847059 > div.custom-html > img div#item-14960529412 > div#item-1667589847059 > div.custom-html > img
div#item-15204640861 > div#item-1667715981861 > div.custom-html > img div#item-15204640861 > div#item-1667715981861 > div.custom-html > img
div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img
div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img
div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img
div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img
div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img div#item-16677176106296 > div#item-16686074587670 > div.custom-html > img

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.column-wrapper > div.ba-grid-column-wrapper > div#item-1667755800239 > a.ba-btn-transition div.column-wrapper > div.ba-grid-column-wrapper > div#item-1667755800239 > a.ba-btn-transition
div.column-wrapper > div.ba-grid-column-wrapper > div#item-1667756064804 > a.ba-btn-transition div.column-wrapper > div.ba-grid-column-wrapper > div#item-1667756064804 > a.ba-btn-transition
div.column-wrapper > div.ba-grid-column-wrapper > div#item-16677560674671 > a.ba-btn-transition div.column-wrapper > div.ba-grid-column-wrapper > div#item-16677560674671 > a.ba-btn-transition
div.slideshow-content > li.item > div.ba-slideshow-img > a div.slideshow-content > li.item > div.ba-slideshow-img > a
div.slideshow-content > li.item > div.ba-slideshow-caption > a div.slideshow-content > li.item > div.ba-slideshow-caption > a
div.ba-slideshow-caption > div.ba-blog-post-fields > div.ba-blog-post-field-row-wrapper > a.facebook div.ba-slideshow-caption > div.ba-blog-post-fields > div.ba-blog-post-field-row-wrapper > a.facebook
div.ba-slideshow-caption > div.ba-blog-post-fields > div.ba-blog-post-field-row-wrapper > a.instagram div.ba-slideshow-caption > div.ba-blog-post-fields > div.ba-blog-post-field-row-wrapper > a.instagram
div.ba-blog-posts-wrapper > div.ba-blog-post > div.ba-blog-post-image > a div.ba-blog-posts-wrapper > div.ba-blog-post > div.ba-blog-post-image > a
div.ba-blog-posts-wrapper > div.ba-blog-post > div.ba-blog-post-content > a div.ba-blog-posts-wrapper > div.ba-blog-post > div.ba-blog-post-content > a
div#item-15204640861 > div#item-16677162370380 > div.custom-html > a div#item-15204640861 > div#item-16677162370380 > div.custom-html > a
div#item-15204640861 > div#item-16677162370380 > div.custom-html > a div#item-15204640861 > div#item-16677162370380 > div.custom-html > 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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
НОВИЙ КОЛІР Gun Metal Перегляньте новий колір для розсувних систем WKS6, WKS7… div#item-1667590926951 > div#item-1667591194918 > div.slideshow-wrapper > ul.ba-slideshow
div#item-1667736729495 > div#item-1667736792333 > div.slideset-wrapper > ul.ba-slideset div#item-1667736729495 > div#item-1667736792333 > div.slideset-wrapper > ul.ba-slideset
Яна Солонська 07.02.2023 Дуже довго шукала душову кабіну, оскільки мала особлив… div#item-1667769072668 > div#item-1667895871274 > div.slideset-wrapper > ul.ba-slideset

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
НОВИЙ КОЛІР Gun Metal Перегляньте новий колір для розсувних систем WKS6, WKS7… div.slideshow-wrapper > ul.ba-slideshow > div.slideshow-content > li.item
Яна Солонська 07.02.2023 Дуже довго шукала душову кабіну, оскільки мала особлив… div.slideset-wrapper > ul.ba-slideset > div.slideshow-content > li.item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.slideshow-content > li.item > div.ba-slideshow-img > a div.slideshow-content > li.item > div.ba-slideshow-img > a

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>`
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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
○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
○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
○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.
○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.
C
Alt Text Quality
Action
7 of 17 images have issues
REVIEW
7 of 17 images have issues
Critical::
7 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
17 images 7 good alt text 3 decorative 7 missing
IssueCount
missing7 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

C
Form Accessibility
Action
7 of 14 controls have issues
REVIEW
7 of 14 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text">
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">; <input type="text" name="username">; <input type="password" name="password">; <input type="text" name="username">; <input type="password" name="password1">
Info::
7 control(s) properly labeled
14 controls
7 labeled
6 placeholder only
1 unlabeled
ControlTypeLabelMethod
#rememberMecheckboxnone
#rememberMeemailЗапам'ятайте менеfor/id
#rememberMetextЗапам'ятайте менеfor/id
#rememberMepasswordЗапам'ятайте менеfor/id
#modlgn-usernametextЛогинfor/id
#modlgn-passwdpasswordПарольfor/id
#modlgn-remembercheckboxЗапомнить меняfor/id
usernametext(Логін)placeholder only
password1password(Пароль)placeholder only
passwordpassword(Пароль)placeholder only
inputtext(Що саме шукаємо ?)placeholder only
inputtext(Що саме шукаємо ?)placeholder only
usernametext(Логін)placeholder only
inputtext(none)none

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

<input type="text">

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

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

<input type="text">; <input type="text">; <input type="text" name="username">; <input type="password" name="password">; <input type="text" name="username">; <input type="password" name="password1">

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

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
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
h1 Weston — виробник душови…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Premium серія
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 душових кабін від WESTON
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wellss від Weston:
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 замовляйте дзеркала т…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 кабіни від Weston
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 – відновимо економік…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Наші переваги
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Популярні товари
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Доставимо обрану душо…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Новою Поштою безкошто…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Каталог
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Вагаєтесь у виборі ду…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Розрахуйте вартість д…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 сьогодні та отримайте…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 консультацію
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Відгуки наших клієнті…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Останні публікації
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Відповіді на запитанн…
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Що ми виробляємо
1.11:1
#000000
on
#111111
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Weston — виро…1.11:13.0:1
#000000
#111111
Fail
h2 Premium серія1.11:13.0:1
#000000
#111111
Fail
h2 душових ка…1.11:13.0:1
#000000
#111111
Fail
h2 Wellss від Weston…1.11:13.0:1
#000000
#111111
Fail
h2 замовляйте…1.11:13.0:1
#000000
#111111
Fail
h2 кабіни від …1.11:13.0:1
#000000
#111111
Fail
h2 – відновим…1.11:13.0:1
#000000
#111111
Fail
h2 Наші перев…1.11:13.0:1
#000000
#111111
Fail
h2 Популярні …1.11:13.0:1
#000000
#111111
Fail
h2 Доставимо …1.11:13.0:1
#000000
#111111
Fail
h2 Новою Пошт…1.11:13.0:1
#000000
#111111
Fail
h2 Каталог1.11:13.0:1
#000000
#111111
Fail
h2 Вагаєтесь …1.11:13.0:1
#000000
#111111
Fail
h2 Розрахуйте…1.11:13.0:1
#000000
#111111
Fail
h2 сьогодні т…1.11:13.0:1
#000000
#111111
Fail
h2 консультац…1.11:13.0:1
#000000
#111111
Fail
h2 Відгуки на…1.11:13.0:1
#000000
#111111
Fail
h2 Останні пу…1.11:13.0:1
#000000
#111111
Fail
h2 Відповіді …1.11:13.0:1
#000000
#111111
Fail
h2 Що ми вироб…1.11:13.0:1
#000000
#111111
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+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H2 Gun Metal
  • H2 Нові моделі душових піддонів вже в продажу
  • H2 Premium серія
  • H2 душових кабін від WESTON
  • H2 Wellss від Weston: замовляйте дзеркала тут.
  • H2 Замовляйте душові кабіни від Weston – відновимо економіку України разом!
  • H2 Наші переваги
  • H2 Популярні товари
  • H2 Доставимо обрану душову кабіну Новою Поштою безкоштовно
  • H2 Каталог продукції
  • H3 Душові кабіни
  • H3 Душові піддони
  • H3 Онлайн калькулятор
  • H2 Вагаєтесь у виборі душової кабіни ? Розрахуйте вартість душової кабіни вже сьогодні та отримайте безкоштовн�
  • H2 Відгуки наших клієнтів
  • H3 Яна Солонська
  • H3 Дмитро та Ольга Алексєєви
  • H3 Олександр
  • H3 Анастасія Прокоп'єва
  • H3 Андрій
  • H3 О.М. Назаренко
  • H2 Останні публікації
  • H3 Чому душова кабіна? Переваги душових зі скла
  • H3 Як вибрати душову кабіну?
  • H3 Скляні перегородки для душу
  • H3 Як обрати скло для душової кабіни?
  • H3 Розсувні душові кабіни
  • H2 Відповіді на запитання
  • H1 Weston — виробник душових кабін в Україні
  • H2 Що ми виробляємо
  • H2 Чому нам довіряють
  • H2 Робота по Україні
  • H2 Як замовити душову кабіну Weston
  • H3 Навігація
  • H3 Продукція
  • H3 Співпраця
  • H3 Звʼязок з нами
  • H3 Login Form
A+
Heading Text Quality
All 38 heading(s) have substantive, well-formed text
PASS
All 38 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
14 form control(s) checked, no type mismatches
PASS
14 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A
Form Input Quality
1 input-semantic issue(s) across 14 form control(s)
PASS
1 input-semantic issue(s) across 14 form control(s)
Info::
3 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password1">, <input type="password" name="password2">, <input type="password" name="password">.
A+
Document Language
Lang attribute set to "ru-ru"
PASS
Lang attribute set to "ru-ru"
Info::
<html lang="ru-ru"> is set and valid
Got: ru-ru
A+
Tabindex Anti-Patterns
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 28 visible text node(s) render at >= 12 CSS pixels
PASS
All 28 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback