Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 222 on Russellville Park page

Basics

About the Russellville Park page

• URL: https://russellvillepark.com/
• Tested 11 days ago by job kyq on 2026-05-21 at 23:58

About HTML element 222

• Tag name: FOOTER
• Text: 503-974-0755 … Contact Us
• Start tag: <footer class="kb-row-layout-wrap kb-row-layout-id54_2566d9-29 alignnone kb-v-md-hidden kb-v-sm-hidden has-theme-palette1-background-color kt-row-has-bg wp-block-kadence-rowlayout">
• XPath: /html/body/div[1]/footer[1]
• Bounding box: x = 0, y = 2850, width = 1920, height = 290

About the landmarks not distinctly named issue

• Why it matters: User cannot get help on how some of the document is organized
• Priority: high
• Related WCAG standard: 1.3.6

Diagnoses

Here is how tools diagnose the landmarks not distinctly named issue for HTML element 222 of the Russellville Park page.

1. Landmarks should have a unique role or role/label/title (i.e. accessible name) combination; The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable

   Tool: Axe (Deque)

   Rule: landmark-unique