Skip to content
https://verisign.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
F
Form Accessibility
Action
5 of 12 controls have issues
FIX
5 of 12 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="menu-option" id="mobile-menu">; <input type="radio" name="menu-option" id="mobile-search">; <input type="radio" name="menu-option" id="menu-reset">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="vquery">; <input type="search" name="vquery" id="search-menu-input">
Info::
7 control(s) properly labeled
12 controls
7 labeled
2 placeholder only
3 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxAnalytic Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextVendor Searchfor/id
#storage-access-groupcheckboxInformation storage and accessfor/id
#select-all-vendor-leg-handlercheckboxSelect All Vendorsfor/id
#select-all-vendor-groups-handlercheckboxSelect All Vendorsfor/id
#select-all-hosts-groups-handlercheckboxSelect All Hostsfor/id
#search-menu-inputsearch(Site Search)placeholder only
vquerysearch(Site Search)placeholder only
#mobile-menuradio(none)none
#mobile-searchradio(none)none
#menu-resetradio(none)none

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

<input type="radio" name="menu-option" id="mobile-menu">; <input type="radio" name="menu-option" id="mobile-search">; <input type="radio" name="menu-option" id="menu-reset">

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

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

<input type="search" name="vquery">; <input type="search" name="vquery" id="search-menu-input">

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

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::
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
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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 (missing!) NAV 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

B
Heading Hierarchy
29 headings
REVIEW
29 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 About Us
  • H3 What We Do
  • H3 Resources
  • H3 News & Insights
  • H2 Verisign enables the world to connect online with reliability and confidence, anytime, anywhere.
  • H3 A Leader in Internet Infrastructure and Domain Name Registry Services
  • H3 Domain Names
  • H3 DNS Security, Stability, and Resiliency
  • H3 DNS Root Zone Maintainer
  • H2 Committed to Meaningful Community Engagement
  • H2 News
  • H3 blog Preparing DNSSEC for the Post-Quantum Era
  • H3 Verisign to Report First Quarter 2026 Financial Results
  • H3 Data Refutes Short Sellers’ Flawed Reports About Negative Impacts on .Com Domain Name Base
  • H3 Celebrating Verisign CTO Burt Kaliski’s Lifetime Achievement Award
  • H2 Join Our Team and Be a Steward of the Internet
  • H3 RESOURCES
  • H3 DNS EDUCATION
  • H3 INSIGHTS
  • H3 SUPPORT
  • H3 ABOUT US
  • H3 DOMAIN NAMES
  • H3 LANGUAGES
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Analytic Cookies
  • H4 Functional Cookies
  • H3 Performance Cookies

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

A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
12 image(s) with good alt text
13 images 12 good alt text
IssueCount
too long1 image(s)
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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
h2 Verisign enables the…19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Committed to Meaning…19.77:13.0:1
#000000
#F8F8F8
Pass
h2 News19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Join Our Team and Be…19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Privacy Preference C…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 About Us19.77:13.0:1
#000000
#F8F8F8
Pass
h3 What We Do19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Resources19.77:13.0:1
#000000
#F8F8F8
Pass
h3 News & Insights19.77:13.0:1
#000000
#F8F8F8
Pass
h3 A Leader in Internet…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Domain Names19.77:13.0:1
#000000
#F8F8F8
Pass
h3 DNS Security, Stabil…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 DNS Root Zone Mainta…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Preparing DNSSEC for…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Verisign to Report F…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Data Refutes Short S…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 Celebrating Verisign…19.77:13.0:1
#000000
#F8F8F8
Pass
h3 RESOURCES19.77:13.0:1
#000000
#F8F8F8
Pass
h3 DNS EDUCATION19.77:13.0:1
#000000
#F8F8F8
Pass
h3 INSIGHTS19.77:13.0:1
#000000
#F8F8F8
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.

A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 26 passed
PASS
95

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.relative > form#search-menu-form > div.absolute > button div.relative > form#search-menu-form > div.absolute > button

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
●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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○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.
○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.

Send Feedback