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

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

Basics

• About the button not named issue
  • Why it matters: User cannot get help explaining a button
  • Priority: highest
  • Related WCAG standard: 4.1.2
• About the Run! page
  • URL: https://www.designedtorun.com/
  • Tested on 2026-04-05 at 01:26
• About HTML element 983
  • 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=":R1al6tl6:">
  • XPath: /html/body/div[1]/div[1]/div[2]/div[1]/div[2]/form[1]/div[1]/div[1]/button[1]
  • Bounding box: x = 1820, y = 1104, width = 64, height = 50

Diagnoses

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