Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ 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 ✗

Alt Text Quality

Action

5 of 7 images have issues

REVIEW

5 of 7 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with filename as alt text

2 image(s) with good alt text

7 images 2 good alt text 1 generic 4 missing

Issue	Count
missing	4 image(s)
filename	1 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

button About

2.13:1

#000000

#2A484C

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a About

2.13:1

#000000

#2A484C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Introduction to the IETF

1.70:1

#000000

#24392E

needs 4.5:1 (normal text)

16px · above the fold

a Introduction to the IETF

2.91:1

#000000

#4F5959

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Participants

3.65:1

#000000

#536977

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Mission

3.31:1

#000000

#406478

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Principles

2.95:1

#000000

#245E79

needs 4.5:1 (normal text)

16px · above the fold

a The work

4.17:1

#000000

#6C6F76

needs 4.5:1 (normal text)

16px · above the fold

a Internet Engineering Steering Group

2.93:1

#000000

#445A6D

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Internet Architecture Board

3.99:1

#000000

#696C73

needs 4.5:1 (normal text)

16px · mid-page

6 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome to the	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 IETF 125 in review	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 Upcoming events	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 What's new?	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 Search the IETF emai…	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 Search IETF Datatrac…	19.20:1	3.0:1	#000000	#F3F5F6	Pass
h2 Next IETF Meeting	19.20:1	3.0:1	#000000	#F3F5F6	Pass
title IETF \| Internet Eng…	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Skip to main content	19.95:1	4.5:1	#000000	#F9F9F9	Pass
button Search	19.95:1	4.5:1	#000000	#F9F9F9	Pass
button About	2.13:1	4.5:1	#000000	#2A484C	Fail
a About	2.13:1	4.5:1	#000000	#2A484C	Fail
a Introduction to the …	1.70:1	4.5:1	#000000	#24392E	Fail
a Introduction to the …	2.91:1	4.5:1	#000000	#4F5959	Fail
a Participants	3.65:1	4.5:1	#000000	#536977	Fail
a Mission	3.31:1	4.5:1	#000000	#406478	Fail
a Principles	2.95:1	4.5:1	#000000	#245E79	Fail
a The work	4.17:1	4.5:1	#000000	#6C6F76	Fail
a Internet Engineering…	2.93:1	4.5:1	#000000	#445A6D	Fail
a Internet Architectur…	3.99:1	4.5:1	#000000	#696C73	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

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

39 headings, 1 skip(s)

PASS

39 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H5 About
H6 Introduction to the IETF
H6 Structure of the IETF
H6 Legal requests
H6 Administration
H5 Technologies
H6 IETF technologies in action
H6 IETF technology groups
H6 Recent posts about IETF technologies
H5 Meetings
H6 Participation information
H6 Organizing meetings
H5 Process
H6 RFCs
H6 Standards process details
H5 Participate
H6 Tools and services
H6 Participation guides
H6 Key policies
H5 Support us
H6 Ways to give
H6 Supporting values
H1 Welcome to the IETF
H2 IETF 125 in review
H2 Upcoming events
H3 IETF 126 Vienna
H3 IETF 127 San Francisco
H2 What's new?
H3 IETF Secretariat continues under new approach
H3 Suggested IETF 125 Sessions for Getting Familiar with New Topics
H2 Search the IETF email archive
H2 Search IETF Datatracker
H2 Next IETF Meeting
H4 About skipped
H4 Technologies
H4 Meetings
H4 Process
H4 Participate
H4 Support us

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

A+

Form Accessibility

All 3 controls labeled

PASS

All 3 controls labeled

3 control(s) properly labeled

3 controls

3 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search	search	Search	aria-label
#search-email-box	search	Search the email archive	aria-label
#search-datatracker-box	search	Search IETF Datatracker	aria-label

A+

Link & Button Quality

167 links, 11 buttons — all OK

PASS

167 links, 11 buttons — all OK

167 link(s) with descriptive text

167 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

178 links and buttons have descriptive text

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

A+

Lighthouse Accessibility Audits

Score 100/100 — 1 failing, 27 passed

PASS

100

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.

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
Go `div.row > div.col-lg-7 > form.input-group > button.btn`
Go `div.row > div.col-lg-5 > form.input-group > button.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

●`[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

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

●`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 are distinguishable without relying on color.

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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