Kilotest: Diagnoses of button name not visible violation by HTML element 278 on Portland City Club page

Basics

About the page

• URL: https://www.pdxcityclub.org/
• Tested 0 days ago on 2026-10-10 at 05:30 by job 261010T0528-evq
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 718
  • Violators: 203
  • Issues: 53
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help explaining a button
• Priority: lowest
• Related WCAG standard: 4.1.2
• Reported by 1 rule engine (ASLint)
• Violations: 4
• Violators: 4

About the violator

• Tag name: DIV
• Text: 2026 Elections Reflections | Friday, November 13 at 12PM … Oregon's Energy Future | Friday, December 11 at 12PM
• Start tag: <div class="sow-carousel-navigation sow-carousel-navigation-next ">
• XPath: [not obtained]
• Bounding box: x = 1826, y = 559, width = 34, height = 32
• Reported by ASLint

Diagnoses

Here is how rule engines diagnose the button name not visible issue for HTML element 278 of the Portland City Club page.

1. The button should have a description, but the content is empty. Having only defined an attribute aria-label="Next Posts" 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.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: empty_button_description