Skip to content
https://www.godaddy.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Color Contrast (Screenshot)
Action
5 text elements analyzed, 1 fail WCAG AA
REVIEW

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

4 pass 1 fail WCAG AA
p https://errors.edgesuite.net/18.e7d0dd17…
4.30:1
#000000
on
#717171
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

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 (5)
ElementRatioRequiredFGBGResult
h1 Access Denied21.00:13.0:1
#000000
#FFFFFF
Pass
title Access Denied21.00:14.5:1
#000000
#FFFFFF
Pass
body You don't have permi…21.00:14.5:1
#000000
#FFFFFF
Pass
p Reference #18.e7d0dd…21.00:14.5:1
#000000
#FFFFFF
Pass
p https://errors.edges…4.30:14.5:1
#000000
#717171
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 82/100 — 6 failing, 25 passed
REVIEW
82

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
網域 網站 電子郵件 主機服務 行銷 安全性 Airo™ 人工智慧生成器 價格 nav#id-undefined > div.hf-f12b4q9y > div.hf-p665c1r > ul.hf-ccvky1n
建站神器 免費網站只是第一步而已 免費開始使用 瞭解更多資訊 無需信用卡。** section#id-5zYWWSD1CyX1UdkaEZ2Ji8 > div.pl-c1bk26ci > div.rotating-marquee-content > div#marquee-5zYWWSD1CyX1UdkaEZ2Ji8-content-1

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.

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.controls > div.pl-cyg195d > div.pl-c11zr02g > button.ux-text div.controls > div.pl-cyg195d > div.pl-c11zr02g > button.ux-text
div.controls > div.pl-cyg195d > div.pl-c11zr02g > button.ux-text div.controls > div.pl-cyg195d > div.pl-c11zr02g > button.ux-text
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy div.pl-rk0vnz4 > div.lazy-bg > div.overlay > button.pl-t16f7avy
body.ux-app > div#dc-messaging-bottom-right > div > button.sc-hLseeT body.ux-app > div#dc-messaging-bottom-right > div > button.sc-hLseeT

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
button.sc-hLseeT > div.sc-eDDNvO > div > img button.sc-hLseeT > div.sc-eDDNvO > div > img

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.

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
通用服務條款 div#id-undefined > div.hf-tc8x3it > p > 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
GoDaddy 如何幫助小型企業主追求商業成功呢？ div.pl-f8v5nqw > details#id-7hvTvqqUtYV5UC9idjwrTf > summary.textHeading > h3

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
HKD HK$ div.hf-s1k1dnfs > div#id-currencySelector > div.hf-taml8l2 > button#currentCurrency
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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 are distinguishable without relying on color.
●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.
●Skip links are focusable.
●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
○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 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
○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
○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.
○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
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 Access Denied
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback