Kilotest: Diagnoses of visible label not in name violation by HTML element 1030 on Giving Green page

Basics

About the page

• URL: https://www.givinggreen.earth/
• Tested 3 days ago on 2026-10-07 at 21:35 by job 261007T2113-wny
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 1708
  • Violators: 531
  • Issues: 63
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help choosing a form control to operate
• Priority: high
• Related WCAG standard: 2.5.3
• Reported by 5 rule engines (Accessibility Checker + Alfa + Axe + QualWeb + SureA11y)
• Violations: 82
• Violators: 42

About the violator

• Tag name: A
• Text: 2025 Annual Impact Report: Defending Hard-Won Progress, Unlocking New Opportunities
• Start tag: <a aria-label="Read this article" href="/post/2025-annual-impact-report-defending-hard-won-progress-unlocking-new-opportunities" class="news_link w-inline-block">
• XPath: [not obtained]
• Bounding box: x = 3868, y = 8076, width = 366, height = 42
• Reported by Accessibility Checker + Axe + SureA11y

Diagnoses

Here is how rule engines diagnose the visible label not in name issue for HTML element 1030 of the Giving Green page.

1. Elements must have their visible text as part of their accessible name; Text inside the element is not included in the accessible name

   Rule engine: Axe (Deque)

   Rule: label-content-name-mismatch

2. Accessible name does not match or contain the visible label text

   Rule engine: Accessibility Checker (IBM)

   Rule: label_name_visible

3. a: visible label "2025 Annual Impact Report: Defending Hard-Won Progress, Unlocking New Opportu..." (from self) is not included in the accessible name (from aria-label).

   Rule engine: SureA11y (Jorge Rumoroso)

   Rule: label-in-name