Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 107 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 107

• Tag name: NAV
• Text: Contact … Home
• Start tag: <nav id="ubermenu-main-2-primary-2" class="ubermenu ubermenu-main ubermenu-menu-2 ubermenu-loc-primary ubermenu-responsive ubermenu-responsive-single-column ubermenu-responsive-single-column-subs ubermenu-responsive-default ubermenu-responsive-collapse ubermenu-horizontal ubermenu-transition-slide ubermenu-trigger-click ubermenu-skin-minimal ubermenu-bar-align-full ubermenu-items-align-left ubermenu-bound ubermenu-sub-indicators ubermenu-retractors-responsive ubermenu-submenu-indicator-closes ubermenu-notouch ubermenu-desktop-view">
• XPath: /html/body/div[1]/div[1]/header[1]/div[2]/div[1]/div[2]/div[1]/nav[1]
• Bounding box: x = 565, y = 73, width = 1000, height = 51

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 rule engines diagnose the landmarks not distinctly named issue for HTML element 107 of the PTR Global 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