Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

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 ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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

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 ✗

Link & Button Quality

1 issue(s) across 74 links and 17 buttons

REVIEW

1 issue(s) across 74 links and 17 buttons

5 link(s) open in new tab without warning

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

Got: https://help.awin.com; https://ui.awin.com/idp/en/awin/login; https://www.facebook.com/Awin; https://www.linkedin.com/company/awin-global/; https://www.instagram.com/awin/

1 button(s) with no accessible text

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

Got: button#enableRecite

69 link(s) with descriptive text

74 links

0 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://help.awin.com	Help Center Find clear answer…	new tab	Add '(opens in new tab)' to text
https://ui.awin.com/idp/en/awin/login	Login	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Awin	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/awin-gl…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/awin/	Instagram	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

85 links and buttons have descriptive text

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

https://help.awin.com; https://ui.awin.com/idp/en/awin/login; https://www.facebook.com/Awin; https://www.linkedin.com/company/awin-global/; https://www.instagram.com/awin/

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#enableRecite

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

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

67 headings

PASS

67 headings

Single H1 present

H1 Your growth, your way.
H2 We build opportunities around your goals
H3 Advertisers
H3 Creators & Influencers
H3 Affiliate partners
H3 Agencies
H2 Trusted by 30K+ brands and 1M+ partners worldwide
H3 Adidas
H3 AliExpress
H3 AO
H3 Booking.com
H3 Decathlon
H3 Dyson
H3 Emma
H3 GE Appliances
H3 Groupon
H3 Lovehoney
H3 Lidl
H3 L'Oreal Paris
H3 McGee & Co.
H3 MyProtein
H3 Nike
H3 Samsung
H3 Sephora
H3 SharkNinja
H3 Sixt
H3 Sky
H3 Tui
H3 Under Armour
H3 Uniqlo
H3 Viator
H3 Vodafone
H3 Sephora
H2 The right connections change everything
H3 £15B+
H3 30K+
H3 1M+
H3 25+
H2 Transform your affiliate strategy with industry-leading tools
H2 Think global, boost local, succeed everywhere
H2 Partnerships for every sector
H3 Retail & Shopping
H3 Retail & Shopping
H3 Fashion
H3 Fashion
H3 Travel
H3 Travel
H3 Finance & Insurance
H3 Finance & Insurance
H3 Telecom & Services
H3 Telecom & Services
H2 Real stories. Real results.
H2 Tactical On-Site Tech Partner Delivers +404% Revenue for SharkNinja
H2 Vodafone Gets 2,000 Extra Sales Per Month After Partnering with SaleCycle
H2 Samsung Increases Affiliate Marketing ROI by +67% with Awin Tools
H2 Tactical On-Site Tech Partner Delivers +404% Revenue for SharkNinja
H2 Vodafone Gets 2,000 Extra Sales Per Month After Partnering with SaleCycle
H2 Samsung Increases Affiliate Marketing ROI by +67% with Awin Tools
H2 Tactical On-Site Tech Partner Delivers +404% Revenue for SharkNinja
H2 ThinkTank Americas 2026
H2 Questions? We're here to help
H2 Follow us on social media
H2 Primary Footer Navigation
H3 Solutions
H3 Resources
H3 Company
H2 Secondary Footer Navigation

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

16 decorative image(s) correctly marked

5 image(s) with good alt text

21 images 5 good alt text 16 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#territory-switcher-1	select	Change Territory	for/id
#territory-switcher-2	select	Change Territory	for/id

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)

Element	Ratio	Required	FG	BG	Result
h1 Your growth,	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted by 30K+ bran…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tactical On-Site Tec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vodafone Gets 2,000 …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Samsung Increases Af…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tactical On-Site Tec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vodafone Gets 2,000 …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Samsung Increases Af…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tactical On-Site Tec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Questions? We're her…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Follow us on social …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Primary Footer Navig…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secondary Footer Nav…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Adidas	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 AliExpress	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Booking.com	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Decathlon	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dyson	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Emma	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 GE Appliances	21.00:1	3.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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 32 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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.gap-gutter > article > button.flex > svg.size-8 `section.gap-gutter > article > button.flex > svg.size-8`
section.gap-gutter > article > button.flex > svg.size-8 `section.gap-gutter > article > button.flex > svg.size-8`
section.gap-gutter > article > button.flex > svg.size-8 `section.gap-gutter > article > button.flex > svg.size-8`

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.

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

●Select elements have associated label elements.

●`button`, `link`, and `menuitem` elements have accessible names

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

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

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

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