Kilotest: Diagnoses of element focusability and operability conflict violation by HTML element 500 on Sage Mages page

Basics

About the Sage Mages page

• URL: https://www.thesagemages.com/
• Tested 13 days ago by job 0lq on 2026-07-07 at 17:44

About HTML element 500

• Tag name: DIV
• Text: Tech Atypically … Audience of neurodiverse tech professionals gets an ecosystem of accommodating brand design.
• Start tag: <div class="gallery-item-container item-container-regular has-custom-focus visible clickable shrink-on-hover" id="pgi201ebdda952443ddb371228f55e9dab6_0" data-hash="201ebdda-9524-43dd-b371-228f55e9dab6" data-id="201ebdda-9524-43dd-b371-228f55e9dab6" data-idx="0" data-hook="item-container" style="overflow-y:hidden;position:absolute;bottom:auto;margin:0;top:0;left:0;right:auto;width:715px;height:786.6px;transition:opacity .2s ease;opacity:0;display:none" aria-hidden="false">
• XPath: [not obtained]
• Bounding box: x = 194, y = 4989, width = 739, height = 808

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 rule engines diagnose the element focusability and operability conflict issue for HTML element 500 of the Sage Mages page.

1. Element is operable (pointer cursor) but not Tab-focusable

   Tool: Testaro (CVS Health)

   Rule: focAndOp