Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DPrint StylesheetActionNo print stylesFIX
BLandmark Structure6 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
BHeading Hierarchy6 headings, 1 skip(s)REVIEW
- H2 Services
- H1 Yandex uses cookies
- H1 Cookie settings duplicate H1
- H3 Technical, always active skipped
- H3 Analytics/marketing
- H3 Other cookies
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
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
CLink & Button QualityAction2 issue(s) across 11 links and 3 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://passport.yandex.com/auth?origin=… | Profile, not logged in | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/images/?utm_source=ya… | Images | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/video/?utm_source=yan… | Video | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/maps/?utm_source=maps… | Maps | new tab | Add '(opens in new tab)' to text |
| https://translate.yandex.com/?utm_source… | Translate | new tab | Add '(opens in new tab)' to text |
| https://meteum.ai/?utm_source=yandex&utm… | Weather | new tab | Add '(opens in new tab)' to text |
| https://mail.yandex.com/?utm_source=yand… | new tab | Add '(opens in new tab)' to text | |
| https://yandex.com/games/?utm_source=yan… | Games | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/all | All | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/legal/cookies_policy_… | Cookie Policy | new tab | Add '(opens in new tab)' to text |
| https://yandex.com/legal/cookies_policy_… | Cookie Policy | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Add '(opens in new tab)' to link text or aria-label.
https://passport.yandex.com/auth?origin=morda&retpath=https%3A%2F%2Fyandex.co…; https://yandex.com/images/?utm_source=yandex&utm_medium=com&utm_campaign=morda; https://yandex.com/video/?utm_source=yandex&utm_medium=com&utm_campaign=morda; https://yandex.com/maps/?utm_source=maps&utm_medium=search&utm_campaign=desktop; https://translate.yandex.com/?utm_source=yandex&utm_medium=com&utm_campaign=m…; https://meteum.ai/?utm_source=yandex&utm_medium=com&utm_campaign=morda; https://mail.yandex.com/?utm_source=yandex&utm_medium=com&utm_campaign=morda?…; https://yandex.com/games/?utm_source=yandex&utm_medium=com&utm_campaign=morda; https://yandex.com/all; https://yandex.com/legal/cookies_policy_eng/ (+1 more)
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
Icon-only buttons need an aria-label so screen readers can announce them.
button.search3__keyboard (#136 on page); button.search3__action (#149 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding12 icon(s) detectedREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
A+Heading Text QualityAll 6 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityNo imagesPASS
AForm Accessibility1 of 2 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #text | input | Request | aria-label |
| #image-search | file | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="file" id="image-search">
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
A+Form Input Types1 input(s) using type=text where a specific type would helpPASS
A+Form Input Quality2 form control(s) checked, no input-semantic issuesPASS
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
A+Document LanguageLang attribute set to "en"PASS
A+Tabindex Anti-Patterns14 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 14 visible text node(s) render at >= 12 CSS pixelsPASS
AWeb ManifestPWA-readyPASS
APWA Depth2 PWA signal(s) surfacedPASS
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 Yandex uses cookies | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Cookie settings | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Services | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Technical, always ac… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Analytics/marketing | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 Other cookies | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Yandex — fast Inte… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Images | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Video | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Maps | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Translate | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Weather | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Mail | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div Games | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div All | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| label Search with Yandex A… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Search | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div {"static":"2026-11-1… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| div They ensure the smoo… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Cookie Policy | 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 — 2 failing, 23 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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Cookie Policy div.gdpr-popup-v3-main > div.gdpr-popup-v3-main__content-container > div#gdpr-popup-v3-main-description > a |
These are opportunities to improve the legibility of your content.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.document_tr-redesign_yes html.document_tr-redesign_yes |
These items highlight common accessibility best practices.