nginx.com Accessibility Report

Accessibility audit of nginx.com — scanned on Feb 20, 2026

Technology
0 /100
F Critical Issues

7 issues found across 2 categories

3 Critical 4 Major

WCAG Compliance Overview

Perceivable 2 issues
Operable 3 issues
Understandable 0 issues
Robust 2 issues

Issues Found

Links missing accessible name

Critical

Links must have discernible text so screen reader users understand their purpose.

WCAG 2.4.4
7 element(s) affected
  • <a href="/">
  • <a href="/">
  • <a href="https://x.com/F5">
  • <a href="https://www.linkedin.com/company/f5/">
  • <a href="https://www.facebook.com/f5incorporated">
How to fix

Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

Form inputs missing labels

Critical

Form elements must have associated labels so users know what information to enter.

WCAG 1.3.1
3 element(s) affected
  • <input type="text" name="(no name)">
  • <input type="text" name="(no name)">
  • <select name="(no name)">
How to fix

Add <label> elements with matching for attributes, or use aria-label.

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
5 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

Add text content, aria-label, or title to all <button> elements.

Heading levels skip order

Major

Headings should follow a logical order (h1 → h2 → h3) without skipping levels.

WCAG 1.3.1
1 element(s) affected
  • <h6> "Featured" (after h2)
How to fix

Restructure headings to follow sequential order. Don't skip from h1 to h3.

Duplicate element IDs

Major

Element IDs must be unique to ensure correct assistive technology behavior.

WCAG 4.1.1
8 element(s) affected
  • id="clip0_14435_426"
  • id="anchor-label"
  • id="next-steps"
How to fix

Make each id attribute value unique within the page.

No skip navigation link

Major

Pages should have a mechanism to bypass repeated navigation blocks.

WCAG 2.4.1
1 element(s) affected
  • No skip navigation link found
How to fix

Add a 'Skip to main content' link as the first focusable element on the page.

Focus indicator not visible

Major

Interactive elements must have visible focus indicators for keyboard users.

WCAG 2.4.7
1 element(s) affected
  • <div style="...outline:none...">
How to fix

Ensure :focus styles are visible. Don't use outline: none without a replacement.

Top Priority Fixes

Here are the most impactful changes nginx.com should make to improve accessibility:

  1. #1
    Links missing accessible name Critical

    Add text content, aria-label, or aria-labelledby to links. Avoid empty <a> tags.

  2. #2
    Buttons missing accessible name Critical

    Add text content, aria-label, or title to all <button> elements.

  3. #3
    Form inputs missing labels Critical

    Add <label> elements with matching for attributes, or use aria-label.

Frequently Asked Questions

Is nginx.com accessible?

nginx.com scored 23/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is nginx.com WCAG compliant?

Our scan found 7 accessibility issues on nginx.com. Full WCAG compliance requires addressing all critical and major issues identified above.

Is nginx.com EAA compliant?

The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see nginx.com's compliance status.

What accessibility issues does nginx.com have?

See the full issue list above with severity levels, affected elements, and recommended fixes for nginx.com.

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing