Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 6 REVIEW 3 FIX

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

Action

8 headings

REVIEW

8 headings

No H1 heading found

Every page should have one H1 that describes the page content.

2 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 Enhance Your Network
H3 With Hardware That Works Harder
H3 Connectivity
H3 Back to Home App
H3 WinBox
H3 Home App
H3 (empty)
H3 (empty)

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Link & Button Quality

7 issue(s) across 181 links and 20 buttons

REVIEW

7 issue(s) across 181 links and 20 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.mtk-button-icon-navigation (#268 on page); button.size-8 (#883 on page); button.size-8 (#885 on page); button.size-8 (#964 on page); button.size-8 (#966 on page); button.rounded-full (#1146 on page)

180 link(s) with descriptive text

181 links

1 empty

0 generic text

0 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

194 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button.mtk-button-icon-navigation (#268 on page); button.size-8 (#883 on page); button.size-8 (#885 on page); button.size-8 (#964 on page); button.size-8 (#966 on page); button.rounded-full (#1146 on page)

Why this matters

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Enhance Your Network

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 With Hardware That Works Harder

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Connectivity

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Back to Home App

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 WinBox

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Home App

1.25:1

#000000

#10201F

needs 3.0:1 (large text)

19px · bottom of viewport

title MikroTik · Routers …

2.38:1

#000000

#1E5252

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

2.22:1

#000000

#1C4D4D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Hardware

2.25:1

#000000

#1E4E4E

needs 4.5:1 (normal text)

16px · top of page (header area)

a New

2.23:1

#000000

#1F4D4D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Search

2.07:1

#000000

#1C4847

needs 4.5:1 (normal text)

16px · above the fold

a Ethernet routers

2.13:1

#000000

#1E4A49

needs 4.5:1 (normal text)

16px · above the fold

a Switches

1.99:1

#000000

#1C4545

needs 4.5:1 (normal text)

16px · above the fold

a Wireless systems

2.01:1

#000000

#1D4645

needs 4.5:1 (normal text)

16px · above the fold

a Wireless for home and office

1.96:1

#000000

#1D4442

needs 4.5:1 (normal text)

16px · above the fold

a LTE/5G products

1.63:1

#000000

#163736

needs 4.5:1 (normal text)

16px · above the fold

a IoT products

1.60:1

#000000

#173534

needs 4.5:1 (normal text)

16px · above the fold

a 60 GHz products

1.63:1

#000000

#173735

needs 4.5:1 (normal text)

16px · above the fold

a RouterBOARD

1.60:1

#000000

#183534

needs 4.5:1 (normal text)

16px · above the fold

a Enclosures

1.52:1

#000000

#173132

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Enhance Your Network	1.25:1	3.0:1	#000000	#10201F	Fail
h3 With Hardware That W…	1.25:1	3.0:1	#000000	#10201F	Fail
h3 Connectivity	1.25:1	3.0:1	#000000	#10201F	Fail
h3 Back to Home App	1.25:1	3.0:1	#000000	#10201F	Fail
h3 WinBox	1.25:1	3.0:1	#000000	#10201F	Fail
h3 Home App	1.25:1	3.0:1	#000000	#10201F	Fail
title MikroTik …	2.38:1	4.5:1	#000000	#1E5252	Fail
a Skip to main content	2.22:1	4.5:1	#000000	#1C4D4D	Fail
span Hardware	2.25:1	4.5:1	#000000	#1E4E4E	Fail
a New	2.23:1	4.5:1	#000000	#1F4D4D	Fail
a Search	2.07:1	4.5:1	#000000	#1C4847	Fail
a Ethernet routers	2.13:1	4.5:1	#000000	#1E4A49	Fail
a Switches	1.99:1	4.5:1	#000000	#1C4545	Fail
a Wireless systems	2.01:1	4.5:1	#000000	#1D4645	Fail
a Wireless for home an…	1.96:1	4.5:1	#000000	#1D4442	Fail
a LTE/5G products	1.63:1	4.5:1	#000000	#163736	Fail
a IoT products	1.60:1	4.5:1	#000000	#173534	Fail
a 60 GHz products	1.63:1	4.5:1	#000000	#173735	Fail
a RouterBOARD	1.60:1	4.5:1	#000000	#183534	Fail
a Enclosures	1.52:1	4.5:1	#000000	#173132	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+

Alt Text Quality

All 33 images OK

PASS

All 33 images OK

33 image(s) with good alt text

33 images 33 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: MikroTik

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name MikroTik ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name MikroTik Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 21 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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HARDWARE `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
New `div.flex > menu.flex > li > a.transition-colors`
Search `div.flex > menu.flex > li > a.transition-colors`
Ethernet routers `div.flex > menu.flex > li > a.transition-colors`
Switches `div.flex > menu.flex > li > a.transition-colors`
Wireless systems `div.flex > menu.flex > li > a.transition-colors`
Wireless for home and office `div.flex > menu.flex > li > a.transition-colors`
LTE/5G products `div.flex > menu.flex > li > a.transition-colors`
IoT products `div.flex > menu.flex > li > a.transition-colors`
60 GHz products `div.flex > menu.flex > li > a.transition-colors`
RouterBOARD `div.flex > menu.flex > li > a.transition-colors`
Enclosures `div.flex > menu.flex > li > a.transition-colors`
Interfaces `div.flex > menu.flex > li > a.transition-colors`
Accessories `div.flex > menu.flex > li > a.transition-colors`
Antennas `div.flex > menu.flex > li > a.transition-colors`
SFP/QSFP `div.flex > menu.flex > li > a.transition-colors`
SOFTWARE `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
Downloads `div.flex > menu.flex > li > a.transition-colors`
Changelogs `div.flex > menu.flex > li > a.transition-colors`
RouterOS `div.flex > menu.flex > li > a.transition-colors`
WinBox `div.flex > menu.flex > li > a.transition-colors`
Mobile apps `div.flex > menu.flex > li > a.transition-colors`
Back to Home `div.flex > menu.flex > li > a.transition-colors`
Connectivity `div.flex > menu.flex > li > a.transition-colors`
DISTRIBUTORS `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
Buy something (find a distributor) `div.flex > menu.flex > li > a.transition-colors`
Sell something (become a distributor) `div.flex > menu.flex > li > a.transition-colors`
Made for MikroTik `div.flex > menu.flex > li > a.transition-colors`
SUPPORT `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
Documentation `div.flex > menu.flex > li > a.transition-colors`
Consultants `div.flex > menu.flex > li > a.transition-colors`
Forum `div.flex > menu.flex > li > a.transition-colors`
Help `div.flex > menu.flex > li > a.transition-colors`
Security `div.flex > menu.flex > li > a.transition-colors`
Warranty `div.flex > menu.flex > li > a.transition-colors`
TRAINING `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
About `div.flex > menu.flex > li > a.transition-colors`
Schedule `div.flex > menu.flex > li > a.transition-colors`
Training centers & trainers `div.flex > menu.flex > li > a.transition-colors`
Academies `div.flex > menu.flex > li > a.transition-colors`
Train the trainer `div.flex > menu.flex > li > a.transition-colors`
Certificate Search `div.flex > menu.flex > li > a.transition-colors`
ABOUT `div.mtk-content-container > div.grid > div.flex > p.mtk-text-sm`
Contacts `div.flex > menu.flex > li > a.transition-colors`
Company `div.flex > menu.flex > li > a.transition-colors`
Our Logo `div.flex > menu.flex > li > a.transition-colors`
Vacancies `div.flex > menu.flex > li > a.transition-colors`
Privacy Policy `div.flex > menu.flex > li > a.hover:text-white/75`

These are opportunities to improve the legibility of your content.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide #1 `div.flex > div.overflow-hidden > div.absolute > button.bg-black`
Go to slide #2 `div.flex > div.overflow-hidden > div.absolute > button.bg-black`
Go to slide #3 `div.flex > div.overflow-hidden > div.absolute > button.bg-black`

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

●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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

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