Kilotest: Diagnoses of link href missing violation by HTML element 365 on Repower get involved page

Basics

About the page

• URL: https://www.repower.world/get-involved
• Tested 3 days ago on 2026-10-07 at 22:22 by job 261007T2157-ijl
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 265
  • Violators: 131
  • Issues: 39
• Download the full technical report (JSON)

About the issue

• Why it matters: Helper cannot properly explain a link to a user
• Priority: low
• Related WCAG standard: 1.3.1
• Reported by 2 rule engines (ASLint + Testaro)
• Violations: 4
• Violators: 4

About the violator

• Tag name: P
• Text: If you would like more information on our project, please email us at: news@repower.world or get in touch using our hello@repower.world.
• Start tag: <p>
• XPath: /html/body/footer[1]/div[1]/div[1]/div[1]/div[2]/p[1]
• Bounding box: x = 260, y = 4422, width = 456, height = 41
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the link href missing issue for HTML element 365 of the Repower get involved page.

1. Missing attribute <code>href</code> on link. The user cannot navigate to this element using the keyboard. A better option here is to use a <code><a></code> element instead.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: missing_href_on_a