Skip to content
https://wassenaar.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
F
Alt Text Quality
Action
5 of 26 images have issues
FIX
5 of 26 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
6 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
26 images 15 good alt text 6 decorative 5 missing
IssueCount
missing5 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

D
Form Accessibility
Action
4 of 4 controls have issues
FIX
4 of 4 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="wpsolr_q" id="search_que">; <input type="text" name="wpsolr_q" id="search_que">
4 controls
0 labeled
2 placeholder only
2 unlabeled
ControlTypeLabelMethod
#search_quetext(Search ....)placeholder only
#search_quetext(Search ....)placeholder only
#searchsubmitsubmit(none)none
#searchsubmitsubmit(none)none

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

<input type="submit" id="searchsubmit">; <input type="submit" id="searchsubmit">

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.

<input type="text" name="wpsolr_q" id="search_que">; <input type="text" name="wpsolr_q" id="search_que">

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-s6jpkh
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://wassenaar.org/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://wassenaar.org/manifest.json

Manifest contains invalid JSON.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 7 fail WCAG AA
REVIEW

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

13 pass 7 fail WCAG AA
title Home - The Wassenaar Arrangement
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · top of page (header area)
span English
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Français
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Deutsch
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Русский
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · above the fold
span Español
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · above the fold
a The Wassenaar Arrangement
2.03:1
#000000
on
#363D6A
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Home21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Home images21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Highlights21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Introduction21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Search21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Recent Activities21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Last updated21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contacts mobile21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
title Home - The Wassenaar…2.03:14.5:1
#000000
#363D6A
Fail
span English2.03:14.5:1
#000000
#363D6A
Fail
span Français2.03:14.5:1
#000000
#363D6A
Fail
span Deutsch2.03:14.5:1
#000000
#363D6A
Fail
span Русский2.03:14.5:1
#000000
#363D6A
Fail
span Español2.03:14.5:1
#000000
#363D6A
Fail
a The Wassenaar Arrang…2.03:14.5:1
#000000
#363D6A
Fail
span On Export Controls f…21.00:14.5:1
#000000
#FFFFFF
Pass
em Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Home21.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.

B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 22 passed
REVIEW
87

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
Highlights div.row > div.col-md-5 > section.widget > h3
Statement issued by 2025 Plenary Chair section.widget > div#recent-posts > div.item > a
5 DECEMBER 2025 section.widget > div#recent-posts > div.item > span.post-date
List of Dual-Use Goods and Technologies & Munitions List (2025) Corr. section.widget > div#recent-posts > div.item > a
5 DECEMBER 2025 section.widget > div#recent-posts > div.item > span.post-date
Summary of Most Recent Changes to Lists Corr. section.widget > div#recent-posts > div.item > a
5 DECEMBER 2025 section.widget > div#recent-posts > div.item > span.post-date
Best Practice Guidelines on Internal Compliance Programmes section.widget > div#recent-posts > div.item > a
5 DECEMBER 2025 section.widget > div#recent-posts > div.item > span.post-date
READ MORE main.main > div.row > div.col-md-5 > a.read-more
Contact main.main > div.row > div.col-md-5 > h3
CONTACT US div.col-md-5 > div.textwidget > p > a.read-more
Introduction main.main > div.row > div.col-md-7 > h3
About Us div.row > div.col-md-7 > p > a
here div.row > div.col-md-7 > p > a
Frequently Asked Questions (FAQ) div.row > div.col-md-7 > p > a
Recent Activities aside.sidebar > section.widget_text > div.textwidget > h3
Head of Secretariat Addresses the Asian Export Control Seminar aside.sidebar > section.widget_text > div.textwidget > a.video-link
Enhanced Technical Briefing for WA Outreach Partners aside.sidebar > section.widget_text > div.textwidget > a.video-link
Introductory Video aside.sidebar > section.widget_text > div.textwidget > a.video-link
Contact div.mobile-footer > section.widget > div.textwidget > h3

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
section.widget_text > div.textwidget > a.video-link > img section.widget_text > div.textwidget > a.video-link > img
section.widget_text > div.textwidget > a.video-link > img section.widget_text > div.textwidget > a.video-link > img
section.widget_text > div.textwidget > a.video-link > img section.widget_text > div.textwidget > a.video-link > img
section.widget > div.textwidget > a.glyphicon > img section.widget > div.textwidget > a.glyphicon > 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.mobile-footer > section.widget > div.textwidget > a.glyphicon div.mobile-footer > section.widget > div.textwidget > a.glyphicon
div.mobile-footer > section.widget > div.textwidget > a.glyphicon div.mobile-footer > section.widget > div.textwidget > a.glyphicon

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.

○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
●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
●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.
●`[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
●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
○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
○`<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.
○Skip links are focusable.
○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.
○`<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.
○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
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A
Heading Hierarchy
13 headings, 1 skip(s)
PASS
13 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Home images
  • H1 Home
  • H3 Highlights skipped
  • H3 Contact
  • H3 Introduction
  • H3 Search
  • H3 Recent Activities
  • H4 Wassenaar, The Hague
  • H4 Vienna, Austria
  • H3 Last updated
  • H3 Contacts mobile
  • H3 Contact
  • H4 WA SECRETARIAT

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

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

Send Feedback