Skip to content

A11y: give the dashboard guarantee icon a real accessible name - #3372

Merged
Crabcyborg merged 1 commit into
masterfrom
fix/issue-6700-guarantee-icon-alt
Sep 18, 2026
Merged

Crabcyborg merged 1 commit into
masterfrom
fix/issue-6700-guarantee-icon-alt

Conversation

@vivi-the-going-merry

Copy link
Copy Markdown
Contributor

Closes Strategy11/formidable-pro#6700

What was broken

img_alt_valid (IBM Equal Access): the guarantee badge icon shown on the
dashboard's Pro-features promo panel (frm-testimonial__guarantee-icon)
had alt="" with no adjacent text describing it, so it was invisible to
screen readers despite conveying real information (the money-back
guarantee).

The same icon is reused in the "no views" upsell panel, right next to a
visible "100% No-Risk, Money Back Guarantee!" heading — there alt="" is
correct since the text already covers it, and that call site is
unchanged.

What changed

FrmAddonsHelper::guarantee_icon() now takes an optional $alt param
(default '', preserving the existing decorative behavior). The dashboard
call site passes a real accessible name; the other call site is untouched.

Markup-only — no CSS/visual change, no JS.

How it was verified

Live before/after check against a disposable formidable-preview-env
instance: fetched /wp-admin/admin.php?page=formidable-dashboard
authenticated — alt="" before, alt="100% No-Risk, Money Back Guarantee"
after, page byte count otherwise unchanged (no structural side effects).
CI can't confirm either way — cy.checkIbmAccessibility is currently
non-blocking (assertCompliance(false)).

img_alt_valid (IBM Equal Access): the guarantee badge on the dashboard's
Pro-features promo panel had alt="" with no adjacent text conveying its
meaning, so it was invisible to screen readers. The same icon is also used
in the "no views" upsell alongside a visible heading that already states
the guarantee, where alt="" is correct and stays unchanged.

guarantee_icon() now takes an optional $alt, passed only at the dashboard
call site.
@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 02a4c2df-d112-4225-8d8d-377bce7a0ec2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@deepsource-io

deepsource-io Bot commented Sep 18, 2026

Copy link
Copy Markdown

DeepSource Code Review

We reviewed changes in e404085...5f2f1ee on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
PHP Sep 18, 2026 12:05a.m. Review ↗
JavaScript Sep 18, 2026 12:05a.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@Crabcyborg Crabcyborg left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

🚀

@Crabcyborg
Crabcyborg merged commit a926b97 into master Sep 18, 2026
42 checks passed
@Crabcyborg
Crabcyborg deleted the fix/issue-6700-guarantee-icon-alt branch September 18, 2026 12:23
@Crabcyborg Crabcyborg added this to the 6.36 milestone Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant