Skip to content
https://no-ip.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Alt Text Quality
Action
5 of 51 images have issues
FIX
5 of 51 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 decorative image(s) correctly marked
Info::
45 image(s) with good alt text
51 images 45 good alt text 1 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) 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::
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 Missing
✓ 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
Theme color only
FIX
Theme color only
Info::
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: #8fbe00
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 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.

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.
C
Heading Hierarchy
Action
83 headings, 3 skip(s)
REVIEW
83 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H6 Your browser is out of date!
  • H5 Free Dynamic DNS
  • H5 Enhanced Dynamic DNS
  • H5 Pro Dynamic DNS
  • H5 Branded Remote Access
  • H5 Plus Managed DNS
  • H5 Premium Managed DNS
  • H5 Squared Backup DNS
  • H5 Domain Search
  • H5 Branded Email
  • H5 SSL Certificates
  • H5 DNS for Domain Management
  • H5 Priority Support
  • H5 Team Login
  • H5 Anonymous VPN
  • H5 Referral Program
  • H5 Managed Service Provider (MSP/MSSP)
  • H5 Managed IT/Consultant
  • H5 Internal IT for SME
  • H5 Developer/Engineer
  • H5 OEM
  • H5 Software Provider (SaaS)
  • H5 Security & Alarm Integrator
  • H5 Smart Home Integrator
  • H5 ISP
  • H5 Manage My Client’s Networks
  • H5 Remotely access my network/device
  • H5 Register my domain
  • H5 Configure my DNS
  • H5 Send/receive email
  • H5 VPN access to dynamic networks
  • H5 Access CCTV/IP Cameras
  • H5 A gamer
  • H5 My family's tech support
  • H5 DIY tech guru
  • H5 Concerned about my privacy/security
  • H5 Access device(s) on my home network
  • H5 Access CCTV/IP Cameras
  • H5 Register my domain
  • H5 Share my gaming server
  • H5 Receive email on my personal domain
  • H5 DDNS Keys
  • H5 Integrate
  • H5 API Documents
  • H5 Download Agent/Update Client
  • H5 Check My Port Forwarding
  • H5 Blog
  • H5 FAQs
  • H5 Support
  • H5 Knowledge Base
  • H5 Getting Started
  • H5 Pricing
  • H5 About Us
  • H5 Careers
  • H5 Contact Us
  • H5 Press & Media
  • H1 Smarter DNS Starts Here
  • H4 Create Your Free Hostname Now skipped
  • H2 Dynamic DNS
  • H2 Managed DNS
  • H2 Domain Registration
  • H2 How Customers Use No-IP
  • H3 Manage Multi-Location Networks
  • H3 Perform System Administration
  • H3 Security and Alarm Monitoring
  • H3 Access Your Home Network
  • H3 Monitor Security Cameras
  • H3 Set Up a Gaming Server
  • H2 What is DDNS?
  • H2 What is Managed DNS?
  • H2 Free Personal DDNS Account
  • H2 Let’s Talk Business
  • H2 Why Choose No-IP as Your DNS Provider?
  • H3 Easy Setup for Everyone
  • H3 100% Uptime
  • H3 Comprehensive Support
  • H5 Seamlessly Integrated with Your Favorite Tools skipped
  • H2 Partners & Resellers
  • H2 No-IP News & Knowledge
  • H2 Welcome to Uncomplicated Connectivity
  • H2 100% Uptime Guaranteed
  • H2 Do you need help?
  • H5 Join Our Mailing List skipped

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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 404 - Page Not Found - No-IP ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 26 passed
REVIEW
87

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
SPRING20 section#banner-nav-wrap > div.container > p.mb-0 > span.green
Get No-IP for Free div.col-lg-6 > div.row > div.col-12 > a.btn
Sign Up fieldset#host-add-form > div.control-group > div.col-md-3 > button.btn
Get Remote Access div.col-lg > div.p-4 > div.d-flex > a.text-primary
Empower Your Network div.col-lg > div.p-4 > div.d-flex > a.text-primary
Find Your Domain div.col-lg > div.p-4 > div.d-flex > a.text-primary
Home ul#pills-tab > li.nav-item > button#pills-home-tab > span.d-flex
Learn More div.row > div.col-lg-4 > div.rounded-4 > a.text-primary
Learn More div.row > div.col-lg-4 > div.rounded-4 > a.text-primary
Learn More div.row > div.col-lg-4 > div.rounded-4 > a.text-primary
All Solutions for Business section.pb-7 > div.row > div.col-12 > a.btn
All Solutions for Personal Use section.pb-7 > div.row > div.col-12 > a.btn
35M+ div.col-md-3 > div.d-flex > div.row > span.text-center
25+ div.col-md-3 > div.d-flex > div.row > span.text-center
90%+ div.col-md-3 > div.d-flex > div.row > span.text-center
150+ div.col-md-3 > div.d-flex > div.row > span.text-center
Sign Up for Free div.col-lg > div.row > div.gap-5 > a.btn
Reach Out To Us div.col-lg > div.row > div.gap-5 > a.btn
Support Center div.rounded-4 > div.d-flex > p.flex-grow-1 > a.text-info
Learn More div.container > div.row > div.col-12 > a.btn
Learn More div.container > div.row > div.col-lg-4 > a.btn
Free Personal Account div.row > div.col-lg-8 > div.d-flex > a.btn
Business Inquiry div.row > div.col-lg-8 > div.d-flex > a.btn
Talk to an Expert div.row > div.col-lg-12 > div.d-flex > a.btn

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Create Your Free Hostname Now div.container > div.row > div.col-md-4 > h4.fs-5
Seamlessly Integrated with Your Favorite Tools section#content > section.bg-tertiary_50 > div.container-fluid > h5.mb-6

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.container-lg > div.d-flex > div.dropdown > a.d-flex div.container-lg > div.d-flex > div.dropdown > a.d-flex

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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>`
●`[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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●Select elements have associated label elements.
●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
●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.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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 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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○`<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.
○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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV "Main Navbar" MAIN CONTENTINFO footer

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

A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#hostnametextHostnamefor/id
#domainselectSelect a Domainaria-label
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
h1 Smarter DNS Starts H…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Dynamic DNS20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Managed DNS20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Domain Registration20.82:13.0:1
#000000
#FEFEFE
Pass
h2 How Customers Use No…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 What is DDNS?20.82:13.0:1
#000000
#FEFEFE
Pass
h2 What is Managed DNS?20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Free Personal DDNS A…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Let’s Talk Busines…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Why Choose No-IP as …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Partners & Resellers20.82:13.0:1
#000000
#FEFEFE
Pass
h2 No-IP News & Knowled…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Welcome to Uncomplic…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 100% Uptime Guarante…20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Do you need help?20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Manage Multi-Locatio…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Perform System Admin…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Security and Alarm M…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Access Your Home Net…20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Monitor Security Cam…20.82:13.0:1
#000000
#FEFEFE
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