Skip to content
https://it.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 NAV MAIN CONTENTINFO (missing!)

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

C
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
h1 Get any name like
1.27:1
#000000
on
#1B1848
needs 3.0:1 (large text)
32px · above the fold
h2 .it.com
1.25:1
#000000
on
#181649
needs 3.0:1 (large text)
24px · above the fold
h2 Why choose it.com?
1.06:1
#000000
on
#070724
needs 3.0:1 (large text)
24px · mid-page
h2 Don't Compromise. Get the name you want…
1.06:1
#000000
on
#070724
needs 3.0:1 (large text)
24px · mid-page
h2 Get a great price on a domain name that …
1.06:1
#000000
on
#070724
needs 3.0:1 (large text)
24px · mid-page
h2 Unsatisfied with your current domain? Ga…
1.13:1
#000000
on
#0F0D37
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
h2 With the .com ending, it.com zones are S…
1.29:1
#000000
on
#1A1753
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get superior website performance with ou…
1.29:1
#000000
on
#1A1753
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your it.com site can be secure and is co…
1.29:1
#000000
on
#1A1753
needs 3.0:1 (large text)
24px · bottom of viewport
title IT.COM
1.14:1
#000000
on
#0F0E38
needs 4.5:1 (normal text)
16px · top of page (header area)
a Blog
1.14:1
#000000
on
#0F0E38
needs 4.5:1 (normal text)
16px · top of page (header area)
a Our team
1.19:1
#000000
on
#16123C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Contacts
1.20:1
#000000
on
#131243
needs 4.5:1 (normal text)
16px · top of page (header area)
a Registrars
1.22:1
#000000
on
#191540
needs 4.5:1 (normal text)
16px · above the fold
span Help
1.24:1
#000000
on
#181547
needs 4.5:1 (normal text)
16px · above the fold
a Log in
1.25:1
#000000
on
#1A1647
needs 4.5:1 (normal text)
16px · above the fold
span yourdomain
1.27:1
#000000
on
#1B174B
needs 4.5:1 (normal text)
16px · above the fold
div .it.com
1.25:1
#000000
on
#1D1741
needs 4.5:1 (normal text)
16px · above the fold
span Why it.com
1.24:1
#000000
on
#1D173D
needs 4.5:1 (normal text)
16px · above the fold
video Video tag not supported.
1.09:1
#000000
on
#0B0B28
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Get any name like1.27:13.0:1
#000000
#1B1848
Fail
h2 .it.com1.25:13.0:1
#000000
#181649
Fail
h2 Why choose it.com?1.06:13.0:1
#000000
#070724
Fail
h2 Don't Compromise. G…1.06:13.0:1
#000000
#070724
Fail
h2 Get a great price on…1.06:13.0:1
#000000
#070724
Fail
h2 Unsatisfied with you…1.13:13.0:1
#000000
#0F0D37
Fail
h2 With the .com ending…1.29:13.0:1
#000000
#1A1753
Fail
h2 Get superior website…1.29:13.0:1
#000000
#1A1753
Fail
h2 Your it.com site can…1.29:13.0:1
#000000
#1A1753
Fail
title IT.COM1.14:14.5:1
#000000
#0F0E38
Fail
a Blog1.14:14.5:1
#000000
#0F0E38
Fail
a Our team1.19:14.5:1
#000000
#16123C
Fail
a Contacts1.20:14.5:1
#000000
#131243
Fail
a Registrars1.22:14.5:1
#000000
#191540
Fail
span Help1.24:14.5:1
#000000
#181547
Fail
a Log in1.25:14.5:1
#000000
#1A1647
Fail
span yourdomain1.27:14.5:1
#000000
#1B174B
Fail
div .it.com1.25:14.5:1
#000000
#1D1741
Fail
span Why it.com1.24:14.5:1
#000000
#1D173D
Fail
video Video tag not suppor…1.09:14.5:1
#000000
#0B0B28
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 25 passed
REVIEW
89

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
We use cookies and other tracking technologies to improve your browsing experie… body > div#termsfeed-pc1-notice-banner

These are opportunities to improve the usage of ARIA in your application which 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
I Agree div.termsfeed-pc1-notice-banner-inner > div.termsfeed-pc1-notice-banner-footer > div.termsfeed-pc1-notice-banner-buttons > button#termsfeed_privacy_consent_banner_button_accept_all

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > span#webby-pv-2014-bug > iframe body > span#webby-pv-2014-bug > iframe

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.

○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
●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 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
●No element has a `[tabindex]` value greater than 0
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○`<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
○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.
○Skip links are focusable.
○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
○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.
○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.
A+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Get any name like
  • H2 yourdomain.it.com
  • H2 Why choose it.com?
  • H2 Don't Compromise. Get the name you want with it.com.
  • H2 Get a great price on a domain name that still ends with .com.
  • H2 Unsatisfied with your current domain? Gain global recognition with an it.com domain.
  • H2 With the .com ending, it.com zones are SEO-friendly.
  • H2 Get superior website performance with our robust DNS infrastructure.
  • H2 Your it.com site can be secure and is compatible with all SSL certificates.
A+
Alt Text Quality
All 19 images OK
PASS
All 19 images OK
Info::
19 image(s) with good alt text
19 images 19 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputtextnone
#g-recaptcha-responsetextarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response">

Why this matters

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

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

Send Feedback