salesforce.com Accessibility Report

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

Technology
0 /100
D Poor

5 issues found across 2 categories

3 Critical 2 Major

WCAG Compliance Overview

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

Issues Found

Images missing alt text

Critical

Images must have alternative text to convey their meaning to screen reader users.

WCAG 1.1.1
1 element(s) affected
  • <img src="https://wp.sfdcdigital.com/en-us/wp-content/uploads/sites/4/2025/10/chp-orbital-">
How to fix

Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Links missing accessible name

Critical

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

WCAG 2.4.4
36 element(s) affected
  • <a href="https://www.salesforce.com/fr/crm/">
  • <a href="https://www.salesforce.com/fr/pricing/">
  • <a href="https://help.salesforce.com/">
  • <a href="https://www.salesforce.com/fr/products/">
  • <a href="https://www.salesforce.com/fr/products/">
How to fix

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

Buttons missing accessible name

Critical

Buttons must have discernible text for screen reader users.

WCAG 4.1.2
46 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
10 element(s) affected
  • <h6> "Découvrez le CRM n°1 intégrant l'IA" (after h2)
  • <h6> "Explorer Salesforce pour les secteurs d'activité" (after h2)
  • <h6> "Explorer les témoignages" (after h2)
  • <h6> "Événements Salesforce" (after h2)
  • <h6> "Devenez un Trailblazer" (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
5 element(s) affected
  • id="video-carousel-modal"
How to fix

Make each id attribute value unique within the page.

Top Priority Fixes

Here are the most impactful changes salesforce.com 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
    Links missing accessible name Critical

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

  3. #3
    Images missing alt text Critical

    Add descriptive alt attributes to all <img> elements. Use alt="" for decorative images.

Frequently Asked Questions

Is salesforce.com accessible?

salesforce.com scored 39/100 (grade D) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.

Is salesforce.com WCAG compliant?

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

Is salesforce.com EAA compliant?

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

What accessibility issues does salesforce.com have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing