Skip to content
https://tonmr.shop

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
11
PASS
10
INFO
0
Checks
24
10 PASS 11 REVIEW 3 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-g7pz6i
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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::
2 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 2 <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
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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.

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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="main-search-input">; <input type="email" name="email">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#main-search-inputtext(Nə axtarırsınız?)placeholder only
emailemail(Email ünvanınız)placeholder only

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

<input type="text" name="q" id="main-search-input">; <input type="email" name="email">

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

C
Mobile Keyboard & Autofill
Action
1/2 eligible field(s) missing autocomplete or inputmode
REVIEW
1/2 eligible field(s) missing autocomplete or inputmode
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" name="email">
B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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.
B
Mobile-Readable Font Sizes
94% of visible text renders at >= 12 CSS px (6 below threshold)
REVIEW
94% of visible text renders at >= 12 CSS px (6 below threshold)
Info::
6 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.9px ("AZ"); <span> 10.9px ("TR"); <span> 10.9px ("EN"); <span> 10.9px ("RU"); <span> 10.0px ("VIP").
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✗ Multiple Sizes Missing
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: TONMR - Premium Elanlar
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name TONMR - Premium Elanlar ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name TONMR - Premium Elanlar Display Mode standalone Theme Color #12121c Background Color #12121c Icons 1 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: dark
Info::
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: #12121c
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 Ən Müasir Rəqəmsal Ekosistemi
1.03:1
#000000
on
#040508
needs 3.0:1 (large text)
32px · mid-page
h2 Son elanlar
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Populyar xidmətlər
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
24px · bottom of viewport
h2 📧 Xəbər Abunəliyi
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
24px · bottom of viewport
h3 🌿 YENİ MODEL BAĞ VƏ BALKON YELLƏN…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 🌿 YENİ MODEL METAL YELLƏNCƏK 🌿
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Təbii kənd yumurtası – gündəlik t…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PUBG mobile konsolu
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 POCO X3 PRO
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 POCO X7 PRO
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 VAZ 21 06
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 İstədiyiniz web saytlarının hazırla…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Epik Cinematic Vətənpərvər Video Haz…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Şəkildən Video və Mini Film Hazırla…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Lunasoft.az – Peşəkar Proqram Təmin…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Veb sayt hazırlanması və texniki dəs…
1.04:1
#000000
on
#050609
needs 3.0:1 (large text)
19px · bottom of viewport
title TONMR - Rəqəmsal Ekosistem
1.04:1
#000000
on
#040609
needs 4.5:1 (normal text)
16px · top of page (header area)
span TONMR
1.03:1
#000000
on
#040608
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ana Səhifə
1.09:1
#000000
on
#050F1C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Elanlar
1.67:1
#000000
on
#243546
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Ən Müasir Rəqəms…1.03:13.0:1
#000000
#040508
Fail
h2 Son elanlar1.04:13.0:1
#000000
#050609
Fail
h2 Populyar xidmətlər1.04:13.0:1
#000000
#050609
Fail
h2 📧 Xəbər Abunəl…1.04:13.0:1
#000000
#050609
Fail
h3 🌿 YENİ MODEL BA…1.04:13.0:1
#000000
#050609
Fail
h3 🌿 YENİ MODEL MET…1.04:13.0:1
#000000
#050609
Fail
h3 Təbii kənd yumurta…1.04:13.0:1
#000000
#050609
Fail
h3 PUBG mobile konsolu1.04:13.0:1
#000000
#050609
Fail
h3 POCO X3 PRO1.04:13.0:1
#000000
#050609
Fail
h3 POCO X7 PRO1.04:13.0:1
#000000
#050609
Fail
h3 VAZ 21 061.04:13.0:1
#000000
#050609
Fail
h3 İstədiyiniz web sa…1.04:13.0:1
#000000
#050609
Fail
h3 Epik Cinematic Vət…1.04:13.0:1
#000000
#050609
Fail
h3 Şəkildən Video v…1.04:13.0:1
#000000
#050609
Fail
h3 Lunasoft.az – Peş…1.04:13.0:1
#000000
#050609
Fail
h3 Veb sayt hazırlanma…1.04:13.0:1
#000000
#050609
Fail
title TONMR - Rəqəmsal E…1.04:14.5:1
#000000
#040609
Fail
span TONMR1.03:14.5:1
#000000
#040608
Fail
a Ana Səhifə1.09:14.5:1
#000000
#050F1C
Fail
a Elanlar1.67:14.5:1
#000000
#243546
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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 21 passed
REVIEW
80

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
✕‹› body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
header.navbar > div.container-custom > div.navbar-actions > button.mobile-nav-toggle header.navbar > div.container-custom > div.navbar-actions > button.mobile-nav-toggle

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
header.navbar > div.container-custom > div.navbar-actions > a.p-2 header.navbar > div.container-custom > div.navbar-actions > a.p-2

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
Abunə ol div.footer-col > div.newsletter-premium > form#newsletter-form > button
© 2026 TONMR. Bütün hüquqlar qorunur. footer.premium-footer > div.container > div.footer-bottom > p
Qəbul edirəm div#cookie-consent-banner > div.cc-wrap > div.cc-actions > button

These are opportunities to improve the legibility of your content.

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
✕ body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-close
‹ body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-prev
› body.is-home > div.tonmr-lightbox-overlay > div.tonmr-lightbox-modal > button.tonmr-lightbox-next

These items highlight common accessibility best practices.

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
Tətbiqi yüklə body.is-home > div.mobile-menu > button.btn-secondary
○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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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.
○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+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 Azərbaycanın Ən Müasir Rəqəmsal Ekosistemi
  • H2 Son elanlar
  • H3 🌿 YENİ MODEL BAĞ VƏ BALKON YELLƏNCƏYİ 🌿
  • H3 🌿 YENİ MODEL METAL YELLƏNCƏK 🌿
  • H3 Təbii kənd yumurtası – gündəlik təzə, halal və təmiz məhsul
  • H3 PUBG mobile konsolu
  • H3 POCO X3 PRO
  • H3 POCO X7 PRO
  • H3 VAZ 21 06
  • H3 İstədiyiniz web saytlarının hazırlanması ucuz və keyfiyyətli şəkildə həyata keçirilir.
  • H2 Populyar xidmətlər
  • H3 Epik Cinematic Vətənpərvər Video Hazırlanması (AI + Montaj)
  • H3 Şəkildən Video və Mini Film Hazırlanması (Canlandırma)
  • H3 Lunasoft.az – Peşəkar Proqram Təminatı və Rəqəmsal Xidmətlər
  • H3 Veb sayt hazırlanması və texniki dəstək xidməti
  • H4 Sürətli Keçidlər
  • H4 Dəstək və Hüquqi
  • H4 Bülletenə Abunə Ol
  • H2 📧 Xəbər Abunəliyi
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
5 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 5 all-caps heading(s)
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
15 image(s) with good alt text
15 images 15 good alt text
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "az-AZ"
PASS
Lang attribute set to "az-AZ"
Info::
<html lang="az-AZ"> is set and valid
Got: az-AZ
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://pagead2.googlesyndication.com/pagead/html/r20260527/r20190131/zrt_looku…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback