Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.F404 Error PageActionSoft 404 detectedFIX
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.
DPrint StylesheetActionNo print stylesFIX
CLandmark StructureAction2 landmarksREVIEW
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
BFavicon & Branding9 icon(s) detectedREVIEW
A+Heading Hierarchy1 headingsPASS
- H1 Security check
A+Heading Text QualityAll 1 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityNo imagesPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button QualityNo links or buttonsPASS
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "uz"PASS
A+Tabindex Anti-Patterns1 explicit tabindex attribute(s) checked, no anti-patternsPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 3 visible text node(s) render at >= 12 CSS pixelsPASS
A+Web ManifestPWA-readyPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Dark Mode SupportFull dark mode supportPASS
Detection limited to meta tags and inline styles.
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
A+Color Contrast (Screenshot)4 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 (4)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Security check | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Dental GPS — Stoma… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Complete this check … | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| span ⏳ Captcha kutilmoq… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | 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.
A+Lighthouse Accessibility AuditsScore 95/100 — 1 failing, 17 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.
ARIA
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Cloudflare Turnstile security check section.w-full > div.w-full > div.w-full > div.min-h-[65px] |
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.