Skip to content
https://iaea.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
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
Theme color only
FIX
Theme color only
Info::
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: #ffffff
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 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.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Skip navigation link detected
Info::
Back-to-top link detected
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 10 fail WCAG AA
REVIEW

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

10 pass 10 fail WCAG AA
a Skip to main content
1.87:1
#FFFFFF
on
#99C3E1
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Skip to main content
3.68:1
#000000
on
#0069B4
needs 4.5:1 (normal text)
16px · top of page (header area)
a Press centre
3.68:1
#000000
on
#0069B4
needs 4.5:1 (normal text)
16px · top of page (header area)
a Employment
4.29:1
#000000
on
#507498
needs 4.5:1 (normal text)
16px · above the fold
a Contact
4.07:1
#000000
on
#497193
needs 4.5:1 (normal text)
16px · above the fold
a English
3.86:1
#000000
on
#486E87
needs 4.5:1 (normal text)
16px · above the fold
a العربية
3.34:1
#000000
on
#41647C
needs 4.5:1 (normal text)
16px · above the fold
a 中文
1.80:1
#000000
on
#253B4A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Français
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a Русский
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold

2 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)
ElementRatioRequiredFGBGResult
h1 International Atomic…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Atoms for peace and …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Director General21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In Focus21.00:13.0:1
#000000
#FFFFFF
Pass
h2 IAEA in Numbers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Upcoming Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 IAEA Flagship Initia…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest Photo Essays …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Publications21.00:13.0:1
#000000
#FFFFFF
Pass
title International Atomic…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content1.87:14.5:1
#FFFFFF
#99C3E1
Fail
a Skip to main content3.68:14.5:1
#000000
#0069B4
Fail
a Press centre3.68:14.5:1
#000000
#0069B4
Fail
a Employment4.29:14.5:1
#000000
#507498
Fail
a Contact4.07:14.5:1
#000000
#497193
Fail
a English3.86:14.5:1
#000000
#486E87
Fail
a العربية3.34:14.5:1
#000000
#41647C
Fail
a 中文1.80:14.5:1
#000000
#253B4A
Fail
a Français1.00:14.5:1
#000000
#000000
Fail
a Русский1.00:14.5:1
#000000
#000000
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.

A+
Heading Hierarchy
33 headings
PASS
33 headings
Info::
Single H1 present
  • H1 International Atomic Energy Agency
  • H2 Atoms for peace and development
  • H3 IAEA Supports Research Reactor Safety and Utilization Efforts in Africa
  • H3 Update 347 – IAEA Director General Statement on Situation in Ukraine
  • H3 Republic of Korea: Nuclear Energy, Safeguards and More
  • H3 IAEA and Japan Strengthen Emergency Preparedness in Fukushima
  • H3 Powering Change: A Nuclear Engineer’s Journey from Brazil to the IAEA
  • H2 Director General
  • H2 In Focus
  • H2 IAEA in Numbers
  • H2 Upcoming Events
  • H3 International Conference on Effective Nuclear and Radiation Regulatory Systems: Strengthening Competence, Agility, and Connection in the Modern Era
  • H3 International Conference on Computer Security in the Nuclear World: Securing the Future
  • H3 International Conference on Fast Reactors and Related Fuel Cycles (FR26)
  • H3 Second International Conference on Accelerators for Research and Innovation
  • H2 IAEA Flagship Initiatives
  • H2 Latest Photo Essays and Videos
  • H2 Video: The IAEA in 2025
  • H3 How Do We Keep Radioactive Material Safe and Secure During Transport?
  • H3 Nuclear Energy Summit 2026
  • H3 International Women’s Day 2026
  • H3 The IAEA’s Transportable E-Beam System
  • H2 Publications
  • H3 Assessment of a Management System for Nuclear Facilities
  • H3 Specific Infrastructure Considerations for Nuclear Energy Applications Beyond Electricity
  • H3 Syllabus for the Training of Radiation Protection Officers
  • H4 More on the IAEA
  • H4 Scientific resources
  • H4 Resources
  • H4 Documents
  • H4 Stay in Touch
  • H4 International Atomic Energy Agency
  • H4 Newsletter
A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
1 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
22 images 21 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="EMAIL" id="mce-EMAIL">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-bar-inputsearchSearchfor/id
#mce-EMAILemail(Email address)placeholder only

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

<input type="email" name="EMAIL" id="mce-EMAIL">

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

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | IAEA ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 24 passed
PASS
90

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
FEATURED STORY div.col-12 > div.card__body > div.card__meta > p.card__label
15 April 2026 div.row > div.col-12 > div.card__body > p.card__date
PRESS RELEASE div.card > div.card__body > div.card__meta > p.card__label
17 April 2026 div > div.card > div.card__body > p.card__date
NEWS STORY div.card > div.card__body > div.card__meta > p.card__label
15 April 2026 div.col-12 > div.card > div.card__body > p.card__date
NEWS STORY div.card > div.card__body > div.card__meta > p.card__label
15 April 2026 div.col-12 > div.card > div.card__body > p.card__date
NEWS STORY div.card > div.card__body > div.card__meta > p.card__label
9 April 2026 div.col-12 > div.card > div.card__body > p.card__date
27 – 30 Apr 2026 div.card > div.card__body > p.card__date > span.meeting-from-to-date
Vienna, Austria div.col-12 > div.card > div.card__body > p.card__location
11 – 15 May 2026 div.card > div.card__body > p.card__date > span.meeting-from-to-date
18 – 21 May 2026 div.card > div.card__body > p.card__date > span.meeting-from-to-date
22 – 26 Jun 2026 div.card > div.card__body > p.card__date > span.meeting-from-to-date
Vienna, AT, div.col-12 > div.card > div.card__body > p.card__location
VIDEO div.card > div.card__body > div.card__meta > p.card__label
12 December 2025 div.view-content > div.card > div.card__body > p.card__date
VIDEO div.card > div.card__body > div.card__meta > p.card__label
24 March 2026 div.col-6 > div.card > div.card__body > p.card__date
VIDEO div.card > div.card__body > div.card__meta > p.card__label
12 March 2026 div.col-6 > div.card > div.card__body > p.card__date
VIDEO div.card > div.card__body > div.card__meta > p.card__label
8 March 2026 div.col-6 > div.card > div.card__body > p.card__date
VIDEO div.card > div.card__body > div.card__meta > p.card__label
12 January 2026 div.col-6 > div.card > div.card__body > p.card__date
19 April 2026 div.col-12 > div.card > div.card__body > p.card__date
8 April 2026 div.col-12 > div.card > div.card__body > p.card__date
29 March 2026 div.col-12 > div.card > div.card__body > p.card__date
Official Email div.row > div.col-xl-8 > p > a
Terms of Use div.row > div.col-xl-48 > p.mt-auto > a

These are opportunities to improve the legibility of your content.

Names and labels

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
div.row > div.col-12 > div.card__image > a div.row > div.col-12 > div.card__image > a
div.card > div.card__body > h3.card__title > a div.card > div.card__body > h3.card__title > a
div.card > div.card__body > h3.card__title > a div.card > div.card__body > h3.card__title > a
div.card > div.card__body > h3.card__title > a div.card > div.card__body > h3.card__title > a
div.card > div.card__body > h3.card__title > a div.card > div.card__body > h3.card__title > a

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to main content body.node-2 > a.visually-hidden
Skip to main content body.node-2 > a.visually-hidden

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

○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
●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.
●ARIA attributes are used as specified for the element's role
●`[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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○No element has a `[tabindex]` value greater than 0
○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.
○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.

Send Feedback