Skip to content
https://globalsign.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
45
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
56 headings, 4 skip(s)
FIX
56 headings, 4 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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: H2 → H4 (missing H3)
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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Management and Automation
  • H4 Certificates
  • H4 Compliance
  • H4 Technology Alliances
  • H4 Certificate Management and Automation
  • H4 Document Signing
  • H4 Custom CA/ Private PKI
  • H4 Website & Server Security (SSL/TLS)
  • H4 Access Control & Authentication
  • H4 Client Certificates
  • H5 Become a GlobalSign Partner
  • H5 Our Partners
  • H5 Partner Programs
  • H1 200-day Certificates have Arrived
  • H4 Why manage them manually when automation is available? skipped
  • H1 Secure your website with SSL/TLS Certificates duplicate H1
  • H2 CODE SIGNING Certificate
  • H2 GlobalSign Cygnature - Bulk Signing Solution
  • H2 S-MIME - EMAIL SECURITY SOLUTION
  • H2 Custom CA
  • H1 Secure your website with SSL/TLS Certificates duplicate H1
  • H2 S-MIME - EMAIL SECURITY SOLUTION
  • H2 GlobalSign Cygnature - Bulk Signing Solution
  • H2 IOT Solutions
  • H2 SSL INSPECTION
  • H2 GlobalSign: A Pioneer in Digital Trust Since 1996
  • H4 Cloud Signatures skipped
  • H4 OCSP Requests
  • H4 Certificates
  • H4 Timestamps
  • H3 Atlas
  • H3 Certificate Automation Manager
  • H3 Managed PKI
  • H3 ACME
  • H3 PKI for DevSecOps
  • H3 Document Signing Solutions
  • H3 Secure Email
  • H3 IoT
  • H3 Certificates
  • H2 Join Our Network
  • H5 New Revenue Line skipped
  • H5 Diversity in ecosystem
  • H5 Providing additional opportunities
  • H5 Trusted provider and trusted services
  • H2 Trusted Around the World
  • H2 HotelPlanner.com
  • H2 HotelPlanner.com
  • H2 What Clients Says About Us
  • H4 EXCELLENT BUSINESS SUPPORT SERVICES! skipped
  • H5 Vishvendra Singh
  • H4 APPRECIATE THE SUPPORT RECEIVED!
  • H5 Suraj Lal Gopinadhan
  • H2 GlobalSign website in other languages
  • H2 Purchase Certificates
  • H3 Please confirm the correct Region and Currency for your order.
  • H3 Product Title

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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

D
Form Accessibility
Action
7 of 12 controls have issues
FIX
7 of 12 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <select>; <select name="gs-pricing" id="gs-pricing">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="query">
Info::
5 control(s) properly labeled
12 controls
5 labeled
1 placeholder only
6 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxPreferencesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxStatisticsfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxMarketingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
querytext(Search GlobalSign)placeholder only
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
selectselect(none)none
#gs-pricingselect(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <select>; <select name="gs-pricing" id="gs-pricing">

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="text" name="query">

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

D
Favicon & Branding
Action
5 icon(s) detected
FIX
5 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::
5 navigation landmark(s) detected
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 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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
Alt Text Quality
Action
24 of 62 images have issues
REVIEW
24 of 62 images have issues
Warning::
19 image(s) with filename as alt text
Warning::
5 image(s) with generic alt text
Info::
8 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
62 images 30 good alt text 8 decorative 24 generic
IssueCount
filename19 image(s)
generic5 image(s)
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 Page Not Found :: Page Not Found :: GlobalSign ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 89/100 — 4 failing, 30 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.

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
Continue div.row > div#tpbr_locales > div.select-box > button#submit-gscountry
GCC Login header#header > div.container-fluid > li > a.gaslogin
25+ years as a pioneering Certificate and Identity Authority. div.row > div.col-sm-8 > p.custom-p > a
GlobalSign div.row > div.col-sm-8 > p.custom-p > a
500B div.container-fluid > div.row > div.col-md-3 > p.h1
267M+ div.container-fluid > div.row > div.col-md-3 > p.h1
Speak to an Expert main > div.section-sp > div.container > a.btn
English div.container-fluid > div#footer-language > div.col > a.show-locale-modal
沪ICP备08025378号 div.col-md > div.foot-license > small.icp-license > a

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
Why manage them manually when automation is available? div.bannerImage > div.container > div > h4.text-light
Cloud Signatures div.container-fluid > div.row > div.col-md-3 > h4.h4
New Revenue Line div.row > div.col-lg-3 > div.card > h5.h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
GCC Login div.ccm-page > header#header > div.container-fluid > li

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
EN / United States EN / United Kingdom EN / Europe EN / Scandinavia DE / Deutsc… div.row > div#tpbr_locales > div.select-box > select#gscountry-list

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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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 are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
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 200-day Certificates…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Secure your website …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Secure your website …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CODE SIGNING Certifi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GlobalSign Cygnature…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 S-MIME - EMAIL SECUR…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Custom CA21.00:13.0:1
#000000
#FFFFFF
Pass
h2 S-MIME - EMAIL SECUR…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GlobalSign Cygnature…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 IOT Solutions21.00:13.0:1
#000000
#FFFFFF
Pass
h2 SSL INSPECTION21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GlobalSign: A Pionee…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Join Our Network21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trusted Around the W…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HotelPlanner.com21.00:13.0:1
#000000
#FFFFFF
Pass
h2 HotelPlanner.com21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What Clients Says Ab…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 GlobalSign website i…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Purchase Certificate…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Atlas21.00:13.0:1
#000000
#FFFFFF
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