Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-uyogff

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://aenetworks.tv/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://aenetworks.tv/manifest.json

Manifest contains invalid JSON.

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: #000000

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 ✗

Link & Button Quality

Action

5 issue(s) across 48 links and 23 buttons

REVIEW

5 issue(s) across 48 links and 23 buttons

1 link(s) with no accessible text

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

Got: a#main-content

5 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/company/aenetworksemea/; /terms-and-conditions; https://www.aenetworks.tv/cookie-notice; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/

4 button(s) with no accessible text

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

Got: button (#359 on page); button (#371 on page); button (#387 on page); button (#403 on page)

42 link(s) with descriptive text

48 links

1 empty

0 generic text

5 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
/partnerships	Partnerships	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/aenetwo…	A+E Networks UK on LinkedIn	new tab	Add '(opens in new tab)' to text
/terms-and-conditions	Terms and Conditions	new tab	Add '(opens in new tab)' to text
https://www.aenetworks.tv/cookie-notice	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

61 links and buttons have descriptive text

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

a#main-content

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

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

https://www.linkedin.com/company/aenetworksemea/; /terms-and-conditions; https://www.aenetworks.tv/cookie-notice; https://cookiepedia.co.uk/giving-consent-to-cookies; https://www.onetrust.com/products/cookie-consent/

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 (#359 on page); button (#371 on page); button (#387 on page); button (#403 on page)

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

Favicon & Branding

22 icon(s) detected

REVIEW

22 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 Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 1 pass AA only

h1 Welcome

1.80:1

#000000

#333A37

needs 3.0:1 (large text)

32px · above the fold · over background image/gradient

h2 Our culture

2.61:1

#000000

#4F514B

needs 3.0:1 (large text)

24px · above the fold

h2 Our purpose

1.94:1

#000000

#373F3D

needs 3.0:1 (large text)

24px · mid-page

h2 Partnerships

2.02:1

#000000

#3C413E

needs 3.0:1 (large text)

24px · mid-page

title Hearst Networks EMEA

1.09:1

#000000

#0E0F0E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.50:1

#000000

#2B2C2A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Our Culture

3.42:1

#000000

#5E635E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Our Purpose

2.65:1

#000000

#4B534F

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
h1 Welcome	1.80:1	3.0:1	#000000	#333A37	Fail
h2 Main navigation	3.71:1	3.0:1	#000000	#656863	Pass
h2 Our culture	2.61:1	3.0:1	#000000	#4F514B	Fail
h2 Our purpose	1.94:1	3.0:1	#000000	#373F3D	Fail
h2 Partnerships	2.02:1	3.0:1	#000000	#3C413E	Fail
h2 Careers	4.89:1	3.0:1	#000000	#7A7A7A	Pass
h2 Latest news	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Corporate	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Footer	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Websites	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Footer Websites	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Follow Us	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Cookie Preferences	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Your Cookies Choices…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Manage Consent Prefe…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Vendors List	5.24:1	3.0:1	#000000	#7F7F7F	Pass
title Hearst Networks EMEA	1.09:1	4.5:1	#000000	#0E0F0E	Fail
a Skip to main content	1.50:1	4.5:1	#000000	#2B2C2A	Fail
a Our Culture	3.42:1	4.5:1	#000000	#5E635E	Fail
a Our Purpose	2.65:1	4.5:1	#000000	#4B534F	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.

Landmark Structure

10 landmarks

PASS

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

1 of 4 <nav> elements are unlabeled

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

Skip navigation link present

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

A+

Heading Hierarchy

24 headings

PASS

24 headings

Single H1 present

H2 Main navigation
H1 Welcome
H2 Our culture
H2 Our purpose
H2 Partnerships
H2 Careers
H2 Latest news
H3 HEARST NETWORKS TEAMS WITH SOSA FOR PREDATOR FILES, AN UNDERCOVER INVESTIGATION SERIES ON CRIME+INVESTIGATION
H3 COSMO CELEBRATES WOMEN’S MONTH WITH DEBATE AND ART
H3 HEARST NETWORKS PARTNERS WITH SPIRIT STUDIOS TO LAUNCH DIGITAL-FIRST HISTORY SLATE
H3 HEARST CANVAS ANNOUNCES CREATIVE DIRECTOR APPOINTMENT
H2 Corporate
H2 Footer
H2 Websites
H2 Footer Websites
H2 Follow Us
H2 Cookie Preferences
H2 Your Cookies Choices On This Site
H3 Manage Consent Preferences
H4 Strictly Necessary & Analytics Cookies
H4 Performance Cookies
H4 Functional Cookies
H4 Marketing and Targeting Cookies
H3 Vendors List

A+

Alt Text Quality

1 of 20 images have issues

PASS

1 of 20 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

18 image(s) with good alt text

20 images 18 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 8 controls labeled

PASS

All 8 controls labeled

8 control(s) properly labeled

8 controls

8 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0004	checkbox	Marketing and Targeting Cookies	for/id
#vendor-search-handler	text	Vendor list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 28 passed

PASS

100

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.

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
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link`

○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

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

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

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

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

○Uses ARIA roles only on compatible elements

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