cursor.sh Accessibility Report

Accessibility audit of cursor.sh — scanned on Feb 20, 2026

Technology
0 /100
D Poor

6 issues found across 2 categories

2 Critical 4 Major

WCAG Compliance Overview

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

Issues Found

Form inputs missing labels

Critical

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

WCAG 1.3.1
4 element(s) affected
  • <textarea name="message">
  • <textarea name="message">
  • <textarea name="message">
  • <textarea name="message">
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
8 element(s) affected
  • <button>
  • <button>
  • <button>
  • <button>
  • <button>
How to fix

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

Frames missing title

Major

Iframes must have title attributes describing their content.

WCAG 2.4.1
1 element(s) affected
  • <iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M2R7938W">
How to fix

Add descriptive title attributes to all <iframe> elements.

Duplicate element IDs

Major

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

WCAG 4.1.1
17 element(s) affected
  • id="demo-window-cursor-ide"
  • id="site-header"
  • id="main"
  • id="tabpanel-browser-preview"
  • id="logo-garden"
How to fix

Make each id attribute value unique within the page.

Invalid ARIA attributes

Major

ARIA attributes must be valid and used correctly to work with assistive technologies.

WCAG 4.1.2
2 element(s) affected
  • <div aria-labelledby="tab-browser-preview"> (missing ref)
How to fix

Review and correct ARIA roles, states, and properties according to the WAI-ARIA specification.

Focus indicator not visible

Major

Interactive elements must have visible focus indicators for keyboard users.

WCAG 2.4.7
12 element(s) affected
  • <button style="...outline:none...">
  • <button style="...outline:none...">
  • <button style="...outline:none...">
  • <button style="...outline:none...">
  • <button 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 cursor.sh should make to improve accessibility:

  1. #1
    Buttons missing accessible name Critical

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

  2. #2
    Form inputs missing labels Critical

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

  3. #3
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is cursor.sh accessible?

cursor.sh scored 38/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is cursor.sh WCAG compliant?

Our scan found 6 accessibility issues on cursor.sh. Full WCAG compliance requires addressing all critical and major issues identified above.

Is cursor.sh EAA compliant?

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

What accessibility issues does cursor.sh have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing