Skip to content
https://symfony.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
2
REVIEW
4
PASS
7
INFO
0
Checks
13
7 PASS 4 REVIEW 2 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found (404 error) ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Symfony
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Symfony ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Symfony Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 3 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Symfony, High Performance PHP Framework …
1.57:1
#000000
on
#2F2F2F
needs 4.5:1 (normal text)
16px · top of page (header area)
span About
3.13:1
#000000
on
#1D4ED8
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Build with confidenc…19.08:13.0:1
#000000
#F3F4F6
Pass
h2 What you can do with…19.08:13.0:1
#000000
#F3F4F6
Pass
h2 Get started with Sym…19.08:13.0:1
#000000
#F3F4F6
Pass
h2 A strategic choice f…19.08:13.0:1
#000000
#F3F4F6
Pass
h2 Empower your project…19.08:13.0:1
#000000
#F3F4F6
Pass
h2 Join the community19.08:13.0:1
#000000
#F3F4F6
Pass
h2 Symfony footer19.08:13.0:1
#000000
#F3F4F6
Pass
title Symfony, High Perfor…1.57:14.5:1
#000000
#2F2F2F
Fail
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
button Close21.00:14.5:1
#000000
#FFFFFF
Pass
span About3.13:14.5:1
#000000
#1D4ED8
Fail
a What is Symfony?19.08:14.5:1
#000000
#F3F4F6
Pass
a Community19.08:14.5:1
#000000
#F3F4F6
Pass
a News19.08:14.5:1
#000000
#F3F4F6
Pass
a Contributing19.08:14.5:1
#000000
#F3F4F6
Pass
a Support19.08:14.5:1
#000000
#F3F4F6
Pass
span Documentation19.08:14.5:1
#000000
#F3F4F6
Pass
a Symfony Docs19.08:14.5:1
#000000
#F3F4F6
Pass
a Symfony Book19.08:14.5:1
#000000
#F3F4F6
Pass
a Screencasts18.91:14.5:1
#000000
#F2F3F5
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.

A+
Landmark Structure
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer
A+
Heading Hierarchy
8 headings
PASS
8 headings
Info::
Single H1 present
  • H1 Build with confidence at any scale
  • H2 What you can do with Symfony
  • H2 Get started with Symfony
  • H2 A strategic choice for long-term success
  • H2 Empower your projects with Symfony solutions
  • H2 Join the community
  • H2 Symfony footer
  • H3 Follow Symfony
A
Alt Text Quality
1 of 1 images have issues
PASS
1 of 1 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
1 images 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#color-scheme-switcherselectSite appearance:for/id
qsearchSearch in Symfony documentationaria-label
A
Favicon & Branding
6 icon(s) detected
PASS
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 light dark ✓Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Lighthouse Accessibility Audits
Score 90/100 — 4 failing, 30 passed
PASS
90

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
SymfonyLive Berlin 2026 div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > a.top-horizontal-highlight-title
main div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3
production div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3
Symfony is a powerful PHP framework that empowers developers to build scalable,… section.section-what > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle
Symfony packages are battle-tested and ready to solve all your needs article.content > section.section-metrics > div.ui-page-container > p.section-metrics-heading
Everything you need to get up to speed quickly! section.section-start > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle
Predictable, secure, and built to last — Symfony meets the demands of all compa… div.d-xl-flex > div.col-xl-6 > div.ui-heading > p.ui-heading-subtitle

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
All rights reserved div.ui-page-container > div.footer-bottom > p.mb-3 > a

These are opportunities to improve the legibility of your content.

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.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Apr 23–24, 2026 SymfonyLive Berlin 2026 In English Jun 4, 2026 SymfonyDay Montr… div.d-lg-flex > div.col-lg-12 > div.community-item > table
○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●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.
●Elements with visible text labels have matching accessible names.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○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 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
○Skip links are focusable.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback