ARIA IDs are not unique

thank you Toufiq

Hi Paul,

I am using raw Helix Ultimate and yes, the search field is also enabled in the Offcanvas-Menu.

Regards - Marco

yes, of course the tool reads the HTML code - just like screen readers do, which extract ARIA attributes or semantic HTML tags from the HTML code

Of course Joomla loads the search module twice because of my settings Paul - since this possibility exists and it makes sense to make the search available on the desktop and in the mobile view - don't you think?
Maybe I'll have a look at how other websites that make the search available in both views have solved the problem.
It's not urgent at all - I ran the test and came across the problem.
The test also says that my site is 90% accessible - I wanted to let you know anyway - if you want to fix it, that's fine, if not, then not ;)
Some things cannot be assessed by the test itself, manual work is required here.

Regards - Marco

that would still have to be checked

• The page has a logical tab order
• Interactive controls are keyboard focusable
• Interactive elements indicate their purpose and state
• The user's focus is directed to new content added to the page
• User focus is not accidentally trapped in a region
• Custom controls have associated labels
• Custom controls have ARIA roles
• Visual order on the page follows DOM order
• Offscreen content is hidden from assistive technology
• HTML5 landmark elements are used to improve navigation

these tests were successful

• [aria-] attributes correspond to their roles
• [aria-hidden="true"] does not exist in the document <body>
• [aria-hidden="true"]-elements do not contain focusable sub-elements
• [role]-elements have all required [aria-*] attributes
• The elements with an ARIA [role], whose subordinate elements must contain a specific [role], have all required subordinate elements.
• [role] elements are subordinate to their respective required parent elements
• [role] values are valid
• [aria-*] attributes have valid values
• [aria-*] attributes are valid and spelled correctly
• The names of the buttons are accessible to screen readers
• The page contains a heading, a skip link or a landmark area
• Document contains a <title> element
• ARIA IDs are unique
• Heading elements are displayed in consecutive descending order
• <html> element has a [lang] attribute
• The <html> element has a valid value for its [lang] attribute
• Image elements have [alt] attributes
• Form elements are linked to labels
• Links have an easily recognizable name
• Lists only contain <li> elements and elements for script support (<script> and <template>).
• List elements (<li>) are located in parent <ul> or <ol> elements
• [user-scalable="no"] is not used in the <meta name="viewport"> element and the
• [maximum-scale] attribute is not smaller than 5.
• Cells in a "<table>" element that contain the "[headers]" attribute refer to cells in the same table.