Kilotest: Diagnoses of element focusability and operability conflict
violation by HTML element 102 on Parking Reform Network page
Basics
About the Parking Reform Network page
- URL: https://parkingreform.org/
- Tested 24 days ago by job
u5son 2026-05-08 at 20:27
About HTML element 102
- Tag name:
BODY - Text: [not applicable]
- Start tag:
<body data-cmplz="1" itemtype="https://schema.org/WebPage" itemscope="itemscope" class="home wp-singular page-template-default page page-id-496 wp-custom-logo wp-theme-astra wp-child-theme-astra-child theme-astra woocommerce-js ast-desktop ast-plain-container ast-no-sidebar astra-4.10.1 group-blog ast-single-post ast-inherit-site-logo-transparent ast-hfb-header ast-full-width-primary-header ast-fluid-width-layout ast-sticky-header-shrink ast-inherit-site-logo-sticky astra-addon-4.13.1 cmplz-marketing cmplz-statistics cmplz-preferences cmplz-functional cmplz-us cmplz-optout" style="overflow: hidden auto;"> - XPath:
/html/body - Bounding box: x = 0, y = 0, width = 1920, height = 4651
About the element focusability and operability conflict
issue
- Why it matters: Keyboard-only user cannot operate an item
- Priority: high
- Related WCAG standard: 2.1.1
Diagnoses
Here is how tools diagnose the element focusability and operability conflict
issue for HTML element 102 of the Parking Reform Network page.
- Element is operable (click listener) but not Tab-focusable
Tool: Testaro (CVS Health)
Rule:
focAndOp