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

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

No <nav> landmark 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

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 ✗

Heading Hierarchy

47 headings

REVIEW

47 headings

No H1 heading found

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

H2 Laravel News
H2 Search Articles
H2 Laravel Newsletter
H3 Launch Your Dream SaaS Application with SaaSykit
H3 Get expert guidance in a few days with a Laravel code review
H2 Partners
H3 Get expert guidance in a few days with a Laravel code review
H3 The agent-first dev environment for Laravel
H3 Laravel Developers that Click into Place.
H3 Laravel Cloud is here! Zero-config managed infrastructure for Laravel apps.
H3 The Web Search API for Your LLM and AI Applications
H3 The go-to PHP IDE with extensive out-of-the-box support for Laravel and its ecosystem.
H3 Outsource to Acquaint Softtech, Sr. Laravel developers with AI expertise - $3000/Month
H2 The latest
H3 An Opinionated Agent Skill for Building REST APIs in Laravel
H3 Launch Your Dream SaaS Application with SaaSykit
H3 Generate, Parse, and Convert Documents in PHP with Paperdoc
H3 Spatie Shares Their Coding Guidelines as AI Skills
H3 AI Generative Engine Optimization for Laravel
H3 Attach PDFs Directly to Mailables in laravel-pdf 2.6.0
H2 Most Read
H3 Spatie Shares Their Coding Guidelines as AI Skills
H3 Redis Cluster Support for Queues in Laravel 13.5.0
H3 Composer 2.9.6 Fixes Two Perforce Command Injection Vulnerabilities
H3 Generate, Parse, and Convert Documents in PHP with Paperdoc
H3 AI Generative Engine Optimization for Laravel
H3 Passage: A Lightweight API Proxy Gateway for Laravel
H2 Partners
H2 Tutorials
H3 Ship AI with Laravel: Your AI Agent Has Amnesia. Let's Fix It.
H3 Ship AI with Laravel: Stop Your AI Agent from Guessing
H3 Making Laravel MongoDB Operations Idempotent: Safe Retries for Financial Transactions
H3 Ship AI with Laravel: Smart Ticket Triage with Structured Output
H3 Build an AI Chat Agent with Laravel 12, MongoDB Atlas Vector Search, and Voyage AI
H3 Building Transaction-Safe Multi-Document Operations in Laravel
H2 Laravel Packages
H3 An Opinionated Agent Skill for Building REST APIs in Laravel
H3 Generate, Parse, and Convert Documents in PHP with Paperdoc
H3 AI Generative Engine Optimization for Laravel
H3 Passage: A Lightweight API Proxy Gateway for Laravel
H3 Pretty PHP Info: A Modern Replacement for `phpinfo()`
H3 Laravel QuickBooks MCP Server: Connect QuickBooks Online to AI Clients
H3 ArtisanFlow: A Flowchart Engine for Laravel and Alpine.js
H3 Manage Software Licenses in Laravel with Laravel Licensing
H2 Subscribe to our newsletter
H2 Laravel News
H2 Search Articles

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

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 Laravel News ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 17 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
Polyscope - The agent-first dev environment for Laravel `div.shadow-card > div > p > a`
Laravel Packages `div.flex > div.flex > div.pt-4 > span.text-red-600`
News `div.flex > div.flex > div.pt-3 > span.text-red-600`
View All Links→ `div.flex > div.border > div.px-3 > a.inline-flex`
View All Jobs → `div.relative > div.px-3 > div > a.inline-flex`
Post a Job → `div.relative > div.px-3 > div > a.inline-flex`
Join free `div > form > div.flex > button.inline-flex`
View all → `section.py-20 > div.mx-auto > div.flex > a.inline-flex`
View all → `section.py-32 > div.mx-auto > div.flex > a.inline-flex`
Join free `div > form > div.flex > button.inline-flex`

These are opportunities to improve the legibility of your content.

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
div.flex > div.flex > div.aspect-[2/1] > a `div.flex > div.flex > div.aspect-[2/1] > 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-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

●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

●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

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

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

○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

○Links are distinguishable without relying on color.

○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

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

Alt Text Quality

1 of 81 images have issues

PASS

1 of 81 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

79 image(s) with good alt text

81 images 79 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	Email	none
input	text	Email	none

Link & Button Quality

1 issue(s) across 140 links and 8 buttons

PASS

1 issue(s) across 140 links and 8 buttons

1 link(s) with no accessible text

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

Got: https://laravel-news.com/attach-pdfs-directly-to-mailables-in-laravel-pdf-2-6-0

1 link(s) open in new tab without warning

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

Got: https://www.facebook.com/laravelnews

138 link(s) with descriptive text

140 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://laravel-news.com/attach-pdfs-dir…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/laravelnews	Facebook	new tab	Add '(opens in new tab)' to text

146 links and buttons have descriptive text

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

https://laravel-news.com/attach-pdfs-directly-to-mailables-in-laravel-pdf-2-6-0

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

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

https://www.facebook.com/laravelnews

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

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 Laravel Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Partners	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 The latest	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Most Read	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tutorials	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Laravel Packages	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Laravel News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Search Articles	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Launch Your Dream Sa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get expert guidance …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get expert guidance …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The agent-first dev …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Laravel Developers t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Laravel Cloud is her…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The Web Search API f…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 The go-to PHP IDE wi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Outsource to Acquain…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 An Opinionated Agent…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Launch Your Dream Sa…	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.

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