Skip to content
https://nobelprize.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
2
PASS
5
INFO
0
Checks
13
5 PASS 2 REVIEW 6 FIX
D
Heading Hierarchy
Action
43 headings, 3 skip(s)
FIX
43 headings, 3 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Nobel Prize
  • H1 Revealing secrets on a tiny scale duplicate H1
  • H2 What would you ask a Nobel Prize laureate?
  • H3 “It’s a lifelong learning process”
  • H2 (empty)
  • H3 Which Nobel Prize laureates do you share a birthday with?
  • H1 Where science takes us: looking back, looking forward duplicate H1
  • H2 What’s on
  • H3 Project Nobel Center
  • H3 Paths to Peace
  • H3 Democracy on the Brink
  • H3 Nobel Prize announcements 2026
  • H1 How microwaves let us tune into one another – and the universe duplicate H1
  • H3 A home for the unique legacy of Alfred Nobel skipped
  • H1 The man behindthe prize duplicate H1
  • H3 One-minute crash course skipped
  • H1 Laureates discussing research, discoveries and achievements duplicate H1
  • H3 Explore prizes and laureates skipped
  • H2 Get involved
  • H2 Connect with us
  • H2 Discover more Nobel Prize stories
  • H3 Sign up for the monthly newsletter
  • H2 Play and learn
  • H3 The Blood Typing Game
  • H3 Pavlov’s Dog
  • H3 Vitamin B1
  • H2 In memoriam
  • H3 J. Michael Bishop dies at 90
  • H3 Christopher Sims passes away
  • H3 Anthony Leggett dies at 87
  • H3 Louis Brus passes away
  • H4 About the Nobel Prize organisation
  • H5 The Nobel Foundation
  • H5 The prize-awarding institutions
  • H5 Outreach organisations
  • H6 Join us
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Strictly Necessary Cookies
  • H3 Cookie List

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - NobelPrize.org ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
33 landmarks
PASS
33 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
4 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main menu" MAIN CONTENTINFO footer

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
Alt Text Quality
1 of 29 images have issues
PASS
1 of 29 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
12 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
29 images 16 good alt text 12 decorative 1 missing
IssueCount
missing1 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

A
Form Accessibility
1 of 21 controls have issues
PASS
1 of 21 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
20 control(s) properly labeled
21 controls
20 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-form-input-headersearchSearch by term.for/id
datetextEnter birth datearia-label
#mobile-dropdownselectSelect the category or categories you would like to filter byfor/id
#physicsradionone
#chemistryradionone
#medicineradionone
#literatureradionone
#peaceradionone
#economic-sciencesradionone
#increment-inputtextChoose a year you would like to search infor/id
#newsletteremailemailYour email addressfor/id
#newsletterconfirmcheckboxnone
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
inputsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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)
ElementRatioRequiredFGBGResult
h1 Revealing secrets on…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Where science takes …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 How microwaves let u…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 The man behind21.00:13.0:1
#000000
#FFFFFF
Pass
h1 the prize21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Laureates discussing…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What would you ask a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 What’s on21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get involved21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect with us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Play and learn21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In memoriam21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Which Nobel Prize la…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Explore prizes and l…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sign up for the mont…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage Consent Prefe…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cookie List21.00:13.0:1
#000000
#FFFFFF
Pass
title The official website…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.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.

A
Lighthouse Accessibility Audits
Score 94/100 — 4 failing, 33 passed
PASS
94

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
What would you ask a Nobel Prize laureate? div.nobel__blocks--content > section.article-grid > header.section-header > h2.section-header-h3
Enter div.laureates-birthday__text > form.laureates-birthday__form > div.laureates-birthday__input-group > button.btn
What’s on section.queried-content-block > div.container > header.block-separator > h2.block-separator__title
Learn more section.page-hero > div.blurb > div.hero-btn-wrapper > a.hero-btn
See all crash courses div.content-wrapper > div.text > p > a
Watch Nobel Minds 2025 section.page-hero > div.blurb > div.hero-btn-wrapper > a.hero-btn
Get involved div.nobel__blocks--content > section.social-media-block > header.block-separator > h2.block-separator__title
Connect with us div.nobel__blocks--content > section.social > header.section-header > h2.section-header-h3
privacy policy form > label.newsletterconfirm > p > a
Play and learn section.queried-content-block > div.container > header.block-separator > h2.block-separator__title
In memoriam div.nobel__blocks--content > section.article-grid > header.section-header > h2.section-header-h3
Biography div.content-wrapper > div.text > p > a
Biography div.content-wrapper > div.text > p > a
Biography div.content-wrapper > div.text > p > a
Biography div.content-wrapper > div.text > p > a
NOBEL PRIZE section.colophon > div.footer-logo > p.site-logo > a
Copyright © Nobel Prize Outreach 2026 footer.site-footer > div.container > section.colophon > div.copyright
Cookies settings div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler
Accept all cookies div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
figure.wp-block-embed > div.wp-block-embed__wrapper > div.iframe > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.iframe > iframe
figure.wp-block-embed > div.wp-block-embed__wrapper > div.iframe > iframe figure.wp-block-embed > div.wp-block-embed__wrapper > div.iframe > iframe

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.

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
A home for the unique legacy of Alfred Nobel div.content-wrapper > header.content > div.title > h3.headline
One-minute crash course div.content-wrapper > header.content > div.title > h3.headline
Explore prizes and laureates div.nobel__blocks--content > section.explore-laureates > header.section-header > h3

These are opportunities to improve keyboard navigation in your application.

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
Enter div.laureates-birthday__text > form.laureates-birthday__form > div.laureates-birthday__input-group > button.btn
Our cookie policy. 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
●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
●Input buttons have discernible text.
●Form elements have associated labels
●`[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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○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.
○`[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>`.
○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.

Send Feedback