Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

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

Theme color only

FIX

Theme color only

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: hsl(203.6, 100%, 12%)

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

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

2 navigation landmark(s) detected

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 2 <nav> element(s)

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.

Form Accessibility

2 of 7 controls have issues

REVIEW

2 of 7 controls have issues

2 control(s) without accessible label

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

Got: <input type="checkbox" id="menu-main-menu-toggle">; <input type="search" name="s">

5 control(s) properly labeled

7 controls

5 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#toggle-4272	checkbox	Feature Status	for/id
#toggle-9988	checkbox	Documentation	for/id
#toggle-4282	checkbox	Policies	for/id
#toggle-4274	checkbox	Contribute	for/id
#toggle-4270	checkbox	Blog	for/id
#menu-main-menu-toggle	checkbox	(none)	none
s	search	(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

Link & Button Quality

6 issue(s) across 58 links and 0 buttons

REVIEW

6 issue(s) across 58 links and 0 buttons

1 link(s) with no accessible text

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

Got: a (#163 on page)

5 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://webkit.org/blog/17917/release-notes-for-safari-technology-preview-241/ ("Read more"); https://webkit.org/blog/17899/introducing-the-jetstream-3-benchmark-suite/ ("Read more"); https://webkit.org/blog/17862/webkit-features-for-safari-26-4/ ("Read more"); https://webkit.org/blog/17818/announcing-interop-2026/ ("Read more"); https://webkit.org/blog/17798/webkit-features-for-safari-26-3/ ("Read more")

52 link(s) with descriptive text

58 links

1 empty

5 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://webkit.org/blog/17917/release-no…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Release Notes For Safari Technology Preview 241
https://webkit.org/blog/17899/introducin…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Introducing The Jetstream 3 Benchmark Suite
https://webkit.org/blog/17862/webkit-fea…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Webkit Features For Safari 26 4
https://webkit.org/blog/17818/announcing…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Announcing Interop 2026
https://webkit.org/blog/17798/webkit-fea…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Webkit Features For Safari 26 3

52 links and buttons have descriptive text

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

a (#163 on page)

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

Generic link text like 'click here' doesn't describe the destination.

https://webkit.org/blog/17917/release-notes-for-safari-technology-preview-241/ ("Read more"); https://webkit.org/blog/17899/introducing-the-jetstream-3-benchmark-suite/ ("Read more"); https://webkit.org/blog/17862/webkit-features-for-safari-26-4/ ("Read more"); https://webkit.org/blog/17818/announcing-interop-2026/ ("Read more"); https://webkit.org/blog/17798/webkit-features-for-safari-26-3/ ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA

title WebKit

1.45:1

#000000

#002C45

needs 4.5:1 (normal text)

16px · top of page (header area)

div WebKit

1.46:1

#000000

#002D46

needs 4.5:1 (normal text)

16px · top of page (header area)

a Downloads

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · top of page (header area)

label Feature Status

1.48:1

#000000

#002E47

needs 4.5:1 (normal text)

16px · top of page (header area)

a CSS Features

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

a Standards Positions

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

label Documentation

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

a Web Inspector

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

a Tracking Prevention

1.50:1

#000000

#002F49

needs 4.5:1 (normal text)

16px · above the fold

label Policies

1.50:1

#000000

#002F49

needs 4.5:1 (normal text)

16px · above the fold

a Project Goals

1.50:1

#000000

#002F49

needs 4.5:1 (normal text)

16px · above the fold

a Bug Prioritization

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

a Bug Report Guidelines

1.48:1

#000000

#002E48

needs 4.5:1 (normal text)

16px · above the fold

a Code Style Guidelines

1.47:1

#000000

#002D48

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 A fast, open sourc…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 Release Notes for Sa…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 Introducing the JetS…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 WebKit Features for …	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 Announcing Interop 2…	19.60:1	3.0:1	#000000	#F7F7F7	Pass
h1 WebKit features for …	19.60:1	3.0:1	#000000	#F7F7F7	Pass
title WebKit	1.45:1	4.5:1	#000000	#002C45	Fail
div WebKit	1.46:1	4.5:1	#000000	#002D46	Fail
a Downloads	1.48:1	4.5:1	#000000	#002E48	Fail
label Feature Status	1.48:1	4.5:1	#000000	#002E47	Fail
a CSS Features	1.48:1	4.5:1	#000000	#002E48	Fail
a Standards Positions	1.48:1	4.5:1	#000000	#002E48	Fail
label Documentation	1.48:1	4.5:1	#000000	#002E48	Fail
a Web Inspector	1.48:1	4.5:1	#000000	#002E48	Fail
a Tracking Prevention	1.50:1	4.5:1	#000000	#002F49	Fail
label Policies	1.50:1	4.5:1	#000000	#002F49	Fail
a Project Goals	1.50:1	4.5:1	#000000	#002F49	Fail
a Bug Prioritization	1.48:1	4.5:1	#000000	#002E48	Fail
a Bug Report Guideline…	1.48:1	4.5:1	#000000	#002E48	Fail
a Code Style Guideline…	1.47:1	4.5:1	#000000	#002D48	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.

Lighthouse Accessibility Audits

Action

Score 78/100 — 4 failing, 14 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
safari technology preview icon `div.tile > div.background-image > svg > use`
performance icon `div.tile > div.background-image > svg > use`
default icon `div.tile > div.background-image > svg > use`
default icon `div.tile > div.background-image > svg > use`
default icon `div.tile > div.background-image > svg > use`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
More Blog Posts `main#content > div.page-width > div.pagination > a.page-numbers`

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read more `div.tile > div.tile-content > p > a.readmore`
Read more `div.tile > div.tile-content > p > a.readmore`
Read more `div.tile > div.tile-content > p > a.readmore`
Read more `div.tile > div.tile-content > p > a.readmore`
Read more `div.tile > div.tile-content > p > a.readmore`

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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

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

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

●Document has a `<title>` element

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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 a valid value for its `[lang]` attribute

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

○Image elements have `[alt]` attributes

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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

6 headings

PASS

6 headings

Multiple H1 headings (6 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 A fast, open source web browser engine.
H1 Release Notes for Safari Technology Preview 241 duplicate H1
H1 Introducing the JetStream 3 Benchmark Suite duplicate H1
H1 WebKit Features for Safari 26.4 duplicate H1
H1 Announcing Interop 2026 duplicate H1
H1 WebKit features for Safari 26.3 duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

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 Page not found | WebKit ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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