Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

No landmarks

FIX

No 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

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: App

192x192 icon present

PWA Install Criteria Not Installable

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

Name App Icons 6 icon(s)

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

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 ✗

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

Favicon & Branding

21 icon(s) detected

REVIEW

21 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

Lighthouse Accessibility Audits

Score 88/100 — 4 failing, 23 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
Open Source PHP class for generating PDF documents `div#layout > div#main > div.header > h2`
tc-lib-pdf is the new generation of TCPDF for modern PHP. Generate production P… `div#layout > div#main > div.content > p`
tc-lib-pdf `div#main > div.content > p > strong`
TCPDF started in 2002 and became one of the most widely adopted PDF engines in … `div#layout > div#main > div.content > p`
tc-lib-pdf `div#main > div.content > p > code`
Install: `div#main > div.content > ul > li`
GitHub: https://github.com/tecnickcom/tc-lib-pdf `div#main > div.content > ul > li`
https://github.com/tecnickcom/tc-lib-pdf `div.content > ul > li > a`
API docs: /docs/srcdoc/tc-lib-pdf `div#main > div.content > ul > li`
/docs/srcdoc/tc-lib-pdf `div.content > ul > li > a`
Examples: /examples/ `div#main > div.content > ul > li`
/examples/ `div.content > ul > li > a`
Packagist: https://packagist.org/packages/tecnickcom/tc-lib-pdf `div#main > div.content > ul > li`
https://packagist.org/packages/tecnickcom/tc-lib-pdf `div.content > ul > li > a`
tc-lib-pdf is a deterministic, pure-PHP PDF toolkit with no external rendering … `div#layout > div#main > div.content > p`
tc-lib-pdf `div#main > div.content > p > code`
Modern baseline: PHP 8.1+, Composer-first, modular dependencies. `div#main > div.content > ul > li`
Modern baseline: `div.content > ul > li > strong`
Production features: advanced typography, graphics, security, standards, and fo… `div#main > div.content > ul > li`
Production features: `div.content > ul > li > strong`
Predictable output: deterministic generation suitable for invoices, reports, la… `div#main > div.content > ul > li`
Predictable output: `div.content > ul > li > strong`
Flexible adoption: use the full stack or install only the tc-lib packages your … `div#main > div.content > ul > li`
Flexible adoption: `div.content > ul > li > strong`
The legacy TCPDF repository is deprecated: `div#layout > div#main > div.content > p`
Legacy library: https://github.com/tecnickcom/TCPDF `div#main > div.content > ul > li`
https://github.com/tecnickcom/TCPDF `div.content > ul > li > a`
New library: https://github.com/tecnickcom/tc-lib-pdf `div#main > div.content > ul > li`
https://github.com/tecnickcom/tc-lib-pdf `ul > li > strong > a`
Recommendation: `div#main > div.content > p > strong`
Starting a new project: use tc-lib-pdf. `div#main > div.content > ul > li`
tc-lib-pdf `div.content > ul > li > strong`
Running legacy TCPDF in production: keep it stable short-term and plan phased m… `div#main > div.content > ul > li`
Migration matters because tc-lib-pdf is where active evolution continues. `div#layout > div#main > div.content > p`
PHP 8.1+ `div#main > div.content > ul > li`
Composer `div#main > div.content > ul > li`
Optional extensions: gd, zlib `div#main > div.content > ul > li`
gd `div.content > ul > li > code`
zlib `div.content > ul > li > code`
'/../vendor/tecnickcom/tc-lib-pdf-font/target/fonts' `code.language-php > span > span > span`
'helvetica' `code.language-php > span > span > span`
12 `code.language-php > span > span > span`
Invoices, receipts, and financial statements `div#main > div.content > ul > li`
Shipping labels and barcode-driven logistics documents `div#main > div.content > ul > li`
Compliance and archival PDFs (including PDF/A workflows) `div#main > div.content > ul > li`
Branded reports with custom fonts, SVG, and advanced layout controls `div#main > div.content > ul > li`
Interactive documents with forms, annotations, and signatures `div#main > div.content > ul > li`
Full UTF-8 Unicode and right-to-left language support `div#main > div.content > ul > li`
TrueTypeUnicode, OpenTypeUnicode v1, TrueType, OpenType v1, Type1, and CID-0 fo… `div#main > div.content > ul > li`
Font subsetting for smaller files `div#main > div.content > ul > li`
TeX-style language-aware hyphenation, optional zero-width breakpoints, and trac… `div#main > div.content > ul > li`
Text rendering modes: fill, stroke, and clipping `div#main > div.content > ul > li`
Automatic line breaks, page breaks, and justified text `div#main > div.content > ul > li`
Standard and custom page sizes, margins, and measurement units `div#main > div.content > ul > li`
HTML and CSS rendering `div#main > div.content > ul > li`
SVG rendering `div#main > div.content > ul > li`
Multi-column layouts and no-write page regions `div#main > div.content > ul > li`
Headers, footers, reusable page content, bookmarks, named destinations, and tab… `div#main > div.content > ul > li`
Automatic page numbering, page groups, page box control, and page reordering `div#main > div.content > ul > li`
Native JPEG, PNG, and SVG support `div#main > div.content > ul > li`
Extended image support through optional GD formats `div#main > div.content > ul > li`
Geometric drawing and 2D transformations `div#main > div.content > ul > li`
Linear/radial and mesh gradients, crop marks, and registration bars `div#main > div.content > ul > li`
ICC profiles, grayscale/RGB/CMYK/spot colors, transparency, and overprint contr… `div#main > div.content > ul > li`
Password and certificate-based encryption (RC4 and AES up to 256-bit) `div#main > div.content > ul > li`
Digital signatures: detached CMS (PKCS#7) signatures with configurable appearan… `div#main > div.content > ul > li`
RFC 3161 TSA timestamps embedded in CMS signatures with configurable digest, po… `div#main > div.content > ul > li`
LTV (Long-Term Validation) embedding in the same PDF revision: /DSS, /VRI, /OCS… `div#main > div.content > ul > li`
/DSS `div.content > ul > li > code`
/VRI `div.content > ul > li > code`
/OCSPs `div.content > ul > li > code`
/CRLs `div.content > ul > li > code`
/Certs `div.content > ul > li > code`
Rich annotations: links, notes, attachments, markup, widgets, and media `div#main > div.content > ul > li`
JavaScript embedding `div#main > div.content > ul > li`
PDF/A (1/2/3 with a/b/u conformance levels) and PDF/X support `div#main > div.content > ul > li`
1D and 2D barcodes through tc-lib-barcode `div#main > div.content > ul > li`
tc-lib-barcode `div.content > ul > li > code`
Interactive AcroForm fields `div#main > div.content > ul > li`
XObject templates and layers with visibility controls `div#main > div.content > ul > li`
Multiple output targets: browser display, download, file save, and MIME attachm… `div#main > div.content > ul > li`
Factur-X / ZUGFeRD workflows via embedded XML in PDF/A-3 `div#main > div.content > ul > li`
tc-lib-pdf is built on a set of focused, independently versioned packages. Each… `div#layout > div#main > div.content > p`
tc-lib-pdf `div#main > div.content > p > code`
tc-lib-pdf : Top-level PDF generation library; composes the full package stack. `div#main > div.content > ul > li`
tc-lib-pdf `div.content > ul > li > strong`
tc-lib-barcode : Generates 1D and 2D barcodes (QR, Data Matrix, Code 128, and … `div#main > div.content > ul > li`
tc-lib-barcode `ul > li > strong > a`
tc-lib-color : Color conversion and management across RGB, CMYK, HSL, and spot… `div#main > div.content > ul > li`
tc-lib-color `ul > li > strong > a`
tc-lib-file : File and data-URI helpers used internally for asset loading. `div#main > div.content > ul > li`
tc-lib-file `ul > li > strong > a`
tc-lib-unicode : Unicode string processing: bidirectional text, normalization,… `div#main > div.content > ul > li`
tc-lib-unicode `ul > li > strong > a`
tc-lib-unicode-data : Raw Unicode character data tables used by tc-lib-unicode. `div#main > div.content > ul > li`
tc-lib-unicode-data `ul > li > strong > a`
tc-lib-pdf-encrypt : PDF encryption: RC4 and AES (up to 256-bit), permissions,… `div#main > div.content > ul > li`
tc-lib-pdf-encrypt `ul > li > strong > a`
tc-lib-pdf-filter : PDF stream filters: FlateDecode, ASCII85, LZW, and others. `div#main > div.content > ul > li`
tc-lib-pdf-filter `ul > li > strong > a`
tc-lib-pdf-font : Font loading, subsetting, and embedding for all supported fo… `div#main > div.content > ul > li`
tc-lib-pdf-font `ul > li > strong > a`
tc-lib-pdf-graph : Vector graphics primitives: paths, transformations, gradien… `div#main > div.content > ul > li`
tc-lib-pdf-graph `ul > li > strong > a`
tc-lib-pdf-image : Image loading and embedding: JPEG, PNG, SVG, and GD-backed … `div#main > div.content > ul > li`
tc-lib-pdf-image `ul > li > strong > a`
tc-lib-pdf-page : Page geometry, margins, boxes, and page-level attributes. `div#main > div.content > ul > li`
tc-lib-pdf-page `ul > li > strong > a`
tc-lib-pdf-parser : Reads and parses existing PDF files for import or manipula… `div#main > div.content > ul > li`
tc-lib-pdf-parser `ul > li > strong > a`
Keep legacy TCPDF stable in production while planning migration. `div#main > div.content > ol > li`
Start new features on tc-lib-pdf. `div#main > div.content > ol > li`
tc-lib-pdf `div.content > ol > li > code`
Move legacy document flows incrementally: one template, one module, or one serv… `div#main > div.content > ol > li`
Validate outputs with your existing PDF regression checks. `div#main > div.content > ol > li`
Read the documentation `div#main > div.content > ul > li`
documentation `div.content > ul > li > a`
Explore examples `div#main > div.content > ul > li`
examples `div.content > ul > li > a`
/examples/007_example_signature_basic/ `div.content > ul > li > a`
/examples/008_example_signature_timestamp/ `div.content > ul > li > a`
/examples/009_example_signature_ltv/ `div.content > ul > li > a`
Browse project packages on /projects/ `div#main > div.content > ul > li`
/projects/ `div.content > ul > li > a`
View source and contribute on GitHub `div#main > div.content > ul > li`
GitHub `div.content > ul > li > a`
If this project helps your work, please consider supporting development via Pay… `div#layout > div#main > div.content > p`
PayPal `div#main > div.content > p > a`
© 2004-2026 – Nicola Asuni - Tecnick.com - All rights reserved. `body > div#layout > div.footerbar > span.copyright`
Nicola Asuni `div#layout > div.footerbar > span.copyright > a`
Tecnick.com `div#layout > div.footerbar > span.copyright > a`
about - disclaimer - privacy `div#layout > div.footerbar > span.copyright > a`

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
/projects/ `div.content > ul > li > a`
GitHub `div.content > ul > li > a`
PayPal `div#main > div.content > p > a`

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
body > div#layout > a#menuLink `body > div#layout > a#menuLink`

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

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

●`[role]` values are valid

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

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

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

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

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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

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

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

Heading Hierarchy

18 headings

PASS

18 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 TCPDF
H2 Open Source PHP class for generating PDF documents
H2 Start Here
H2 Why tc-lib-pdf
H2 Legacy TCPDF vs New tc-lib-pdf
H2 Requirements
H2 Quick Start
H2 What You Can Build
H2 Key Features
H3 Text and Typography
H3 Layout and Rendering
H3 Images and Graphics
H3 Security and Standards
H3 Advanced Workflows
H2 tc-lib-* Ecosystem
H2 Migration Path
H2 Next Steps
H1 Opt out of the sale or sharing of personal information duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 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
#gsc-i-id1	text	search	aria-label

Link & Button Quality

1 issue(s) across 65 links and 4 buttons

PASS

1 issue(s) across 65 links and 4 buttons

1 link(s) with no accessible text

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

Got: #menu

1 link(s) open in new tab without warning

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

Got: https://github.com/tecnickcom/tc-lib-pdf

63 link(s) with descriptive text

65 links

1 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#menu	(empty)	empty	Add link text or aria-label
https://github.com/tecnickcom/tc-lib-pdf	GitHub	new tab	Add '(opens in new tab)' to text

67 links and buttons have descriptive text

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

#menu

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://github.com/tecnickcom/tc-lib-pdf

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
h1 TCPDF	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Opt out of the sale …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Open Source PHP clas…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start Here	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why tc-lib-pdf	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Legacy TCPDF vs New …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Requirements	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quick Start	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What You Can Build	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Key Features	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 tc-lib-* Ecosystem	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Migration Path	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Next Steps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Text and Typography	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Layout and Rendering	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Images and Graphics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Security and Standar…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Advanced Workflows	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title TCPDF	21.00:1	4.5:1	#000000	#FFFFFF	Pass
i	21.00:1	4.5: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.