Skip to content
https://icc-cpi.int

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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: #003366
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
9 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
13 headings, 1 skip(s)
REVIEW
13 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Main navigation
  • H5 About the Court
  • H5 States Parties
  • H5 Trust Fund For Victims
  • H5 Documents
  • H2 Today in the courtroom
  • H2 Court Calendar
  • H5 Social Media Links skipped
  • H5 About
  • H5 Situations and Cases
  • H5 Documents
  • H5 Practical information
  • H5 Footer menu

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

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | International Criminal Court ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
title | International Criminal Court
1.67:1
#000000
on
#003366
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.67:1
#000000
on
#003366
needs 4.5:1 (normal text)
16px · top of page (header area)
div Trying individuals for genocide, war cri…
1.67:1
#000000
on
#003366
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Today in the courtro…18.76:13.0:1
#000000
#F2F2F2
Pass
h2 Court Calendar18.76:13.0:1
#000000
#F2F2F2
Pass
title | International Crim…1.67:14.5:1
#000000
#003366
Fail
a Skip to main content1.67:14.5:1
#000000
#003366
Fail
div Trying individuals f…1.67:14.5:1
#000000
#003366
Fail
a Home7.16:14.5:1
#000000
#8599AD
Pass
a About16.67:14.5:1
#000000
#E5E5E5
Pass
a The Court18.76:14.5:1
#000000
#F2F2F2
Pass
a How the Court works18.76:14.5:1
#000000
#F2F2F2
Pass
a Organization18.76:14.5:1
#000000
#F2F2F2
Pass
a Presidency18.76:14.5:1
#000000
#F2F2F2
Pass
a Judicial Divisions18.76:14.5:1
#000000
#F2F2F2
Pass
a Office of the Prosec…18.76:14.5:1
#000000
#F2F2F2
Pass
a Defence18.76:14.5:1
#000000
#F2F2F2
Pass
a Victims18.76:14.5:1
#000000
#F2F2F2
Pass
a Witnesses18.76:14.5:1
#000000
#F2F2F2
Pass
a Registry18.76:14.5:1
#000000
#F2F2F2
Pass
a States Parties18.76:14.5:1
#000000
#F2F2F2
Pass
a Cooperation18.76:14.5:1
#000000
#F2F2F2
Pass
a Outreach18.76:14.5:1
#000000
#F2F2F2
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 8 failing, 21 passed
REVIEW
79

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_previous_homepage_press_release_feed-block_1 > li.arrow div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_previous_homepage_press_release_feed-block_1 > li.arrow
div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_next_homepage_press_release_feed-block_1 > li.arrow div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_next_homepage_press_release_feed-block_1 > li.arrow

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Other News div.view > div.view-header > p.m-0 > a.text-decoration-none
Duterte (Republic of the Philippines) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Duterte (Republic of the Philippines) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Duterte (Republic of the Philippines) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Duterte (Republic of the Philippines) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
El Hishri (Libya) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Central African Republic II td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Duterte (Republic of the Philippines) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Al Hassan (Mali) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Ongwen (Uganda) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
El Hishri (Libya) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
El Hishri (Libya) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Moot Court td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-two
El Hishri (Libya) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Moot Court td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Moot Court td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one
Abd-Al-Rahman (Darfur, Sudan) td.fc-list-item-title > div.calendar-view > div.heading > span.court-event-colour-one

These are opportunities to improve the legibility of your content.

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
Social Media Links div.container-xll > div.footer--menus-holder > nav#block-socialmedialinks > h5#block-socialmedialinks-menu

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
01234 div.view-content > div.skin-default > div.views-slideshow-controls-bottom > ul#listNav

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_previous_homepage_press_release_feed-block_1 > li.arrow div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_previous_homepage_press_release_feed-block_1 > li.arrow
div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_next_homepage_press_release_feed-block_1 > li.arrow div.views_slideshow_controls_defendants > div#views_slideshow_controls_text_homepage_press_release_feed-block_1 > span#views_slideshow_controls_text_next_homepage_press_release_feed-block_1 > li.arrow

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Defendants at large div.row > div.col-2 > p.statsTitle > a.text-decoration-none
Defendants div.row > div.col-2 > p.statsTitle > a.text-decoration-none
Cases div.row > div.col-2 > p.statsTitle > a.text-decoration-none

These items highlight common accessibility best practices.

Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen reader users. Learn more about captions.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
February 23, 2026 Monday 10:00 - 15:00 Duterte (Republic of the Philippines)… div.fc-view-container > div.fc-view > div.fc-scroller > table.fc-list-table

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
February 23, 2026 Monday 10:00 - 15:00 Duterte (Republic of the Philippines)… div.fc-view-container > div.fc-view > div.fc-scroller > table.fc-list-table
○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 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 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
●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.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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-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
○`<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.
○`<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.
○Elements with visible text labels have matching accessible names.
A
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
2 of 9 <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 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
All 14 images OK
PASS
All 14 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
13 image(s) with good alt text
14 images 13 good alt text
IssueCount
too long1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback