Hi,
Unfortunately, there is no such option for now.
You have to write the custom code to achieve that setting.
Hi @abhikr781,
I’m not familiar with coding js. Can you possibly provide a sample script I can use to trigger on-click navigation menu instead of hover? Thanks.
HI,
I apologize, but unfortunately, it falls under Personal Customization, and as such is out of our scope: https://docs.oceanwp.org/article/685-support-policy
Usually, when it comes only to a few lines of code, we are more than eager to help everyone achieve the desired look. However, this is really more than that, and I would kindly advise you to consult a professional on this matter.
Hope this helps and best of luck with your website
The problem with your attitude is that your theme is not Accessibility Compliant which will lead to reduced sales. Accessibility Compliance is now required in the US and allowing developers to choose click for menu item behavior is one of listed requirements.
@alfie424: I recommend Max Megamenu plugin which offers this option and the developer is very responsive to questions. https://www.megamenu.com/
Hello @lightwing,
We understand your concern and appreciate the suggestion. OceanWP navigation is accessibility friendly and meets requirements: https://www.w3.org/TR/wai-aria-practices-1.1/examples/menubar/menubar-1/menubar-1.html
We are also working on other things not measured by these sorts of websites and plugins. However, accessibility readiness does not depend on the theme alone, but on all plugins you’re using, the design, content, and everything else you have on the website.
The default WordPress Twenty Twenty theme is more than Accessibility Ready and has the nav menu functioning in the same way (just one of the examples).
What you have is a misunderstanding of Pointer Cancellation guidelines and recommendations on the use of JS events – onmousedown and onclick, which in this case, is not related to the navigation menu: https://usability.yale.edu/web-accessibility/articles/wcag2-checklist/developers
Of course, if you’re just looking for the sub-menu items to open on click, that’s one thing, and for now does fall under personal requests which are out of our scope.
Hope this clarifies the situation out. Wishing you a wonderful weekend
Thanks. There are many Accessibility resources out there and as a busy independent developer I don’t have time to sift through the whole spec. So, I rely on other people’s synopses and one of them outlined that developers shouldn’t use mouseover for nav menu dropdowns—that onClick was the only acceptable method. A deeper reading of 1.4.13 Content on Hover or Focus revealed that my resource did indeed misinterpret the intent of this success criterion.
Thanks for the heads up. There is always more to learn in web tech. If you are not learning something new every single day, you are falling behind!
