Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 3 REVIEW 9 FIX

Landmark Structure

Action

1 landmarks

FIX

1 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

No contentinfo (footer) landmark

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

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

Alt Text Quality

Action

10 of 51 images have issues

FIX

10 of 51 images have issues

10 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

8 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 decorative image(s) correctly marked

39 image(s) with good alt text

51 images 39 good alt text 2 decorative 10 missing

Issue	Count
missing	10 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

15 issue(s) across 107 links and 158 buttons

FIX

15 issue(s) across 107 links and 158 buttons

12 link(s) with no accessible text

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

Got: /; /; /the-human-body/; /; https://www.ourmediashop.com/bbc-science-focus-magazine-EAST26BRA?utm_source=…; /; https://www.facebook.com/sciencefocus; https://twitter.com/sciencefocus; https://www.instagram.com/bbcsciencefocus/; https://www.pinterest.co.uk/ScienceFocus/ (+2 more)

3 button(s) with no accessible text

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

Got: button.mat-ripple (#266 on page); button (#278 on page); button (#282 on page)

95 link(s) with descriptive text

107 links

12 empty

0 generic text

0 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
/the-human-body/	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
advertisement-feature/heres-what-school-…	Here's what school examiners d…	img no alt	Add alt attribute to the image
https://www.ourmediashop.com/bbc-science…	(empty)	empty	Add link text or aria-label
space/artemis-ii-in-pictures-21-jaw-drop…	Artemis II in pictures: 21 jaw…	img no alt	Add alt attribute to the image
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/sciencefocus	(empty)	empty	Add link text or aria-label
https://twitter.com/sciencefocus	(empty)	empty	Add link text or aria-label
https://www.instagram.com/bbcsciencefocu…	(empty)	empty	Add link text or aria-label
https://www.pinterest.co.uk/ScienceFocus…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/channel/UCS0P18F…	(empty)	empty	Add link text or aria-label
https://feeds.purplemanager.com/193c804a…	(empty)	empty	Add link 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

250 links and buttons have descriptive text

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

/; /; /the-human-body/; /; https://www.ourmediashop.com/bbc-science-focus-magazine-EAST26BRA?utm_source=…; /; https://www.facebook.com/sciencefocus; https://twitter.com/sciencefocus; https://www.instagram.com/bbcsciencefocus/; https://www.pinterest.co.uk/ScienceFocus/ (+2 more)

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

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

button.mat-ripple (#266 on page); button (#278 on page); button (#282 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

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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ 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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Heading Hierarchy

46 headings

REVIEW

46 headings

No H1 heading found

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

H3 We could be on the brink of total internet collapse. And there may only be months to stop it
H3 Narcissism shows differently in men and women. Here’s how to spot it
H3 This radical 'dark stars' theory could solve our Universe’s greatest mystery
H3 Here's what school examiners do that AI never could
H3 This is what a near-death experience actually feels like
H3 New issue: What really causes autism?
H3 7 small changes that will significantly cut your risk of heart disease
H3 Top 10 most dangerous animals in the world
H3 Two supermassive black holes are now heading for a Universe-shaking collision
H3 We’re losing 338 spoken words every day
H2 Top reads
H3 121 random fun facts that will blow your mind
H3 8 techniques all anxious people should use, according to a psychologist
H3 44 cool gadgets: Our pick of the best new tech for 2025
H2 Science news
H3 Monkeys have found a bizarre natural supplement to counteract human junk food
H3 The end of sex? How human reproduction could soon change forever
H3 Scientists have just mapped all the nerves of the clitoris for the first time
H3 A mega-building in China is now so large that it's slowing Earth's spin
H3 Monkeys have found a bizarre natural supplement to counteract human junk food
H3 The end of sex? How human reproduction could soon change forever
H3 Scientists have just mapped all the nerves of the clitoris for the first time
H3 A mega-building in China is now so large that it's slowing Earth's spin
H2 Future technology
H3 10 of the world's worst-ever inventions
H3 10 ingenious inventions about to change our world forever
H3 Your reality really could be a simulation, say experts. Here’s why
H3 The hidden reason new 'superfast' Wi-Fi still feels anything but
H2 Instant Genius Podcast
H3 Instant Genius Podcast | Do you have synaesthesia? Why some of us can taste words
H3 Instant Genius Podcast | Why you’re not actually addicted to your phone
H3 Instant Genius Podcast | How personalised medicine is about to change healthcare forever
H2 Your questions answered
H3 How identical are identical twins?
H3 Meet the weird worm that can survive being boiled alive
H3 Could I build a nuclear reactor in my shed?
H3 Why do I keep seeing faces in everything?
H3 What's the craziest thing ever stolen?
H3 What is a skyquake?
H2 Science photo galleries
H3 Artemis II in pictures: 21 jaw-dropping photos, from launch to splashdown
H3 Top 10 most dangerous roads in the world 2026
H3 Artemis II: 21 historic images of the stunning Moon mission launch
H3 31 jaw-dropping space photos that will change how you see the Universe
H3 15 of the world's weirdest-ever inventions
H3 The top 10 fastest jets in the world 2025

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

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 6 pass AA only

title BBC Science Focus Magazine - science, na…

2.82:1

#000000

#555556

needs 4.5:1 (normal text)

16px · top of page (header area)

span Anmelden

2.82:1

#000000

#555556

needs 4.5:1 (normal text)

16px · top of page (header area)

span Anmelden

2.82:1

#000000

#555556

needs 4.5:1 (normal text)

16px · top of page (header area)

span Abonnement

2.82:1

#000000

#555556

needs 4.5:1 (normal text)

16px · top of page (header area)

span Käufe wiederherstellen (tbd.)

2.82:1

#000000

#555556

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Top reads	3.00:1	3.0:1	#000000	#595959	Pass
h2 Science news	3.00:1	3.0:1	#000000	#595959	Pass
h2 Future technology	3.00:1	3.0:1	#000000	#595959	Pass
h2 Instant Genius Podca…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Your questions answe…	3.00:1	3.0:1	#000000	#595959	Pass
h2 Science photo galler…	3.00:1	3.0:1	#000000	#595959	Pass
title BBC Science Focus Ma…	2.82:1	4.5:1	#000000	#555556	Fail
span Anmelden	2.82:1	4.5:1	#000000	#555556	Fail
span Anmelden	2.82:1	4.5:1	#000000	#555556	Fail
span Abonnement	2.82:1	4.5:1	#000000	#555556	Fail
span Käufe wiederherstel…	2.82:1	4.5:1	#000000	#555556	Fail
span Lokalregion wählen …	7.38:1	4.5:1	#000000	#99999A	Pass
span Rechtliches	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Datenschutz	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Impressum	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Kontakt	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Feedback	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Bookmarks	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span E-Paper	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Info/Contact	21.00:1	4.5: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.

Lighthouse Accessibility Audits

Score 86/100 — 3 failing, 22 passed

REVIEW

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.

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
storefront-section.header-mobile-left-elements > storefront-element > storefront-button.menu-icon-button > button.mat-ripple `storefront-section.header-mobile-left-elements > storefront-element > storefront-button.menu-icon-button > button.mat-ripple`
storefront-section.header-mobile-right-elements > storefront-element > storefront-button.user > button `storefront-section.header-mobile-right-elements > storefront-element > storefront-button.user > button`
storefront-section.header-mobile-right-elements > storefront-element > storefront-button.search > button `storefront-section.header-mobile-right-elements > storefront-element > storefront-button.search > button`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`
ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text `ul.menu-content > li.menu-item > storefront-button.menu-button > button.has-text`

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
storefront-element > storefront-html.home-banner > a > img `storefront-element > storefront-html.home-banner > a > img`
storefront-section > storefront-element > storefront-html.home-banner > img `storefront-section > storefront-element > storefront-html.home-banner > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`
storefront-button.menu-button > button.has-text > a.button-icon > img `storefront-button.menu-button > button.has-text > a.button-icon > img`

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
storefront-section.header-mobile > storefront-element > storefront-html.header-mobile-logo > a `storefront-section.header-mobile > storefront-element > storefront-html.header-mobile-logo > a`
storefront-section > storefront-element > storefront-html.home-banner > a `storefront-section > storefront-element > storefront-html.home-banner > a`
storefront-section.footer-top-elements > storefront-element > storefront-html.footer-top-logo > a `storefront-section.footer-top-elements > storefront-element > storefront-html.footer-top-logo > a`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`
li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon `li.menu-item > storefront-button.menu-button > button.has-text > a.button-icon`

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

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

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

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

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

○`[lang]` attributes have a valid value

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	search	(Search...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

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

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