force.com Accessibility Report

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

Technology
0 /100
D Poor

5 issues found across 2 categories

2 Critical 3 Major

WCAG Compliance Overview

Perceivable 1 issues
Operable 2 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
20 element(s) affected
  • <a href="https://www.salesforce.com/crm/">
  • <a href="https://www.salesforce.com/pricing/">
  • <a href="https://help.salesforce.com/">
  • <a href="https://www.salesforce.com/products/">
  • <a href="https://www.salesforce.com/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
65 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
11 element(s) affected
  • <h6> "Discover the #1 AI CRM" (after h2)
  • <h6> "Explore Salesforce for industries." (after h2)
  • <h6> "Explore success stories." (after h2)
  • <h6> "Salesforce Events" (after h2)
  • <h6> "Become a 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
18 element(s) affected
  • id="tile-card"
  • id="content"
  • id="bento"
  • id="mid-bento"
  • id="bottom-bento"
How to fix

Make each id attribute value unique within the page.

Generic link text

Major

Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.

WCAG 2.4.4
3 element(s) affected
  • <a href="https://www.salesforce.com/dreamforce/">learn more</a>
  • <a href="https://www.salesforce.com/connections/">learn more</a>
  • <a href="https://www.salesforce.com/events/">learn more</a>
How to fix

Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.

Top Priority Fixes

Here are the most impactful changes force.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
    Duplicate element IDs Major

    Make each id attribute value unique within the page.

Frequently Asked Questions

Is force.com accessible?

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

Is force.com WCAG compliant?

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

Is force.com EAA compliant?

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

What accessibility issues does force.com have?

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

Scan Your Own Website

Get a free accessibility report for your website in seconds.

Scan Your Website Free View Pricing