Kilotest: Diagnoses of control not named violation by HTML element 925 on Run! page

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

Basics

• About the control not named issue
  • Why it matters: User cannot get help on how to operate a form item
  • 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 925
  • Tag name: INPUT
  • Text: [not applicable]
  • Start tag: <input class="PrivateSwitchBase-input MuiSwitch-input css-1m9pwf3" type="checkbox">
  • XPath: [not obtained]
  • Bounding box: x = 603, y = 8431, width = 546, height = 60

Diagnoses

1. Form elements must have labels; Element does not have an implicit (wrapped) <label>; Element does not have an explicit <label>; 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 has no placeholder attribute; Element's default semantics were not overridden with role="none" or role="presentation"

   Tool: Axe (Deque)

   Rule: label

2. This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.

   Tool: HTML CodeSniffer (Squiz Labs)

   Rule: E-WCAG2AAA.Principle1.Guideline1_3.1_3_1.F68

3. Form control element <input> has no associated label

   Tool: Accessibility Checker (IBM)

   Rule: input_label_exists

4. [failed] The test target accessible name doesn't exist or it's empty ('').

   Tool: QualWeb (University of Lisbon)

   Rule: QW-ACT-R16