Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #071426

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 ModePartial Dark Mode

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Mobile-Readable Font Sizes

94% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

94% of visible text renders at >= 12 CSS px (7 below threshold)

7 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.6px ("Kondisioner · Kombi · Təmir · Xidmət"); <span> 11.8px ("Xidmətlərimiz"); <p> 11.8px ("Niyə biz?"); <small> 11.5px ("Müştəri"); <p> 11.8px ("FAQ").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 Kondisioner və kombi ustası Bakıda

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Peşəkar xidmətlər

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

h2 hər zaman sizin üçün

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Xidmətimiz fərq yaradır

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Kondisioner servisi haqqında suallar

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ustanın getdiyi Bakı rayonları

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Salam, Xoş Gəldiniz!

1.15:1

#000000

#0B1527

needs 3.0:1 (large text)

24px · bottom of viewport

title Kondisioner və kombi ustası Bakı | T�…

1.16:1

#000000

#0C1629

needs 4.5:1 (normal text)

16px · top of page (header area)

a Əsas məzmuna keç

1.16:1

#000000

#0C162A

needs 4.5:1 (normal text)

16px · top of page (header area)

span Mikrorayon

1.75:1

#000000

#2C3749

needs 4.5:1 (normal text)

16px · top of page (header area)

span Servis

1.89:1

#000000

#323C4D

needs 4.5:1 (normal text)

16px · top of page (header area)

span .az

1.84:1

#000000

#313A4B

needs 4.5:1 (normal text)

16px · above the fold

span Kondisioner · Kombi · Təmir · Xidmə…

1.70:1

#000000

#2B3546

needs 4.5:1 (normal text)

16px · above the fold

a Əsas

1.52:1

#000000

#232D3E

needs 4.5:1 (normal text)

16px · above the fold

a Xidmətlər

1.37:1

#000000

#1C2536

needs 4.5:1 (normal text)

16px · above the fold

a Kombi

1.22:1

#000000

#121B2C

needs 4.5:1 (normal text)

16px · above the fold

a Korporativ/Sənaye

1.15:1

#000000

#0D1527

needs 4.5:1 (normal text)

16px · above the fold

a Haqqımızda

1.13:1

#000000

#0B1325

needs 4.5:1 (normal text)

16px · above the fold

a Əlaqə

1.13:1

#000000

#0B1325

needs 4.5:1 (normal text)

16px · above the fold

span +994 70 477 03 27

1.14:1

#000000

#0B1425

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Kondisioner və komb…	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 Peşəkar xidmətlə…	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 hər zaman sizin ü�…	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 Xidmətimiz fərq ya…	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 Kondisioner servisi …	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 Ustanın getdiyi Bak…	1.15:1	3.0:1	#000000	#0B1527	Fail
h2 Salam, Xoş Gəldini…	1.15:1	3.0:1	#000000	#0B1527	Fail
title Kondisioner və komb…	1.16:1	4.5:1	#000000	#0C1629	Fail
a Əsas məzmuna keç	1.16:1	4.5:1	#000000	#0C162A	Fail
span Mikrorayon	1.75:1	4.5:1	#000000	#2C3749	Fail
span Servis	1.89:1	4.5:1	#000000	#323C4D	Fail
span .az	1.84:1	4.5:1	#000000	#313A4B	Fail
span Kondisioner · Kombi…	1.70:1	4.5:1	#000000	#2B3546	Fail
a Əsas	1.52:1	4.5:1	#000000	#232D3E	Fail
a Xidmətlər	1.37:1	4.5:1	#000000	#1C2536	Fail
a Kombi	1.22:1	4.5:1	#000000	#121B2C	Fail
a Korporativ/Sənaye	1.15:1	4.5:1	#000000	#0D1527	Fail
a Haqqımızda	1.13:1	4.5:1	#000000	#0B1325	Fail
a Əlaqə	1.13:1	4.5:1	#000000	#0B1325	Fail
span +994 70 477 03 27	1.14:1	4.5:1	#000000	#0B1425	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.

Landmark Structure

14 landmarks

PASS

14 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Heading Hierarchy

12 headings, 1 skip(s)

PASS

12 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Kondisioner və kombi ustası Bakıda Tam təmir və servis
H2 Peşəkar xidmətlər hər zaman sizin üçün
H3 Kondisioner Xidmətləri
H3 Kombi Xidmətləri
H3 Korporativ / Sənaye
H2 Xidmətimiz fərq yaradır
H2 Kondisioner servisi haqqında suallar
H2 Ustanın getdiyi Bakı rayonları
H2 Salam, Xoş Gəldiniz!
H4 Kombi Xidmətləri skipped
H4 Kondisioner Xidmətləri
H4 Böyük Sistemlər

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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 Quality

All 12 heading(s) have substantive, well-formed text

PASS

All 12 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

1 decorative image(s) correctly marked

4 image(s) with good alt text

5 images 4 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

62 links, 9 buttons — all OK

PASS

62 links, 9 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://wa.me/994704770327; https://wa.me/994704770327; https://wa.me/994704770327; https://wa.me/994704770327

58 link(s) with descriptive text

62 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/994704770327	WhatsApp ilə yaz	new tab	Add '(opens in new tab)' to text
https://wa.me/994704770327	WhatsApp ilə yaz	new tab	Add '(opens in new tab)' to text
https://wa.me/994704770327	WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/994704770327	WhatsApp	new tab	Add '(opens in new tab)' to text

67 links and buttons have descriptive text

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

https://wa.me/994704770327; https://wa.me/994704770327; https://wa.me/994704770327; https://wa.me/994704770327

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "az"

PASS

Lang attribute set to "az"

<html lang="az"> is set and valid

Got: az

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 26 passed

PASS

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
XİDMƏTLƏRİMİZ `div.container > div.hx-services-intro > p.hx-eyebrow > span`
Bütün xidmətlər `div.container > div.hx-services-intro > a.btn > span`
NİYƏ BİZ? `section.hx-why > div.container > div.hx-why-intro > p.hx-eyebrow`
Haqqımızda `div.container > div.hx-why-intro > a.btn > span`
FAQ `section.hx-faq > div.container > div > p.hx-eyebrow`
Qəbul et `div#mrsConsentBanner > div.mrs-consent-inner > div.mrs-consent-actions > button#mrsConsentAllow`

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
MikrorayonServis.az Kondisioner · Kombi · Təmir · Xidmət `body.v2 > header#header > div.header-inner > a.logo`
MikrorayonServis.az Kondisioner · Kombi · Təmir · Xidmət `footer.footer > div.container > div.footer-top > a.logo`

○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

●`[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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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 are distinguishable without relying on color.

●Links have a discernible name

●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.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

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

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

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

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