Kilotest: Diagnoses of focusable element not active violation by HTML element 110 on PTR Global page

Basics

About the PTR Global page

• URL: https://www.ptrglobal.com/
• Tested 46 days ago by job sdo on 2026-06-05 at 04:36

About HTML element 110

• Tag name: SPAN
• Text: [not applicable]
• Start tag: <span class="ubermenu-target ubermenu-target-with-icon ubermenu-item-layout-default ubermenu-item-layout-icon_left ubermenu-noindicator ubermenu-item-notext" tabindex="0">
• XPath: /html/body/div[1]/div[1]/header[1]/div[2]/div[1]/div[2]/div[1]/nav[1]/ul[1]/li[1]/span[1]
• Bounding box: x = 1502, y = 73, width = 63, height = 51

About the focusable element not active issue

• Why it matters: Keyboard-only user cannot navigate properly to the operable items
• Priority: high
• Related WCAG standard: 4.1.2

Diagnoses

Here is how rule engines diagnose the focusable element not active issue for HTML element 110 of the PTR Global page.

1. Elements in the focus order should have an appropriate role; Element does not have a widget role.; Element has invalid semantics for an element in the focus order.

   Tool: Axe (Deque)

   Rule: focus-order-semantics