Forum Replies Created
-
AuthorPosts
-
July 19, 2020 at 12:11 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1231491
@ismael That did it, thank you for sticking with me through all that!!!
July 14, 2020 at 10:12 pm in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1230448I meant @ismael :)
July 14, 2020 at 6:55 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1230175Thanks @ishmael
July 10, 2020 at 7:41 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1229335Oops, pinged the wrong username. :) @Ismael
July 7, 2020 at 1:24 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1228454@ishmail Thanks. No, I got rid of that already. I’m just using the regular Enfold menu.
July 3, 2020 at 3:29 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1227611@ishmael It seems to ignore any changes I make to the JS file. Just for testing I’ve added
console.log('blah')
to thecurrentLink.on('mouseenter',
function. Even deleting the JS file from the main and child theme has no effect. Is it possible I have some setting telling it to use a different menu? Thanks.June 30, 2020 at 12:29 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1226624Hmm. I can get the CSS working, though mine is a little different than yours.
#top .av-main-nav a:focus { text-decoration: underline!important; }
As for the focus, still no luck for me. Does this look right? It doesn’t seem to have an effect on the menu’s behavior.
@mitchell Here’s how I did it:
1. Follow the docs to create a child theme: https://kriesi.at/documentation/enfold/child-theme/.
2. Copy the file fromenfold/js/avia-snippet-megamenu.js
toenfold-child/avia-snippet-megamenu.js
. After you do this, you should be able to see theavia-snippet-megamenu.js
underAppearance/Theme Editor
in the right sidebar.
3. From there, make the changes that Ishmael listed above.- This reply was modified 4 years, 4 months ago by dfpg.
June 29, 2020 at 2:10 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1226270Thanks @Ismael. I appreciate you looking into this. Unfortunately, this doesn’t help people using screen readers. The visibility is
hidden
, which means it’s hidden from screen readers too. That means that blind people are unable to navigate any Enford site. That’s _exactly_ what makes _al_l of us open to lawsuits.It’s 2020. Maybe 7 years ago when this theme was created accessibility was an optional feature. It’s not anymore. This theme has been in the top sellers list for years, meaning it’s made millions and millions from us, your customers. With that kind of money, you can afford to keep your theme up to date with the most basic of legal requirements.
June 25, 2020 at 2:48 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1225392Well, I bought and implemented the Ubermenu and it’s totally broken. That’s a half day wasted. I’m really starting to get frustrated with this theme. Navigating a website with the keyboard may have been a “feature” several years ago, but it’s a necessity for a modern website. How is a theme this popular so behind on accessibility? Accessibility is the law in my country and this theme doesn’t meet even the most basic of standards. :(
I just recently asked the same thing here: https://kriesi.at/support/topic/accessibility-issues-with-main-nav-leaves-us-sites-in-danger-of-lawsuits/. I’m a little disappointed with the answer, given that in the US we can get sued for having non-accessible sites. :(
June 24, 2020 at 11:45 pm in reply to: Accessibility – Add label or aria-label to search widget #1225376Works like a charm, thanks!
June 24, 2020 at 2:44 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1224984My jQuery isn’t great, but it seems like you could edit the avia-snippet-megamenu.js to respond to focus, as well as hover events. Is that right?
//bind event for mega menu megaItems.each(function(i){ $(this).hover( function() { delayCheck[i] = true; setTimeout(function(){megaDivShow(i); },options.delay); }, function() { delayCheck[i] = false; setTimeout(function(){megaDivHide(i); },options.delay); } ); }); // bind events for dropdown menu dropdownItems.find('li').addBack().each(function() { var currentItem = $(this), sublist = currentItem.find('ul:first'), showList = false; if(sublist.length) { sublist.css({display:'block', opacity:0, visibility:'hidden'}); var currentLink = currentItem.find('>a'); currentLink.on('mouseenter', function() { sublist.stop().css({visibility:'visible'}).animate({opacity:1}); }); currentItem.on('mouseleave', function() { sublist.stop().animate({opacity:0}, function() { sublist.css({visibility:'hidden'}); }); }); } });
June 22, 2020 at 4:38 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1224465Thanks @ismael! So there’s no way to make it navigable with the keyboard? Is there a way to use a different menu, not the one built into the theme?
June 11, 2020 at 2:44 am in reply to: Remove link from featured post image (not just a css fix) #1221483@rikard @guenni007 Thanks so much! Yeah, that looks like it’ll work. I’ll post a link once it’s done.
June 11, 2020 at 2:43 am in reply to: Accessibility issues with main nav leaves US sites in danger of lawsuits :( #1221482Thanks @Rikard! The guidelines are unfortunately a little vague, but you need to be able to navigate navigation menus without a mouse. Otherwise there’s no way for many people with disabilities to reach your content.
-
AuthorPosts