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 4 REVIEW 5 FIX

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

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

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 5 pass AA only

title PHP-FIG — PHP Framework Interop Group …

1.25:1

#000000

#0A202B

needs 4.5:1 (normal text)

16px · top of page (header area)

span PHP-FIG

1.25:1

#000000

#0A202B

needs 4.5:1 (normal text)

16px · top of page (header area)

span The PHP Framework Interop Group

1.25:1

#000000

#0A202B

needs 4.5:1 (normal text)

16px · top of page (header area)

label Menu

1.25:1

#000000

#0A202B

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

3.79:1

#000000

#247652

needs 4.5:1 (normal text)

16px · above the fold

a Blog

3.79:1

#000000

#247652

needs 4.5:1 (normal text)

16px · above the fold

a PSRs

3.84:1

#000000

#257753

needs 4.5:1 (normal text)

16px · above the fold

a PERs

3.79:1

#000000

#247652

needs 4.5:1 (normal text)

16px · above the fold

a Personnel

3.84:1

#000000

#257753

needs 4.5:1 (normal text)

16px · above the fold

a Bylaws

3.90:1

#000000

#267854

needs 4.5:1 (normal text)

16px · above the fold

a FAQs

3.84:1

#000000

#257753

needs 4.5:1 (normal text)

16px · above the fold

a Get Involved

3.79:1

#000000

#247652

needs 4.5:1 (normal text)

16px · above the fold

p Welcome to the PHP Framework Interop Gro…

3.90:1

#000000

#267854

needs 4.5:1 (normal text)

16px · mid-page

a View recommendations (PSRs)

4.18:1

#000000

#2B7D59

needs 4.5:1 (normal text)

16px · mid-page

a Frequently asked questions

4.30:1

#000000

#2D7F5B

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Moving PHP forward t…	3.84:1	3.0:1	#000000	#257753	Pass
h2 Autoloading	4.48:1	3.0:1	#000000	#30825E	Pass
h2 Interfaces	3.38:1	3.0:1	#000000	#256D4E	Pass
h2 HTTP	3.38:1	3.0:1	#000000	#256D4E	Pass
h2 Coding Styles	3.38:1	3.0:1	#000000	#256D4E	Pass
title PHP-FIG — PHP Fram…	1.25:1	4.5:1	#000000	#0A202B	Fail
span PHP-FIG	1.25:1	4.5:1	#000000	#0A202B	Fail
span The PHP Framework In…	1.25:1	4.5:1	#000000	#0A202B	Fail
label Menu	1.25:1	4.5:1	#000000	#0A202B	Fail
a Home	3.79:1	4.5:1	#000000	#247652	Fail
a Blog	3.79:1	4.5:1	#000000	#247652	Fail
a PSRs	3.84:1	4.5:1	#000000	#257753	Fail
a PERs	3.79:1	4.5:1	#000000	#247652	Fail
a Personnel	3.84:1	4.5:1	#000000	#257753	Fail
a Bylaws	3.90:1	4.5:1	#000000	#267854	Fail
a FAQs	3.84:1	4.5:1	#000000	#257753	Fail
a Get Involved	3.79:1	4.5:1	#000000	#247652	Fail
p Welcome to the PHP F…	3.90:1	4.5:1	#000000	#267854	Fail
a View recommendations…	4.18:1	4.5:1	#000000	#2B7D59	Fail
a Frequently asked que…	4.30:1	4.5:1	#000000	#2D7F5B	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

Score 84/100 — 3 failing, 12 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.

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
MENU `header.site_header > div.center > nav.site_menu > label.site_menu__dropdown_button`
View recommendations (PSRs) `div.center > div.home_banner__content > div.home_banner__links > a.home_banner__link`
Frequently asked questions `div.center > div.home_banner__content > div.home_banner__links > a.home_banner__link`
AUTOLOADING `li.home_features__item > div.center > div.home_features__content > h2.home_features__title`
PSR-4: Improved Autoloading `div.home_features__content > ul.home_features__links > li > a.home_features__link`
INTERFACES `li.home_features__item > div.center > div.home_features__content > h2.home_features__title`
PSR-3: Logger Interface `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-6: Caching Interface `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-11: Container Interface `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-13: Hypermedia Links `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-14: Event Dispatcher `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-16: Simple Cache `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-20: Clock `div.home_features__content > ul.home_features__links > li > a.home_features__link`
/** * Describes a logger instance */ `div.home_features__code > pre > code.language-php > span.hljs-comment`
HTTP `li.home_features__item > div.center > div.home_features__content > h2.home_features__title`
PSR-7: HTTP Message Interfaces `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-15: HTTP Handlers `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-17: HTTP Factories `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-18: HTTP Client `div.home_features__content > ul.home_features__links > li > a.home_features__link`
/** * Representation of an outgoing, client-side request. */ `div.home_features__code > pre > code.language-php > span.hljs-comment`
CODING STYLES `li.home_features__item > div.center > div.home_features__content > h2.home_features__title`
PER Coding Style `div.home_features__content > ul.home_features__links > li > a.home_features__link`
PSR-1: Basic Coding Standard `div.home_features__content > ul.home_features__links > li > a.home_features__link`
// method body `div.home_features__code > pre > code.language-php > span.hljs-comment`
Follow us on Mastodon `div.site_footer_links__content > ul.site_footer_links__list > li.site_footer_links__item > a.site_footer_links__link`
Follow us on Bluesky `div.site_footer_links__content > ul.site_footer_links__list > li.site_footer_links__item > a.site_footer_links__link`
Discuss on Discord `div.site_footer_links__content > ul.site_footer_links__list > li.site_footer_links__item > a.site_footer_links__link`
Contribute via GitHub `div.site_footer_links__content > ul.site_footer_links__list > li.site_footer_links__item > a.site_footer_links__link`
Join our mailing list `div.site_footer_links__content > ul.site_footer_links__list > li.site_footer_links__item > a.site_footer_links__link`
© 2026 PHP Framework Interop Group. `body > footer.site_footer > div.center > span.site_footer__section`
Site design by Jonathan Reinink. `body > footer.site_footer > div.center > span.site_footer__section`
Jonathan Reinink `footer.site_footer > div.center > span.site_footer__section > a.site_footer__link`
Hosting sponsored by the PHP PaaS `body > footer.site_footer > div.center > span.site_footer__section`
PHP PaaS `footer.site_footer > div.center > span.site_footer__section > a.site_footer__link`

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
PHP PaaS `footer.site_footer > div.center > span.site_footer__section > a.site_footer__link`

These are opportunities to improve the legibility of your content.

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●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

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

○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

○Elements use only permitted ARIA attributes

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

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

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

○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 an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

○Identical links have the same purpose.

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

Heading Hierarchy

5 headings

PASS

5 headings

Single H1 present

H1 Moving PHP forward through collaboration and standards.
H2 Autoloading
H2 Interfaces
H2 HTTP
H2 Coding Styles

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#site_menu__dropdown_checkbox	checkbox	Menu	for/id

Link & Button Quality

33 links, 0 buttons — all OK

PASS

33 links, 0 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://twitter.com/reinink; https://platform.sh/?utm_campaign=sponsored_sites&utm_source=php_fig; https://platform.sh/?utm_campaign=sponsored_sites&utm_source=php_fig

30 link(s) with descriptive text

33 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/reinink	Jonathan Reinink	new tab	Add '(opens in new tab)' to text
https://platform.sh/?utm_campaign=sponso…	platform.sh logo	new tab	Add '(opens in new tab)' to text
https://platform.sh/?utm_campaign=sponso…	PHP PaaS	new tab	Add '(opens in new tab)' to text

30 links and buttons have descriptive text

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

https://twitter.com/reinink; https://platform.sh/?utm_campaign=sponsored_sites&utm_source=php_fig; https://platform.sh/?utm_campaign=sponsored_sites&utm_source=php_fig

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

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