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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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

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

Heading Hierarchy

27 headings, 2 skip(s)

REVIEW

27 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H5 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 International Association for Cryptologic Research
H1 International Associationfor Cryptologic Research
H3 Events skipped
H5 Eurocrypt 2026 skipped
H6 10 - 14 May 2026Rome, Italy
H5 Crypto 2026
H6 17 - 20 August 2026Santa Barbara, USA
H5 Asiacrypt 2026
H6 7 - 11 December 2026Hong Kong, China
H5 FSE 2026
H6 23 - 27 March 2026Singapore, Singapore
H5 PKC 2026
H6 25 - 28 May 2026West Palm Beach, USA
H5 CHES 2026
H6 11 - 15 October 2026Antalya, Turkey
H5 TCC 2026
H6 10 - 13 November 2026New York City, USA
H5 RWC 2027
H6 5 - 7 April 2027Seattle, United States
H3 News
H3 Publications
H4 Journal of Cryptology
H4 Conference Proceedings
H4 Open Access Journals
H4 IACR ePrint Archive
H3 Recent Awards
H3 Featured Video

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="search" name="q" id="searchbox">; <input type="search" name="q" id="searchboxMobile">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#searchbox	search	(Search IACR)	placeholder only
#searchboxMobile	search	(Search IACR)	placeholder only

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h2 International Association for Cryptologi…

1.68:1

#000000

#102A83

needs 3.0:1 (large text)

24px · top of page (header area)

title The International Association for Crypto…

1.68:1

#000000

#102A83

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 International Associ…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h1 for Cryptologic Rese…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 International Associ…	1.68:1	3.0:1	#000000	#102A83	Fail
h3 Events	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 News	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Publications	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Recent Awards	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h3 Featured Video	20.47:1	3.0:1	#000000	#FCFCFC	Pass
title The International As…	1.68:1	4.5:1	#000000	#102A83	Fail
a IACR	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a Events	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a All IACR events	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a Asiacrypt	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a Crypto	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a Eurocrypt	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a CHES	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a FSE	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a PKC	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a TCC	20.47:1	4.5:1	#000000	#FCFCFC	Pass
a RWC	20.47:1	4.5:1	#000000	#FCFCFC	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.

A+

Alt Text Quality

All 29 images OK

PASS

All 29 images OK

29 image(s) with good alt text

29 images 29 good alt text

All images have appropriate alt text.

Link & Button Quality

1 issue(s) across 131 links and 3 buttons

PASS

1 issue(s) across 131 links and 3 buttons

1 button(s) with no accessible text

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

Got: button.btn (#100 on page)

131 link(s) with descriptive text

131 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

133 links and buttons have descriptive text

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

button.btn (#100 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

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 23 passed

PASS

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.

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
Eurocrypt 2026 `article.col-12 > div.row > div.col > h5.mt-2`

These are opportunities to improve keyboard navigation in your application.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
CC BY 3.0 `div.row > div.col-12 > p.attribution > a`
via Wikimedia Commons `div.row > div.col-12 > p.attribution > a`
pxhere.com `div.row > div.col-12 > p.attribution > a`
Compact Lattice Signatures via Iterative Rejection Sampling `section.row > article.col-12 > p > a`

These are opportunities to improve the legibility of your content.

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

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

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

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