Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

13 issue(s) across 155 links and 1 buttons

FIX

13 issue(s) across 155 links and 1 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#responsive-navi-button; a#seachbar-responsive-toggle

10 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/sell-domains/it-pays-to-sell-at-sedo/ ("Learn more"); /us/buy-domains/ai-domains/?itm_medium=Display&itm_campaign=BuyDomains&itm_so… ("Learn more"); /us/sell-domains/buy-it-now-domains/ ("Learn more")

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://faq-us.sedo.com/app/answers/detail/a_id/651/kw/payment%20method; https://www.paypal.com/us/selfhelp/home; https://www.united-internet.de/en.html; https://www.internetcommerce.org/; https://x.com/sedo; https://www.facebook.com/sedo; https://www.instagram.com/sedodomains/; https://www.youtube.com/user/SedoGmbH

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button#search-submit

135 link(s) with descriptive text

155 links

2 empty

10 generic text

8 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/about-us/case-studies/	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Case Studies
/us/sell-domains/it-pays-to-sell-at-sedo…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: It Pays To Sell At Sedo
/us/buy-domains/ai-domains/?itm_medium=D…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: ?Itm Medium=Display&Itm Campaign=Buydomains&Itm Source=Home&Itm Content=Ai Lander&Itm Term=Us
/us/sell-domains/buy-it-now-domains/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Buy It Now Domains
https://faq-us.sedo.com/app/answers/deta…	variety of payment options	new tab	Add '(opens in new tab)' to text
https://www.paypal.com/us/selfhelp/home	PayPal	new tab	Add '(opens in new tab)' to text
https://www.united-internet.de/en.html	United Internet	new tab	Add '(opens in new tab)' to text
https://www.internetcommerce.org/	Internet Commerce Association …	new tab	Add '(opens in new tab)' to text
https://x.com/sedo	twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/sedo	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/sedodomains/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/SedoGmbH	YouTube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

135 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#responsive-navi-button; a#seachbar-responsive-toggle

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/about-us/case-studies/ ("Read more"); /us/sell-domains/it-pays-to-sell-at-sedo/ ("Learn more"); /us/buy-domains/ai-domains/?itm_medium=Display&itm_campaign=BuyDomains&itm_so… ("Learn more"); /us/sell-domains/buy-it-now-domains/ ("Learn more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://faq-us.sedo.com/app/answers/detail/a_id/651/kw/payment%20method; https://www.paypal.com/us/selfhelp/home; https://www.united-internet.de/en.html; https://www.internetcommerce.org/; https://x.com/sedo; https://www.facebook.com/sedo; https://www.instagram.com/sedodomains/; https://www.youtube.com/user/SedoGmbH

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button#search-submit

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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: #0060a9

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

7 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 7 <nav> element(s)

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.

Landmark Structure

12 landmarks

REVIEW

12 landmarks

<main> landmark present

7 <nav> landmark(s) found

7 of 7 <nav> elements are unlabeled

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

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

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

Heading Hierarchy

Action

22 headings, 1 skip(s)

REVIEW

22 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

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

H3 Showcase Domains
H3 Auctions ending soon
H3 Top Domains
H2 Sedo is perfect for Domain Buyers ...
H2 ... and Domain Sellers
H2 KIK
H2 Lars Nierfeld, Managing Director
H2 HOW IT WORKS
H3 How do I find a domain?
H3 How do I buy a domain?
H3 How much does it cost?
H2 Global market leader
H2 Secure purchase
H2 Individual consultation
H2 More about Sedo
H4 News about the company and the domain market skipped
H3 About Sedo
H3 Market trends
H4 Additional information
H3 Case Studies
H3 FAQs
H3 Subscribe to newsletter

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

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

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Sedo

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name Sedo ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Name Sedo Display Mode standalone Theme Color #0060a9 Background Color #0060a9 Icons 2 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 5 fail WCAG AA

REVIEW

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

15 pass 5 fail WCAG AA

title Buy. Park. Sell. Domains | Sedo - World'…

1.77:1

#000000

#32383D

needs 4.5:1 (normal text)

16px · top of page (header area)

label Your Keyword

1.77:1

#000000

#32383D

needs 4.5:1 (normal text)

16px · top of page (header area)

span Login

1.35:1

#000000

#1E252B

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span My Sedo

1.04:1

#000000

#000810

needs 4.5:1 (normal text)

16px · top of page (header area)

span Username

1.02:1

#000000

#000309

needs 4.5:1 (normal text)

16px · above the fold

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)

Element	Ratio	Required	FG	BG	Result
h2 Sedo is perfect for …	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 ... and Domain Selle…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Lars Nierfeld, Manag…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 HOW IT WORKS	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Global market leader	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Secure purchase	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 Individual consultat…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h2 More about Sedo	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 How do I find a doma…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 How do I buy a domai…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 How much does it cos…	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 About Sedo	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Market trends	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 Case Studies	19.26:1	3.0:1	#000000	#F5F5F5	Pass
h3 FAQs	19.26:1	3.0:1	#000000	#F5F5F5	Pass
title Buy. Park. Sell. Dom…	1.77:1	4.5:1	#000000	#32383D	Fail
label Your Keyword	1.77:1	4.5:1	#000000	#32383D	Fail
span Login	1.35:1	4.5:1	#000000	#1E252B	Fail
span My Sedo	1.04:1	4.5:1	#000000	#000810	Fail
span Username	1.02:1	4.5:1	#000000	#000309	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.

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-input	search	Your Keyword	for/id
#footer-newsletter-signup-checkbox	checkbox	Yes, I would like to receive regular email updates on Sedo product news, discounts, promotions and domain news. I can unsubscribe at any time using the unsubscribe link in the respective newsletter.	for/id
#footer-newsletter-email	email	Email	for/id

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 28 passed

PASS

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.

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
News about the company and the domain market `div.ce-list-boxes-cta > div.list-boxes-item > div.header > h4`

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
449 USD `ul > li > span.offer > a`
variety of payment options `div.ce-textimage-ver > div.ce-text-bottom > p > a`
domain brokerage service `div.ce-textimage-ver > div.ce-text-bottom > p > a.internal-link`

These are opportunities to improve the legibility of your content.

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.t3-content-fullwidth > div.ce-wrapper > div.ce-content-teaser-multigrid > a.box-left `div.t3-content-fullwidth > div.ce-wrapper > div.ce-content-teaser-multigrid > a.box-left`
div.t3-content-fullwidth > div.ce-wrapper > div.ce-content-teaser-multigrid > a.box-right `div.t3-content-fullwidth > div.ce-wrapper > div.ce-content-teaser-multigrid > a.box-right`

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

●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

●`[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

●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.

●`[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 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

○Form elements have associated labels

○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.

○`<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.

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