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 3 REVIEW 4 FIX

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 ✗

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Raspberry Pi Foundation ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Enabling all young people to realise the…

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Why kids still need to learn to code in …

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Coding for kids

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join or start a Code Club

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Resources for teachers & schools

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Research

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 News

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 “When I started coding, I started to d…

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Raspberry Pi computers

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Learn to code

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Coolest Projects

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Your code in space

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Professional development for teachers

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 The Computing Curriculum

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Experience AI

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ada Computer Science

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Experience CS

1.95:1

#000000

#3F3D3E

needs 3.0:1 (large text)

19px · bottom of viewport

title Teach, learn, and make with the Raspberr…

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

2.03:1

#000000

#404040

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to footer

1.19:1

#000000

#340815

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Enabling all young p…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Why kids still need …	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Coding for kids	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Join or start a Code…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Resources for teache…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Research	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 News	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 “When I started co…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h2 Raspberry Pi compute…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Learn to code	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Coolest Projects	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Your code in space	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Professional develop…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 The Computing Curric…	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Experience AI	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Ada Computer Science	1.95:1	3.0:1	#000000	#3F3D3E	Fail
h3 Experience CS	1.95:1	3.0:1	#000000	#3F3D3E	Fail
title Teach, learn, and ma…	2.03:1	4.5:1	#000000	#404040	Fail
a Skip to main content	2.03:1	4.5:1	#000000	#404040	Fail
a Skip to footer	1.19:1	4.5:1	#000000	#340815	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

7 <nav> landmark(s) found

6 of 7 <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

Heading Hierarchy

21 headings, 1 skip(s)

PASS

21 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 Enabling all young people to realise their full potential through computing
H2 Why kids still need to learn to code in the age of AI
H2 Coding for kids
H3 Learn to code
H3 Coolest Projects
H3 Your code in space
H2 Join or start a Code Club
H2 Resources for teachers & schools
H3 Professional development for teachers
H3 The Computing Curriculum
H3 Experience AI
H3 Ada Computer Science
H3 Experience CS
H2 Research
H2 News
H4 Experience AI: Reaching millions of young people with AI literacy skipped
H4 Many paths into mentoring: Building inclusive Code Clubs in Glasgow
H4 Experience CS: The complete set of units is live
H4 Highlights from Astro Pi 2025–2026 community events
H2 “When I started coding, I started to discover that it was very fun, I could create anything I wanted. My imagination was running wild.”
H2 Raspberry Pi computers

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

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

6 decorative image(s) correctly marked

9 image(s) with good alt text

15 images 9 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

1 issue(s) across 87 links and 1 buttons

PASS

1 issue(s) across 87 links and 1 buttons

1 link(s) with generic text

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

Got: https://www.raspberrypi.org/computers ("Read more")

86 link(s) with descriptive text

87 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.raspberrypi.org/computers	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Computers

87 links and buttons have descriptive text

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

https://www.raspberrypi.org/computers ("Read 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

A+

Lighthouse Accessibility Audits

Score 99/100 — 1 failing, 27 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
Experience AI: Reaching millions of young people with AI literacy `div.pk-c-blog-slice__wrapper > div.pk-c-blog-slice__blog-posts > a.pk-c-color-blog-post > h4`

These are opportunities to improve keyboard navigation in your application.

○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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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