Skip to content
https://transparency.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 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: #3695d8
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::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <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
Form Accessibility
Action
3 of 14 controls have issues
REVIEW
3 of 14 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <input type="submit">; <input type="submit">
Info::
11 control(s) properly labeled
14 controls
11 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
querytextEnter search queryaria-label
querytextEnter search queryaria-label
#banner-first-nametextFirst name *for/id
#banner-last-nametextLast name *for/id
#banner-emailemailEmail address *for/id
#banner-privacy-consent-0checkboxView our Privacy Policy.for/id
#footer-first-nametextFirst name *for/id
#footer-last-nametextLast name *for/id
#footer-emailemailEmail address *for/id
#footer-privacy-consent-0checkboxView our Privacy Policy.for/id
#footer-select-a-countryselectSelect a countryaria-label
inputsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<input type="submit">; <input type="submit">; <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

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
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Error 404 - Transparency.org Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
13 icon(s) detected
REVIEW
13 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
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 HOW DOES YOUR COUNTRY MEASURE UP ON THE …
1.04:1
#000000
on
#0F0409
needs 3.0:1 (large text)
32px · mid-page
h2 We have one vision, a world free of corr…
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · mid-page
h2 Latest news & analyses
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What we have done so far
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Share our vision
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What we do
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Updates
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Corruption
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 More
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Subscribe to our weekly newsletter
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay informed
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Engage
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Donate
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Join the conversation on social media
1.85:1
#000000
on
#3A3A3A
needs 3.0:1 (large text)
19px · bottom of viewport
title Home - Transparency.org
1.96:1
#000000
on
#3E3E3E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · top of page (header area)
p You are using an outdated browser. Most …
1.82:1
#000000
on
#393939
needs 4.5:1 (normal text)
16px · top of page (header area)
a upgrading your browser
1.01:1
#000000
on
#070003
needs 4.5:1 (normal text)
16px · top of page (header area)
p it will look and perform better.
1.01:1
#000000
on
#070003
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 HOW DOES YOUR COUNTR…1.04:13.0:1
#000000
#0F0409
Fail
h2 We have one vision, …1.79:13.0:1
#000000
#383838
Fail
h2 Latest news & analys…1.85:13.0:1
#000000
#3A3A3A
Fail
h2 What we have done so…1.85:13.0:1
#000000
#3A3A3A
Fail
h2 Share our vision1.85:13.0:1
#000000
#3A3A3A
Fail
h2 About1.85:13.0:1
#000000
#3A3A3A
Fail
h2 What we do1.85:13.0:1
#000000
#3A3A3A
Fail
h2 Updates1.85:13.0:1
#000000
#3A3A3A
Fail
h2 Corruption1.85:13.0:1
#000000
#3A3A3A
Fail
h2 More1.85:13.0:1
#000000
#3A3A3A
Fail
h3 Subscribe to our wee…1.85:13.0:1
#000000
#3A3A3A
Fail
h3 Stay informed1.85:13.0:1
#000000
#3A3A3A
Fail
h3 Engage1.85:13.0:1
#000000
#3A3A3A
Fail
h3 Donate1.85:13.0:1
#000000
#3A3A3A
Fail
h3 Join the conversatio…1.85:13.0:1
#000000
#3A3A3A
Fail
title Home - Transparency.…1.96:14.5:1
#000000
#3E3E3E
Fail
a Skip to main content1.87:14.5:1
#000000
#3B3B3B
Fail
p You are using an out…1.82:14.5:1
#000000
#393939
Fail
a upgrading your brows…1.01:14.5:1
#000000
#070003
Fail
p it will look and per…1.01:14.5:1
#000000
#070003
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
Landmark Structure
22 landmarks
PASS
22 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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 "Site navigation" 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+
Heading Hierarchy
26 headings
PASS
26 headings
Info::
Single H1 present
  • H1 HOW DOES YOUR COUNTRY MEASURE UP ON THE CORRUPTION PERCEPTIONS INDEX 2025?
  • H2 We have one vision, a world free of corruption
  • H2 What is corruption?
  • H2 Research
  • H2 Advocacy
  • H2 Latest news & analyses
  • H2 Panama Papers: 10 years on, the promises and the failures
  • H2 CPI 2025: Findings and insights
  • H2 CoSP11: A critical moment for shaping the future of integrity worldwide
  • H2 Who really owns it? The push for transparency to reveal stolen wealth in the Middle East and North Africa
  • H2 Corruption Perceptions Index 2025: Decline in leadership undermining global fight against corruption
  • H2 Corruption Perceptions Index 2025: Europe must step up leadership in the fight against corruption
  • H2 Corruption Perceptions Index 2025: Corruption across the Americas is damaging people’s lives and fuelling violence
  • H2 Corruption Perceptions Index 2025: Weak institutions are fuelling corruption in Eastern Europe and Central Asia
  • H2 What we have done so far
  • H3 Subscribe to our weekly newsletter
  • H2 Share our vision
  • H3 Stay informed
  • H3 Engage
  • H3 Donate
  • H3 Join the conversation on social media
  • H2 About
  • H2 What we do
  • H2 Updates
  • H2 Corruption
  • H2 More
A
Alt Text Quality
1 of 10 images have issues
PASS
1 of 10 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 image(s) with alt text over 125 characters
Info::
7 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
10 images 1 good alt text 7 decorative 1 missing
IssueCount
missing1 image(s)
too long1 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+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 33 passed
PASS
95

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
Consent div#CybotCookiebotDialogNav > ul#CybotCookiebotDialogNavList > li.CybotCookiebotDialogNavItem > a#CybotCookiebotDialogNavDeclaration
Allow all div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll

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.grid > nav.col-span-2 > div.flex > a.itz-logo div.grid > nav.col-span-2 > div.flex > a.itz-logo

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.

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
Explore the results main#content > section#hero > div.flex > a.btn
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.
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
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
`[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
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 type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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