Accessibility audit of php.net — scanned on Feb 20, 2026
Technology3 issues found across 2 categories
Images must have alternative text to convey their meaning to screen reader users.
WCAG 1.1.1<img src="/images/logos/php-logo-white.svg">Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button>Add text content, aria-label, or title to all <button> elements.
Pages should have a mechanism to bypass repeated navigation blocks.
WCAG 2.4.1No skip navigation link foundAdd a 'Skip to main content' link as the first focusable element on the page.
Here are the most impactful changes php.net should make to improve accessibility:
Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.
Add text content, aria-label, or title to all <button> elements.
Add a 'Skip to main content' link as the first focusable element on the page.
php.net scored 62/100 (grade C) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 3 accessibility issues on php.net. Full WCAG compliance requires addressing all critical and major issues identified above.
The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see php.net's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for php.net.
Get a free accessibility report for your website in seconds.