-
Posts
-
A WCAG 2.2 report was run on my site and found the following issues:
1- Landmarks are not properly inserted into the web page, and fail to provide access to the main and navigation regions of the web page. Landmarks should be built using their corresponding HTMLS element or include a description using an “aria-label” attribute and a “role” tag. Landmarks help assistive technology users orient themselves on the web page.
2- Interactive elements that behave as “buttons” are not programmatically written correctly. Instead of using a “role” attribute, they are built by tags such as <span>, <div>, or others. As a result, the assistive technology reads the incorrectly constructed element and the user is confused, because of receiving ambiguous information about the element in focus.
3- – The Navigation menu has elements with drop-down menu, and they do not announce their state – “collapsed” or “expanded”. As a result, assistive technology users do not know what part of the Navigation menu they navigate or if they skipped sub-menu links.
my client is getting sued and need to fix this issue, can you assist?
url – https://bowl360.nyc/
thanks in advance
- You must be logged in to reply to this topic.