Accessibility

D

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

No banner (header) landmark

No contentinfo (footer) 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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

F

Heading Hierarchy

Action

44 headings, 20 skip(s)

FIX

44 headings, 20 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

H2 Making an Asynchronous Clocking Drum Machine App in Perl
H5 Read it skipped
H2 Musical Rhythms with Math in Perl
H5 Read it skipped
H2 Fastmail Donates USD 10,000 to The Perl and Raku Foundation
H5 Read it skipped
H2 Cast-Iron Community: Your Chance to Sponsor TPRC 2026
H5 Read it skipped
H2 Podlite comes to Perl: a lightweight block-based markup language for everyday use
H5 Read it skipped
H2 Announcing the Perl Toolchain Summit 2026
H5 Read it skipped
H2 DuckDuckGo Donates $25,000 to The Perl and Raku Foundation v2025
H5 Read it skipped
H2 Geizhals Preisvergleich Donates USD 10,000 to The Perl and Raku Foundation
H5 Read it skipped
H2 Announcing Dancer2 2.0.0
H5 Read it skipped
H2 My Guilty Perl Obsession
H5 Read it skipped
H2 SUSE Donates USD 11,500 to The Perl and Raku Foundation
H5 Read it skipped
H2 MetaCPAN's Traffic Crisis: An Eventual Success Story
H5 Read it skipped
H2 Analysing FIT data with Perl: interactive data analysis
H5 Read it skipped
H2 Proxmox Donates €10,000 to The Perl and Raku Foundation
H5 Read it skipped
H2 Analysing FIT data with Perl: producing PNG plots
H5 Read it skipped
H2 Analysing FIT data with Perl: basic beginnings
H5 Read it skipped
H2 Introducing DBIx::Class::ResultSet::PrettyPrint
H5 Read it skipped
H2 Building Map::Tube::<*> maps, a HOWTO: alternative connections
H5 Read it skipped
H2 SlapbirdAPM, a Free and Open-Source Observability Tool for Perl Web Applications
H5 Read it skipped
H2 The Perl Toolchain Summit 2025: Security, Testing, and Community Collaboration
H5 Read it skipped
H5 Site Map
H5 Contact Us
H5 License
H5 Legal

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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

F

Alt Text Quality

Action

5 of 13 images have issues

FIX

5 of 13 images have issues

5 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

5 image-in-link without alt text

An image inside a link with no alt creates an empty link.

1 decorative image(s) correctly marked

7 image(s) with good alt text

13 images 7 good alt text 1 decorative 5 missing

Issue	Count
missing	5 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

Link & Button Quality

Action

6 issue(s) across 146 links and 1 buttons

FIX

6 issue(s) across 146 links and 1 buttons

6 link(s) with no accessible text

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

Got: https://duckduckgo.com; https://www.webpros.com/; https://www.proxmox.com/en/; https://www.suse.com/; https://geizhals.de/; https://www.fastmail.com/

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/about"]

6 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/

133 link(s) with descriptive text

146 links

6 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/about	ABOUT	img no alt	Add alt attribute to the image
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://duckduckgo.com	(empty)	empty	Add link text or aria-label
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://www.webpros.com/	(empty)	empty	Add link text or aria-label
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://www.proxmox.com/en/	(empty)	empty	Add link text or aria-label
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://www.suse.com/	(empty)	empty	Add link text or aria-label
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://geizhals.de/	(empty)	empty	Add link text or aria-label
https://www.perlfoundation.org/	TPRF	new tab	Add '(opens in new tab)' to text
https://www.fastmail.com/	(empty)	empty	Add link text or aria-label

134 links and buttons have descriptive text

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

https://duckduckgo.com; https://www.webpros.com/; https://www.proxmox.com/en/; https://www.suse.com/; https://geizhals.de/; https://www.fastmail.com/

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/about"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/; https://www.perlfoundation.org/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

F

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

D

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.

D

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.

D

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 ✗

F

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

Search

Skip Link

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

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Lighthouse Accessibility Audits

Action

Score 70/100 — 6 failing, 14 passed

REVIEW

70

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
Gene Boggs `div.row > div.col-sm-9 > p.blog-post-meta > a`
development `div.col-sm-9 > div.tags > div.category > a`
Asynchronous `div.col-sm-9 > div.tags > div.tag > a`
Drums `div.col-sm-9 > div.tags > div.tag > a`
MIDI `div.col-sm-9 > div.tags > div.tag > a`
Music `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Gene Boggs `div.row > div.col-sm-9 > p.blog-post-meta > a`
development `div.col-sm-9 > div.tags > div.category > a`
MIDI `div.col-sm-9 > div.tags > div.tag > a`
Music `div.col-sm-9 > div.tags > div.tag > a`
Math `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
tprf `div.col-sm-9 > div.tags > div.tag > a`
community `div.col-sm-9 > div.tags > div.tag > a`
sponsors `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
tprc `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Aliaksandr Zahatski `div.row > div.col-sm-9 > p.blog-post-meta > a`
tooling `div.col-sm-9 > div.tags > div.category > a`
documentation `div.col-sm-9 > div.tags > div.tag > a`
markdown `div.col-sm-9 > div.tags > div.tag > a`
pod `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Philippe Bruhat (BooK) `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
perl-toolchain-summit `div.col-sm-9 > div.tags > div.tag > a`
pts `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Jason A. Crome `div.row > div.col-sm-9 > p.blog-post-meta > a`
web `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Bryan S. Katz `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Leo Lapworth `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Paul Cochrane `div.row > div.col-sm-9 > p.blog-post-meta > a`
data `div.col-sm-9 > div.tags > div.category > a`
science `div.col-sm-9 > div.tags > div.tag > a`
sport `div.col-sm-9 > div.tags > div.tag > a`
cycling `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Olaf Alders `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Paul Cochrane `div.row > div.col-sm-9 > p.blog-post-meta > a`
data `div.col-sm-9 > div.tags > div.category > a`
science `div.col-sm-9 > div.tags > div.tag > a`
sport `div.col-sm-9 > div.tags > div.tag > a`
cycling `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Paul Cochrane `div.row > div.col-sm-9 > p.blog-post-meta > a`
data `div.col-sm-9 > div.tags > div.category > a`
science `div.col-sm-9 > div.tags > div.tag > a`
sport `div.col-sm-9 > div.tags > div.tag > a`
cycling `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Paul Cochrane `div.row > div.col-sm-9 > p.blog-post-meta > a`
cpan `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Paul Cochrane `div.row > div.col-sm-9 > p.blog-post-meta > a`
tutorials `div.col-sm-9 > div.tags > div.category > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Rawley Fowler `div.row > div.col-sm-9 > p.blog-post-meta > a`
tooling `div.col-sm-9 > div.tags > div.category > a`
observability `div.col-sm-9 > div.tags > div.tag > a`
performance `div.col-sm-9 > div.tags > div.tag > a`
monitoring `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
Breno G. de Oliveira (garu) `div.row > div.col-sm-9 > p.blog-post-meta > a`
community `div.col-sm-9 > div.tags > div.category > a`
perl-toolchain-summit `div.col-sm-9 > div.tags > div.tag > a`
pts `div.col-sm-9 > div.tags > div.tag > a`
Read it `div.row > div.col-sm-9 > h5 > a.moretag`
« Older Posts `div.col-sm-9 > nav#nav-below > div.older > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
TPRF `div.col-sm-3 > div.row > div.col-sm-12 > a`
Learn more `div#perl-ad > p > span#perl-ad-link > a`
Get Perl `div#perlresourcelinks > ul > li > a`
Learn About Perl `div#perlresourcelinks > ul > li > a`
Get Perl Code `div#perlresourcelinks > ul > li > a`
Help Perl `div#perlresourcelinks > ul > li > a`
Home `div.col-md-1 > ul > li > a`
About `div.col-md-1 > ul > li > a`
Authors `div.col-md-1 > ul > li > a`
Categories `div.col-md-1 > ul > li > a`
Tags `div.col-md-1 > ul > li > a`
To get in touch, submit an issue to perladvent/perldotcom on GitHub. `div.container > div.row > div.col-md-3 > p`
submit an issue to perladvent/perldotcom `div.row > div.col-md-3 > p > a`
This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Un… `div.container > div.row > div.col-md-2 > p`
Creative Commons Attribution-NonCommercial 3.0 Unported License `div.row > div.col-md-2 > p > a`
Perl.com and the authors make no representations with respect to the accuracy o… `div.container > div.row > div.col-md-5 > p`

These are opportunities to improve the legibility of your content.

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
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`
Read it `article > div.row > div.col-sm-9 > h5`

These are opportunities to improve keyboard navigation in your application.

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
div.row > div.col-sm-12 > a > img `div.row > div.col-sm-12 > a > img`
div.row > div.col-sm-12 > a > img `div.row > div.col-sm-12 > a > img`
div.row > div.col-sm-12 > a > img `div.row > div.col-sm-12 > a > img`
div.row > div.col-sm-12 > a > img `div.row > div.col-sm-12 > a > img`
div.row > div.col-sm-12 > a > img `div.row > div.col-sm-12 > a > 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.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`
div.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`
div.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`
div.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`
div.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`
div.col-sm-3 > div.row > div.col-sm-12 > a `div.col-sm-3 > div.row > div.col-sm-12 > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Home About Authors Categories Tags `div.container > div.row > div.col-md-1 > ul`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Get Perl `div#perlresourcelinks > ul > li > a`
Learn About Perl `div#perlresourcelinks > ul > li > a`
Get Perl Code `div#perlresourcelinks > ul > li > a`
Help Perl `div#perlresourcelinks > ul > li > a`
Home `div.col-md-1 > ul > li > a`
About `div.col-md-1 > ul > li > a`
Authors `div.col-md-1 > ul > li > a`
Categories `div.col-md-1 > ul > li > a`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Buttons have an accessible name

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

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

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○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 use only permitted 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

○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

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

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

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

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	(SEARCH)	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

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
h2 Making an Asynchrono…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Musical Rhythms with…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Fastmail Donates USD…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cast-Iron Community:…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Podlite comes to Per…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Announcing the Perl …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 DuckDuckGo Donates $…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Geizhals Preisvergle…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Announcing Dancer2 2…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 My Guilty Perl Obses…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SUSE Donates USD 11,…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 MetaCPAN's Traffic C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Analysing FIT data w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Proxmox Donates €1…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Analysing FIT data w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Analysing FIT data w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Introducing DBIx::Cl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Building Map::Tube::…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 SlapbirdAPM, a Free …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The Perl Toolchain S…	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.