Skip to content
https://tomsk.ru

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 MAIN (missing!) CONTENTINFO footer

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

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 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

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="s">; <input type="text" name="s">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
stext(Поиск)placeholder only
stext(Поиск)placeholder only

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

<input type="text" name="s">; <input type="text" name="s">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Страница не найдена — TOMSK.RU ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 18 passed
REVIEW
83

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.

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
div.row > div.col-12 > form.search-form > button.search-form__submit div.row > div.col-12 > form.search-form > button.search-form__submit

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.post-asd > div#on_ads_bloc7780531 > span.on_banner_div > a div.post-asd > div#on_ads_bloc7780531 > span.on_banner_div > a
div.post-asd > div#on_ads_bloc4727000 > span.on_banner_div > a div.post-asd > div#on_ads_bloc4727000 > span.on_banner_div > 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.

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
Культура div.top-post > div.top-post__info > div.post-item__categories > a
20:05 / 22.04.26 div.post-item-wrap > div.top-post > div.top-post__info > div.post-item__time
22:15 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
21:01 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
20:05 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
19:06 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
18:01 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
17:00 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
16:30 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
16:10 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
15:30 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
15:00 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
14:40 / 22.04.26 div.main__side > div.post-links > div.post-links__item > div.post-links__date
Все новости div.post-links > div.post-links__item > a.post-links__link > strong
19:10 / 14.04.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
21:10 / 13.04.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
17:10 / 24.03.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
09:10 / 23.03.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
16:40 / 18.03.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
10:00 / 27.02.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
14:40 / 26.02.26 div.main__partners > div.post-links > div.post-links__item > div.post-links__date
Культура div.post-item > div.post-item__info > div.post-item__categories > a
20:05 / 22.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Актуальное div.post-item > div.post-item__info > div.post-item__categories > a
17:00 / 22.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Общество div.post-item > div.post-item__info > div.post-item__categories > a
16:30 / 22.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Дороги div.post-large > div.post-large__info > div.post-item__categories > a
Томск. История div.post-large > div.post-large__info > div.post-item__categories > a
Природа div.post-item > div.post-item__info > div.post-item__categories > a
13:00 / 22.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Паводок в Томской области div.post-item > div.post-item__info > div.post-item__categories > a
10:07 / 22.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Перекрытия div.post-item > div.post-item__info > div.post-item__categories > a
22:01 / 21.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Отключения div.post-item > div.post-item__info > div.post-item__categories > a
20:12 / 21.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Наука div.post-item > div.post-item__info > div.post-item__categories > a
19:00 / 21.04.26 div.col-lg-4 > div.post-item > div.post-item__info > div.post-item__time
Учредитель ООО «Дайджест ТВ». Св-во о регистрации СМИ ЭЛ №ФС 77-71671 выдано Фе… div.container > div.row > div.col-lg-3 > div.copy
Разделы div.row > div.col-lg-auto > div.footer__widget > div.footer__widget-title
Документация div.row > div.col-lg-auto > div.footer__widget > div.footer__widget-title
© 1997 – 2026 Городской портал Томск.ру. Функционирует при финансовой поддержке… div.container > div.row > div.col-auto > div.copy-text
Cookie body.home > div#clearfy-cookie > div.clearfy-cookie-container > a
Политикой конфиденциальности body.home > div#clearfy-cookie > div.clearfy-cookie-container > a
Пользовательским соглашением body.home > div#clearfy-cookie > div.clearfy-cookie-container > a
OK body.home > div#clearfy-cookie > div.clearfy-cookie-container > button#clearfy-cookie-accept

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.

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>`
●`[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
●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
●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.
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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 have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`<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 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
○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.
○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
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
5 image(s) with alt text over 125 characters
Info::
3 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
17 images 9 good alt text 3 decorative
IssueCount
too long5 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title Новостной …21.00:14.5:1
#000000
#FFFFFF
Pass
a Новости21.00:14.5:1
#000000
#FFFFFF
Pass
a Проекты18.76:14.5:1
#000000
#F2F2F2
Pass
a Погода18.76:14.5:1
#000000
#F2F2F2
Pass
a Культура18.76:14.5:1
#000000
#F2F2F2
Pass
a Комедийный…18.76:14.5:1
#000000
#F2F2F2
Pass
div 20:05 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a Томский Ро…18.76:14.5:1
#000000
#F2F2F2
Pass
div 22:15 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a В Томской о…18.76:14.5:1
#000000
#F2F2F2
Pass
div 21:01 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a Комедийный…18.76:14.5:1
#000000
#F2F2F2
Pass
div 20:05 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a 9 Мая в Томс…18.76:14.5:1
#000000
#F2F2F2
Pass
div 19:06 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a В томском «…18.76:14.5:1
#000000
#F2F2F2
Pass
div 18:01 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a Сибирский …18.76:14.5:1
#000000
#F2F2F2
Pass
div 17:00 / 22.04.2618.76:14.5:1
#000000
#F2F2F2
Pass
a В Томске 26 …18.76:14.5:1
#000000
#F2F2F2
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.

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

Send Feedback