Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://tucows.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://tucows.com/manifest.json

Manifest contains invalid JSON.

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 ✗

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 Whoops! Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

title Tucows | Making the Internet Better Sinc…

2.58:1

#000000

#0019FF

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

2.58:1

#000000

#0019FF

needs 4.5:1 (normal text)

16px · top of page (header area)

div About us

2.58:1

#000000

#0019FF

needs 4.5:1 (normal text)

16px · top of page (header area)

a Overview

2.58:1

#000000

#0019FF

needs 4.5:1 (normal text)

16px · top of page (header area)

a Leadership

2.58:1

#000000

#0019FF

needs 4.5:1 (normal text)

16px · above the fold

a History

1.97:1

#000000

#0013CD

needs 4.5:1 (normal text)

16px · above the fold

a Inclusion

1.76:1

#000000

#0011B7

needs 4.5:1 (normal text)

16px · above the fold

div Investors

1.76:1

#000000

#0011B7

needs 4.5:1 (normal text)

16px · above the fold

a Overview

1.76:1

#000000

#0011B7

needs 4.5:1 (normal text)

16px · above the fold

a News

1.76:1

#000000

#0011B7

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Making the Internet …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What we do	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Who we are	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How we’re doing	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our businesses	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 #LifeAtTucows	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join the Herd	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Investors	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Tucows \| Making the …	2.58:1	4.5:1	#000000	#0019FF	Fail
a Skip to main content	2.58:1	4.5:1	#000000	#0019FF	Fail
div About us	2.58:1	4.5:1	#000000	#0019FF	Fail
a Overview	2.58:1	4.5:1	#000000	#0019FF	Fail
a Leadership	2.58:1	4.5:1	#000000	#0019FF	Fail
a History	1.97:1	4.5:1	#000000	#0013CD	Fail
a Inclusion	1.76:1	4.5:1	#000000	#0011B7	Fail
div Investors	1.76:1	4.5:1	#000000	#0011B7	Fail
a Overview	1.76:1	4.5:1	#000000	#0011B7	Fail
a News	1.76:1	4.5:1	#000000	#0011B7	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+

Landmark Structure

9 landmarks

PASS

9 landmarks

<main> landmark present

5 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

10 headings

PASS

10 headings

Single H1 present

H1 Making the Internet better.
H2 What we do
H2 Who we are
H2 How we’re doing
H2 Our businesses
H2 #LifeAtTucows
H2 Join the Herd
H2 About us
H2 Company
H2 Investors

A+

Alt Text Quality

All 10 images OK

PASS

All 10 images OK

4 decorative image(s) correctly marked

6 image(s) with good alt text

10 images 6 good alt text 4 decorative

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.

Link & Button Quality

61 links, 0 buttons — all OK

PASS

61 links, 0 buttons — all OK

9 link(s) open in new tab without warning

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

Got: https://tucowsdomains.com/; https://ting.com; https://www.wavelo.com/; https://www.linkedin.com/feed/hashtag/?keywords=lifeattucows; https://ca.linkedin.com/company/tucows; https://www.instagram.com/tucows/; https://www.facebook.com/tucowsinc/; https://twitter.com/tucows; https://tucowsdomains.com/

52 link(s) with descriptive text

61 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://tucowsdomains.com/	Tucows Domains is the world’…	new tab	Add '(opens in new tab)' to text
https://ting.com	Fiber Internet service provide…	new tab	Add '(opens in new tab)' to text
https://www.wavelo.com/	The future of telecom is event…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/feed/hashtag/?k…	#LifeAtTucows (Opens in a new …	new tab	Add '(opens in new tab)' to text
https://ca.linkedin.com/company/tucows	LinkedIn (Opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/tucows/	Instagram (Opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/tucowsinc/	Facebook (Opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://twitter.com/tucows	Twitter (Opens in a new tab)	new tab	Add '(opens in new tab)' to text
https://tucowsdomains.com/	Looking for Tucows Domains? (O…	new tab	Add '(opens in new tab)' to text

52 links and buttons have descriptive text

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

https://tucowsdomains.com/; https://ting.com; https://www.wavelo.com/; https://www.linkedin.com/feed/hashtag/?keywords=lifeattucows; https://ca.linkedin.com/company/tucows; https://www.instagram.com/tucows/; https://www.facebook.com/tucowsinc/; https://twitter.com/tucows; https://tucowsdomains.com/

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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 30 passed

PASS

100

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.

○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

●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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

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

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

●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

●`<frame>` or `<iframe>` elements have a title

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

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

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Buttons have an accessible name

○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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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