Skip to content
https://sert-nfpmk.ru

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
10
REVIEW
6
PASS
8
INFO
0
Checks
24
8 PASS 6 REVIEW 10 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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
Form Accessibility
Action
4 of 10 controls have issues
FIX
4 of 10 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="Date" id="input_5854200896061">; <select name="Selectbox" id="input_1762624253478">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="Name" id="input_1762625077493">; <input type="email" name="Email" id="input_5854200896060">
Info::
6 control(s) properly labeled
10 controls
6 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#input_5017513689600emailEmailfor/id
#input_5017513689601textИмяfor/id
#input_5017513689603textareaВаш вопросfor/id
#input_6967513689600emailEmailfor/id
#input_6967513689601textИмя и фамилияfor/id
#input_6967513689603selectУровень сертификацииfor/id
#input_1762625077493text(Смирнов Иван)placeholder only
#input_5854200896060email(Ваш e-mail)placeholder only
#input_5854200896061text(none)none
#input_1762624253478select(none)none

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

<input type="text" name="Date" id="input_5854200896061">; <select name="Selectbox" id="input_1762624253478">

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" name="Name" id="input_1762625077493">; <input type="email" name="Email" id="input_5854200896060">

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

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
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 ✓Page Title 404 Page Not Found. ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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::
1 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 1 <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
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
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

C
Mobile Keyboard & Autofill
Action
3/9 eligible field(s) missing autocomplete or inputmode
REVIEW
3/9 eligible field(s) missing autocomplete or inputmode
Warning::
3 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" id="input_5854200896060">, <input type="email" name="Email" id="input_5017513689600">, <input type="email" name="Email" id="input_6967513689600">
B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <input>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <select>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Mobile-Readable Font Sizes
92% of visible text renders at >= 12 CSS px (11 below threshold)
REVIEW
92% of visible text renders at >= 12 CSS px (11 below threshold)
Info::
11 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: <div> 10.0px ("Ваши фамилия и имя"); <div> 10.0px ("Дата выбранного менторинга"); <div> 10.0px ("В какой роли хотите участвовать?"); <div> 10.0px ("Бизнес коуч (СПБК НФПМК), победитель Пре..."); <div> 10.0px ("Сертифицированный коуч (СПК НФПМК), неве...").
C
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
span ВСЁ О СЕРТИФИКАЦИИ
1.13:1
#FFFFFF
on
#F5F1E8
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Универсаль…16.71:14.5:1
#000000
#EAE5D9
Pass
a О сертифик…16.71:14.5:1
#000000
#EAE5D9
Pass
a Расписание17.84:14.5:1
#000000
#F1ECE2
Pass
a Менторы18.63:14.5:1
#000000
#F5F1E8
Pass
a Записи18.63:14.5:1
#000000
#F5F1E8
Pass
a Вопросы18.63:14.5:1
#000000
#F5F1E8
Pass
a Полезные м…18.63:14.5:1
#000000
#F5F1E8
Pass
span Заявка18.63:14.5:1
#000000
#F5F1E8
Pass
div Стандарты …18.63:14.5:1
#000000
#F5F1E8
Pass
span ВСЁ О СЕРТИ…1.13:14.5:1
#FFFFFF
#F5F1E8
Fail
div по российс…18.63:14.5:1
#000000
#F5F1E8
Pass
div Национальн…18.63:14.5:1
#000000
#F5F1E8
Pass
span Групповые …18.63:14.5:1
#000000
#F5F1E8
Pass
span Полезные м…18.63:14.5:1
#000000
#F5F1E8
Pass
div Татьяна Ру…18.63:14.5:1
#000000
#F5F1E8
Pass
li о российск…18.63:14.5:1
#000000
#F5F1E8
Pass
li как проход…18.63:14.5:1
#000000
#F5F1E8
Pass
li что важно у…18.63:14.5:1
#000000
#F5F1E8
Pass
li на что обра…17.68:14.5:1
#000000
#E1F3B4
Pass
li какие есть …17.15:14.5:1
#000000
#D4F491
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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 6 failing, 19 passed
REVIEW
77

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
Бизнес коуч (СПБК НФПМК), победитель Премии “ТОП-3 executive&business коучей” 2… li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Сертифицированный коуч (СПК НФПМК), невербальный коуч, телесно-ориентированный … li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Executive, бизнес и командный коуч (СПБК НФПМК), сертифицированный WingWave коуч li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), командный коуч, автор программ по навыкам управления … li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), экспоненциальный коуч, ментор и инструктор в Сколково li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Сертифицированный коуч (СПК НФПМК), действующий директор по персоналу li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), командный коуч, преподавать коучинговых программ li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
Бизнес коуч (СПБК НФПМК), телесно-ориентированный терапевт, бизнес-тренер li.t524__col > div.t524__itemwrapper > div.t524__wrappercenter > div.t524__persdescr
политикой конфиденциальности div.t678__form-bottom-text > strong > u > a
политикой конфиденциальности div.t678__form-bottom-text > strong > u > a
Made on div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtleft
Tilda div#tildacopy > a.t-tildalabel__link > div.t-tildalabel__wrapper > div.t-tildalabel__txtright

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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.t-input-group > div.t-input-block > div.t-datepicker__wrapper > input#input_5854200896061 div.t-input-group > div.t-input-block > div.t-datepicker__wrapper > input#input_5854200896061

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
наблюдатель коуч клиент div.t-input-group > div.t-input-block > div.t-select__wrapper > select#input_1762624253478

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.t228__maincontainer > div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper div.t228__maincontainer > div.t228__leftside > div.t228__leftcontainer > a.t228__imgwrapper
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom
div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom div.t396 > div.t396__artboard > div.t396__elem > a.tn-atom
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a
div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > a div.t-persons-social-links > div.t-persons-social-links__wrapper > div.t-persons-social-links__item > 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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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]` 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 use only permitted ARIA attributes
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
A+
Heading Text Quality
No headings to evaluate -- check is N/A
PASS
No headings to evaluate -- check is N/A
Info::
No headings to evaluate -- check is N/A
A+
Alt Text Quality
All 3 images OK
PASS
All 3 images OK
Info::
3 decorative image(s) correctly marked
3 images 3 decorative
All images have appropriate alt text.
A+
Form Input Types
10 form control(s) checked, no type mismatches
PASS
10 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
10 form control(s) checked, no input-semantic issues
PASS
10 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback