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 3 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

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

No dark mode signals

FIX

No dark mode signals

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

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

1 navigation landmark(s) detected

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 1 <nav> element(s)

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.

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No contentinfo (footer) landmark

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found · GitHub Pages ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

3 pass 17 fail WCAG AA

h1 Notes

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

32px · above the fold

h2 Общее

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · mid-page

h2 C++

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · mid-page

h2 JavaScript

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · mid-page

h2 Базы данных

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · mid-page

h2 Теория компиляции

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Low Level

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Математика

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

24px · bottom of viewport

title Index | Notes

1.37:1

#000000

#242526

needs 4.5:1 (normal text)

16px · top of page (header area)

a Перейти к основному с�…

1.37:1

#000000

#242526

needs 4.5:1 (normal text)

16px · top of page (header area)

a GitHub

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · above the fold

b Главная

1.22:1

#000000

#1B1B1D

needs 3.0:1 (large text)

16px · above the fold

a C++

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · above the fold

a JavaScript

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · above the fold

a GitHub

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · above the fold

button ← Перейти к главному �…

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · above the fold

div Заметки на общие темы.

1.22:1

#000000

#1B1B1D

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Notes	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 Общее	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 C++	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 JavaScript	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 Базы данны�…	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 Теория ком�…	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 Low Level	1.22:1	3.0:1	#000000	#1B1B1D	Fail
h2 Математика	1.22:1	3.0:1	#000000	#1B1B1D	Fail
title Index \| Notes	1.37:1	4.5:1	#000000	#242526	Fail
a Перейти к о…	1.37:1	4.5:1	#000000	#242526	Fail
b Главная	10.91:1	3.0:1	#000000	#93C890	Pass
a C++	10.91:1	4.5:1	#000000	#93C890	Pass
a JavaScript	10.91:1	4.5:1	#000000	#93C890	Pass
a GitHub	1.22:1	4.5:1	#000000	#1B1B1D	Fail
b Главная	1.22:1	3.0:1	#000000	#1B1B1D	Fail
a C++	1.22:1	4.5:1	#000000	#1B1B1D	Fail
a JavaScript	1.22:1	4.5:1	#000000	#1B1B1D	Fail
a GitHub	1.22:1	4.5:1	#000000	#1B1B1D	Fail
button ← Перейти �…	1.22:1	4.5:1	#000000	#1B1B1D	Fail
div Заметки на …	1.22:1	4.5:1	#000000	#1B1B1D	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.

A+

Heading Hierarchy

8 headings

PASS

8 headings

Single H1 present

H1 Notes
H2 Общее
H2 C++
H2 JavaScript
H2 Базы данных
H2 Теория компиляции
H2 Low Level
H2 Математика

A+

Heading Text Quality

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

PASS

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

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

Alt Text Quality

2 of 2 images have issues

PASS

2 of 2 images have issues

2 image(s) with generic alt text

2 images 2 generic

Issue	Count
generic	2 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

18 links, 3 buttons — all OK

PASS

18 links, 3 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://github.com/wermuind; https://github.com/wermuind; https://github.com/wermuind

15 link(s) with descriptive text

18 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/wermuind	GitHub	new tab	Add '(opens in new tab)' to text
https://github.com/wermuind	GitHub	new tab	Add '(opens in new tab)' to text
https://github.com/wermuind	мне	new tab	Add '(opens in new tab)' to text

18 links and buttons have descriptive text

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

https://github.com/wermuind; https://github.com/wermuind; https://github.com/wermuind

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 "ru"

PASS

Lang attribute set to "ru"

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

Got: ru

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+

Mobile-Readable Font Sizes

All 27 visible text node(s) render at >= 12 CSS pixels

PASS

All 27 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
мне `div#__docusaurus_skipToContent_fallback > div.index-description > p > a`
регулярным выражениям `div#__docusaurus_skipToContent_fallback > div.index-description > p > a`

These are opportunities to improve the legibility of your content.

○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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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.

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

○Identical links have the same purpose.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.