WCAG 4.1.2: Ensure buttons have discernible text

[mgifford]

Title: WCAG 4.1.2: Ensure buttons have discernible text (._button_18q4p_1._small_18q4p_36[data-accent="secondary"])
Tags: Accessibility, WCAG 4.1.2, button-name

Issue: Ensure buttons have discernible text (button-name - https://accessibilityinsights.io/info-examples/web/button-name)

Target application: All Companies - Companies - https://crm.civicactions.com/objects/companies?viewId=242124e5-2d4e-4fb4-bf1a-8f50d473879d

Element path: .s1b7q4oc > ._button_18q4p_1._small_18q4p_36[data-accent="secondary"]

Snippet:

How to fix:
Fix any of the following:
Element does not have inner text that is visible to screen readers
aria-label attribute does not exist or is empty
aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
Element has no title attribute
Element does not have an implicit (wrapped)
Element does not have an explicit
Element's default semantics were not overridden with role="none" or role="presentation"

Environment: Chrome version 150.0.0.0

====

This accessibility issue was found using Accessibility Insights for Web 2.47.0 (axe-core 4.11.3), a tool that helps find and fix accessibility issues. Get more information & download this tool at http://aka.ms/AccessibilityInsights.

[krish-mittal1]

I'd like to work on this. The group toggle button in RecordTableRecordGroupSection.tsx is missing an aria-label. Could this be assigned to me?

[djadji-gueye]

Hi, I'd like to work on this issue — starting now!