Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure9 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
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
BForm Input Quality2 input-semantic issue(s) across 6 form control(s)REVIEW
BMobile-Readable Font Sizes97% of visible text renders at >= 12 CSS px (1 below threshold)REVIEW
BFavicon & Branding6 icon(s) detectedREVIEW
AHeading Hierarchy6 headings, 1 skip(s)PASS
- H1 Вхід
- H3 Меню skipped
- H3 Блог
- H3 Співпраця
- H3 Соціальні мережі
- H3 Застереження
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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+Heading Text QualityAll 6 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityNo imagesPASS
AForm Accessibility1 of 6 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| s | search | Пошук | aria-label |
| s | search | Пошук | aria-label |
| input | search | Почніть вводити місто | aria-label |
| #inputEmail | input | Логін | for/id |
| #inputPassword | password | Пароль | for/id |
| textarea | textarea | (Коментар (не обов'язково)) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<textarea>
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
ALink & Button Quality252 links, 7 buttons — all OKPASS
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.instagram.com/stomatology.in… | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/stomatology.in.… | Ми у Facebook | new tab | Add '(opens in new tab)' to text |
Add '(opens in new tab)' to link text or aria-label.
https://www.instagram.com/stomatology.in.ua; https://www.facebook.com/stomatology.in.ua
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 Types1 input(s) using type=text where a specific type would helpPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "uk-UA"PASS
A+Tabindex Anti-PatternsNo explicit tabindex attributes foundPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A404 Error PageHTTP 404, custom pagePASS
A+Web ManifestPWA-readyPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Вхід | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| h3 Меню | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| h3 Блог | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| h3 Співпраця | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| h3 Соціальні Ð… | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| h3 Застережен… | 18.96:1 | 3.0:1 | #000000 | #EAF6F2 | Pass |
| title Вхід | СтомÐ… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span Стоматолог… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span каталог клÑ… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Блог | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Захворюван… | 17.29:1 | 4.5:1 | #000000 | #E3EAF0 | Pass |
| a Лікарі | 18.50:1 | 4.5:1 | #000000 | #EDF1F5 | Pass |
| a Клініки | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| a Послуги та … | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| a Акції | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| a 📍 Поруч зі… | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| button Кабінет клÑ… | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| a Вхід | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| a Реєстрація… | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | Pass |
| span Місто | 19.36:1 | 4.5:1 | #000000 | #F3F6F9 | 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.
ALighthouse Accessibility AuditsScore 94/100 — 2 failing, 19 passedPASS
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
UK header.header > div.container > div.mhead-lang > a.mhead-lang__link |
Увійти div.container > form.cform > div.login-actions > button.cform-submit |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Меню footer.sitefoot > div.container > nav.sitefoot-menu > h3.fcol-title |
These are opportunities to improve keyboard navigation in your application.