Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Alt Text Quality

Action

7 of 10 images have issues

FIX

7 of 10 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image-in-link without alt text

An image inside a link with no alt creates an empty link.

3 image(s) with good alt text

10 images 3 good alt text 7 missing

Issue	Count
missing	7 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

5 issue(s) across 87 links and 2 buttons

FIX

5 issue(s) across 87 links and 2 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://twitter.com/share; https://www.linkedin.com/shareArticle; #

7 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/speeches/sp260420.htm"]; a[href="/fsi/fsibriefs30.htm"]; a[href="/press/p260316.htm"]; a[href="/publ/qtrpdf/r_qt2603b.htm"]; a[href="/careers/index.htm"]; a[href="/fsi/index.htm"]; a[href="/topic/fintech/hub.htm"]

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.hdr_searchbutton (#70 on page); button.hdr_searchbutton (#80 on page)

77 link(s) with descriptive text

87 links

3 empty

0 generic text

0 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
/speeches/sp260420.htm	Stablecoins: framing the debat…	img no alt	Add alt attribute to the image
/fsi/fsibriefs30.htm	Stress testing banks for cyber…	img no alt	Add alt attribute to the image
/press/p260316.htm	Senior management appointment1…	img no alt	Add alt attribute to the image
/publ/qtrpdf/r_qt2603b.htm	Central bank communications16 …	img no alt	Add alt attribute to the image
/careers/index.htm	Careers at the BIS Learn abo…	img no alt	Add alt attribute to the image
/fsi/index.htm	Financial Stability Institute …	img no alt	Add alt attribute to the image
/topic/fintech/hub.htm	The BIS Innovation Hub Desig…	img no alt	Add alt attribute to the image
https://twitter.com/share	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/shareArticle	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

77 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://twitter.com/share; https://www.linkedin.com/shareArticle; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/speeches/sp260420.htm"]; a[href="/fsi/fsibriefs30.htm"]; a[href="/press/p260316.htm"]; a[href="/publ/qtrpdf/r_qt2603b.htm"]; a[href="/careers/index.htm"]; a[href="/fsi/index.htm"]; a[href="/topic/fintech/hub.htm"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Icon-only buttons need an aria-label so screen readers can announce them.

button.hdr_searchbutton (#70 on page); button.hdr_searchbutton (#80 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://bis.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://bis.org/manifest.json

Manifest contains invalid JSON.

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.

Landmark Structure

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

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

Form Accessibility

Action

3 of 3 controls have issues

REVIEW

3 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="image" id="pagemsgx">

2 control(s) rely on placeholder only

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

Got: <input type="text" name="globalset_q" id="sp_q">; <input type="text" name="globalset_q">

3 controls

0 labeled

2 placeholder only

1 unlabeled

Control	Type	Label	Method
#sp_q	text	(Search the website)	placeholder only
globalset_q	text	(Search the website)	placeholder only
#pagemsgx	image	(none)	none

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

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

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

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

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 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Lighthouse Accessibility Audits

Score 80/100 — 4 failing, 16 passed

REVIEW

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
20 Apr 2026 \| Pablo Hernández de Cos \| Bank of Japan seminar, Tokyo `div#hp_dc_bisspeeches > ul > li.singlelink > span.date`
24 Mar 2026 \| Alexandre Tombini \| 89th Banking Convention, Cancún `div#hp_dc_bisspeeches > ul > li.singlelink > span.date`
04 Mar 2026 \| Pablo Hernández de Cos \| International Center for Monetary and Ba… `div#hp_dc_bisspeeches > ul > li.singlelink > span.date`
20 Feb 2026 \| Hyun Song Shin \| 15th Annual Julis Rabinowitz Public Policy and F… `div#hp_dc_bisspeeches > ul > li.singlelink > span.date`
28 Jan 2026 \| Pablo Hernández de Cos \| CEU San Pablo University, Madrid `div#hp_dc_bisspeeches > ul > li.singlelink > span.date`
20 Apr 2026 \| Working paper \| Kumar Rishabh and Vatsala Shreeti `div > ul > li.singlelink > span.date`
02 Apr 2026 \| BIS Paper \| Torsten Ehlers, Leonardo Gambacorta and Livia Pancotto `div > ul > li.singlelink > span.date`
01 Apr 2026 \| Working paper \| Jon Frost, Carlos Madeira, Yash Rastogi and Haral… `div > ul > li.singlelink > span.date`
30 Mar 2026 \| Working paper \| Enisse Kharroubi and Marius Koechlin `div > ul > li.singlelink > span.date`
30 Mar 2026 \| BIS Paper \| Hakan Eroglu, Giulio Cornelli, Jon Frost, Friederike … `div > ul > li.singlelink > span.date`
19 Feb 2026 `div > ul > li.singlelink > span.date`
29 Jan 2026 `div > ul > li.singlelink > span.date`
08 Dec 2025 `div > ul > li.singlelink > span.date`
24 Mar 2026 \| Publication `div > ul > li.singlelink > span.date`
23 Mar 2026 \| Standard `div > ul > li.singlelink > span.date`
17 Mar 2026 \| Press release `div > ul > li.singlelink > span.date`
09 Mar 2026 \| Press release `div > ul > li.singlelink > span.date`
26 Feb 2026 \| Press release `div > ul > li.singlelink > span.date`
21 Apr 2026 \| Publication \| CPMI `div > ul > li.singlelink > span.date`
16 Apr 2026 \| Publication \| FSI `div > ul > li.singlelink > span.date`
16 Apr 2026 \| Publication \| CPMI `div > ul > li.singlelink > span.date`
31 Mar 2026 \| Publication \| IFC `div > ul > li.singlelink > span.date`
12 Mar 2026 \| Publication \| CGFS `div > ul > li.singlelink > span.date`
Green finance `div > ul > li.singlelink > span.date`
Green finance `div > ul > li.singlelink > span.date`
Suptech and regtech `div > ul > li.singlelink > span.date`
Suptech and regtech `div > ul > li.singlelink > span.date`
17 Feb 2026 \| Publication `div > ul > li.singlelink > span.date`
29 Jan 2026 \| Publication `div > ul > li.singlelink > span.date`
11 Dec 2025 \| Publication `div > ul > li.singlelink > span.date`
10 Dec 2025 \| Publication `div > ul > li.singlelink > span.date`
17 Nov 2025 \| Publication `div > ul > li.singlelink > span.date`
20 Apr 2026 `div > ul > li.singlelink > span.date`
01 Apr 2026 `div > ul > li.singlelink > span.date`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.bighlblk-inner > a.hl > div.hlimg > img `div.bighlblk-inner > a.hl > div.hlimg > img`
div.bighlblk-inner > a.hl > div.hlimg > img `div.bighlblk-inner > a.hl > div.hlimg > img`
a.cd-cell > div.boxlink-inner > div > img `a.cd-cell > div.boxlink-inner > div > img`
a.cd-cell > div.boxlink-inner > div > img `a.cd-cell > div.boxlink-inner > div > img`
a.cd-cell > div.boxlink-inner > div > img `a.cd-cell > div.boxlink-inner > div > img`

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#sharethispage > ul.sociallist > li > a#footershare_twitter `div#sharethispage > ul.sociallist > li > a#footershare_twitter`
div#sharethispage > ul.sociallist > li > a#footershare_linkedin `div#sharethispage > ul.sociallist > li > a#footershare_linkedin`
div#sharethispage > ul.sociallist > li > a#footershare_email `div#sharethispage > ul.sociallist > li > a#footershare_email`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●`[accesskey]` values are unique

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

●Heading elements appear in a sequentially-descending order

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Deprecated ARIA roles were not used

○`[aria-*]` attributes match their roles

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

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

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

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

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

A+

Heading Hierarchy

12 headings

PASS

12 headings

Single H1 present

H1 Welcome to the Bank for International Settlements
H2 What's new at BIS
H3 Speeches from
H3 Research at BIS
H3 Statistics from BIS
H2 Basel Committee
H2 Other BIS committees
H2 BIS Innovation Hub
H3 Latest project updates
H3 Publications & Speeches
H2 Announcements
H2 You may be interested in

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /bis_original/shared/print-5dd6ea242dd39ae99601c816cf6ba8e800e519f71ffa3f5a06a8ef0ddf95f597.css

Print Stylesheet ✓ Print Optimized

Print stylesheet /bis_original/shared/print-5dd6ea242dd39ae99601c816cf6ba8e800e519f71ffa3f5a06a8ef0ddf95f597.css ✓Inline @media print Not detected ✗

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)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to the Bank …	10.65:1	3.0:1	#000000	#DDADAC	Pass
h2 What's new at BIS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Basel Committee	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Other BIS committees	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 BIS Innovation Hub	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Announcements	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 You may be intereste…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Speeches from	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Research at BIS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Statistics from BIS	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Latest project updat…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Publications & Speec…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Bank for Internation…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Logout	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Promoting global mon…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Stablecoins: framing…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 20 Apr 2026	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Speech	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Pablo Hernández de …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Stress testing banks…	21.00:1	4.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.

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