Kilotest: Diagnoses of button name not visible violation by HTML element 320 on Go Portland Go! Coalition page

Basics

About the Go Portland Go! Coalition page

• URL: https://www.goportlandgo.org/coalition
• Tested 5 days ago by job xr7 on 2026-08-26 at 20:15

About HTML element 320

• Tag name: DIV
• Text: “Taking care of people — whether it's our team and our guests — sometimes means making hard practical choices that will allow us to keep taking care of them. Portland needs leaders willing to do the same: make tough decisions that deliver real results, not just good optics. That is why we support Go Portland Go's vision to do that.” … Item 1 of 3
• Start tag: <div class="desktop-arrows arrow-container arrow-container--right" style=" right: 5vw; ">
• XPath: [not obtained]
• Bounding box: x = 1764, y = 1332, width = 60, height = 540

About the button name not visible issue

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

Diagnoses

Here is how rule engines diagnose the button name not visible issue for HTML element 320 of the Go Portland Go! Coalition page.

1. The button content has only whitespaces. Having only defined an attribute aria-label=" Next " is not sufficient and it is recommended to have the content instead, e.g. at least visually hidden, but exposed to assisitve technologies. Some users are disabling styles for better readability, and also description from attribute is not available for automatic translators.

   Tool: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description