Kilotest: Diagnoses of button not named violation by HTML element 996 on Run! page

Basics

About the Run! page

• URL: https://www.designedtorun.com/
• Tested 28 days ago by job mgf on 2026-05-04 at 17:00

About HTML element 996

• Tag name: BUTTON
• Text: [not applicable]
• Start tag: <button class="MuiButtonBase-root MuiButton-root MuiLoadingButton-root MuiButton-contained MuiButton-containedSecondary MuiButton-sizeMedium MuiButton-containedSizeMedium no-rotate css-1ohzrnn-LoadingButton" tabindex="0" type="submit" id=":Rl8datl6:">
• XPath: /html/body/div[1]/div[1]/footer[1]/div[1]/div[1]/form[1]/div[1]/div[1]/button[1]
• Bounding box: x = 1151, y = 9714, width = 60, height = 50

About the button not named issue

• Why it matters: User cannot get help explaining a button
• Priority: highest
• Related WCAG standard: 4.1.2

Diagnoses

Here is how tools diagnose the button not named issue for HTML element 996 of the Run! page.

1. This button element does not have a name available to an accessibility API. Valid names are: title attribute, element content, aria-label attribute, aria-labelledby attribute.

   Tool: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle4.Guideline4_1.4_1_2.H91.Button.Name

2. [failed] The test target doesn't have an accessible name, or it's empty ('').

   Tool: QualWeb (University of Lisbon)

   Rule: QW-ACT-R11