Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-78iuvl

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.

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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://www.ocaml.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.ocaml.org/manifest.json

Manifest contains invalid JSON.

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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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">; <input type="search" name="q">

2 controls

0 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
q	search	(Search OCaml packages)	placeholder only
q	search	(Search OCaml packages)	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

Link & Button Quality

4 issue(s) across 81 links and 11 buttons

REVIEW

4 issue(s) across 81 links and 11 buttons

3 link(s) with generic text

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

Got: /news/sigplan_announcement ("Read more"); /academic-users ("Learn more"); /industrial-users ("Learn more")

1 button(s) with no accessible text

78 link(s) with descriptive text

81 links

0 empty

3 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/news/sigplan_announcement	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Sigplan Announcement
/academic-users	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Academic Users
/industrial-users	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Industrial Users
<button>	(empty)	empty	Add button text or aria-label

88 links and buttons have descriptive text

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

/news/sigplan_announcement ("Read more"); /academic-users ("Learn more"); /industrial-users ("Learn 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

A+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H1 OCaml
H2 The OCaml Compiler has been recognised by SIGPLAN for their prestigious Programming Languages Software Award
H2 Trusted by Industry Leaders
H2 Why OCaml?
H3 RELIABILITY Powerful Type Safety Made Simple
H3 First-Class Editor and Tooling
H3 PERFORMANCE Fast Compiler and Applications
H2 Exceptionally Robust and Reliable
H3 Releases
H3 5.4.1 (2026-02-17)
H3 5.4.0 (2025-10-09)
H3 Changelog
H3 Compiler and Platform Tools
H2 Users of OCaml
H3 For Educators
H3 For Industrial Users
H2 Curated Resources
H2 OCaml Packages
H2 Footer
H3 About OCaml
H3 Resources
H3 Ecosystem
H3 Policies

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

1 image(s) with alt text over 125 characters

10 decorative image(s) correctly marked

24 image(s) with good alt text

35 images 24 good alt text 10 decorative

Issue	Count
too long	1 image(s)

A+

Dark Mode Support

Full dark mode support

PASS

Full dark mode support

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: white

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta white ✓Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 OCaml	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 has been	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 for their prestigiou…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted by Industry …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why OCaml?	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Exceptionally Robust…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Users of OCaml	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Curated Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 OCaml Packages	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 First-Class Editor a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Releases	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 5.4.1	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 5.4.0	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Changelog	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Compiler and Platfor…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 For Educators	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 For Industrial Users	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About OCaml	21.00:1	3.0: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.

Lighthouse Accessibility Audits

Score 92/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.

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
val square : int -> int = < fun > `pre#output > code > span > i.text-content`
- : int = 9 `pre#output > code > span > i.text-content`
val factorial : int -> int = < fun > `pre#output > code > span > i.text-content`
- : int = 120 `pre#output > code > span > i.text-content`
- : int = 14400 `pre#output > code > span > i.text-content`

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
Success Stories `div.container-fluid > div.text-center > div.text-content > a.text-primary`

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.

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

●`[aria-hidden="true"]` elements do not contain focusable descendents

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

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