Kilotest: Diagnoses of element focusability and operability conflict violation by HTML element 366 on Pacific Northwest Software Quality Conference page

Basics

About the Pacific Northwest Software Quality Conference page

• URL: https://pnsqc.org/
• Tested 28 days ago by job owx on 2026-05-04 at 16:59

About HTML element 366

• Tag name: DIV
• Text: AI-Augmented Manual Testing with PLUS QA … "Testing the Future: From Testing Code to Testing Intelligence" with Premi Vinayagam fro...
• Start tag: <div class="recent-events-track flex gap-0 overflow-x-auto scroll-smooth snap-x snap-mandatory" id="recent-events-track" role="region" tabindex="0" aria-labelledby="recent-events-heading" data-carousel-track="" data-recent-events-state="ready">
• XPath: /html/body/main[1]/section[4]/div[1]/div[1]/div[2]/div[2]
• Bounding box: x = 992, y = 2420, width = 704, height = 437

Take me there

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 366 of the Pacific Northwest Software Quality Conference page.

1. Element is Tab-focusable but not operable

   Tool: Testaro (CVS Health)

   Rule: focAndOp