Skip to content
https://php.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
30 landmarks
FIX
30 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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
Info::
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
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 3 <nav> element(s)
Back to Top
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.
B
Heading Hierarchy
25 headings
REVIEW
25 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 PHP 8.4.20 Released!
  • H2 PHP 8.5.5 Released!
  • H2 PHP 8.5.4 Released!
  • H2 PHP 8.4.19 Released!
  • H2 PHP 8.5.3 Released!
  • H2 PHP 8.4.18 Released!
  • H2 PHP 8.5.2 Released!
  • H2 PHP 8.3.30 Released!
  • H2 PHP 8.4.17 Released!
  • H2 PHP 8.1.34 Released!
  • H2 PHP 8.4.16 Released!
  • H2 PHP 8.2.30 Released!
  • H2 PHP 8.3.29 Released!
  • H2 PHP 8.5.1 Released!
  • H2 PHP 8.5.0 Released!
  • H2 PHP 8.4.15 Released!
  • H2 PHP 8.3.28 Released!
  • H2 PHP 8.5.0 RC 5 available for testing
  • H2 PHP 8.5.0 RC4 available for testing
  • H2 PHP 8.3.27 Released!
  • H2 PHP 8.4.14 Released!
  • H2 PHP 8.5.0 RC 3 available for testing
  • H2 PHP 8.5.0 RC 2 available for testing
  • H2 PHP 8.5.0 RC 1 available for testing
  • H2 PHP 8.3.26 Released!

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

C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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'>.
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
title PHP
3.25:1
#000000
on
#4F5B93
needs 4.5:1 (normal text)
16px · top of page (header area)
a update page now
3.25:1
#000000
on
#4F5B93
needs 4.5:1 (normal text)
16px · top of page (header area)
a Downloads
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
a Documentation
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
a Get Involved
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Help
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
button Search docs
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Getting Started
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Introduction
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a A simple tutorial
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Language Reference
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Basic syntax
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Types
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · above the fold
a Variables
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Constants
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Expressions
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Operators
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Control Structures
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Functions
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
a Classes and Objects
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
title PHP3.25:14.5:1
#000000
#4F5B93
Fail
a update page now3.25:14.5:1
#000000
#4F5B93
Fail
a Downloads1.66:14.5:1
#000000
#333333
Fail
a Documentation1.66:14.5:1
#000000
#333333
Fail
a Get Involved1.66:14.5:1
#000000
#333333
Fail
a Help1.66:14.5:1
#000000
#333333
Fail
button Search docs1.66:14.5:1
#000000
#333333
Fail
a Getting Started1.66:14.5:1
#000000
#333333
Fail
a Introduction1.66:14.5:1
#000000
#333333
Fail
a A simple tutorial1.66:14.5:1
#000000
#333333
Fail
a Language Reference1.66:14.5:1
#000000
#333333
Fail
a Basic syntax1.66:14.5:1
#000000
#333333
Fail
a Types1.66:14.5:1
#000000
#333333
Fail
a Variables1.66:14.5:1
#000000
#333333
Fail
a Constants1.66:14.5:1
#000000
#333333
Fail
a Expressions1.66:14.5:1
#000000
#333333
Fail
a Operators1.66:14.5:1
#000000
#333333
Fail
a Control Structures1.66:14.5:1
#000000
#333333
Fail
a Functions1.66:14.5:1
#000000
#333333
Fail
a Classes and Objects1.66:14.5:1
#000000
#333333
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+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
1 decorative image(s) correctly marked
Info::
3 image(s) with good alt text
4 images 3 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="pattern" id="navbar__search-input">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#search-modal__inputsearchSearch docsaria-label
#navbar__search-inputsearch(Search docs)placeholder only

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

<input type="search" name="pattern" id="navbar__search-input">

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
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title PHP: Manual Quick Reference ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 20 passed
PASS
94

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.

Names and labels

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
body.home > div.elephpants > div.images > a body.home > div.elephpants > div.images > 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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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

Send Feedback