teisha21
Forum Replies Created
-
Thank you for the suggestion @joelsmashballoon!
I started to look into this today but I believe the file that I need to update isclass-sb-instagram-display-elements.php
which is located under theinc
file of your plugin directory. Do you know if there is any way I am able to edit that file just on my site? Else I’ll tell my client we will need to wait for your updates.I would suggest removing the aria-hidden attribute on the
<svg>
s in the get_basic_icons() function and adding focusable=”false” attribute to them. That should solved the accessibility issues I was running into.Forum: Plugins
In reply to: [Max Mega Menu] WCAG 2.0This is what I did to fix the issue I was having.
#mega-menu-wrap-primary .mega-menu-toggle.mega-menu-open + #mega-menu-primary { display: block; } #mega-menu-wrap-primary .mega-menu-toggle + #mega-menu-primary { display: none; }
- This reply was modified 4 years, 1 month ago by teisha21.
Forum: Plugins
In reply to: [Max Mega Menu] WCAG 2.0The hamburger menu does open if I tab and press enter but I want to get to a search button I have after the hamburger. How it’s setup right now, I have to tab through ALL of the top-level menu items even if the hamburger menu isn’t open.
It looks like the tabbing is working as expected on your demo but curious how you have that setup to work correctly?
Forum: Plugins
In reply to: [Max Mega Menu] WCAG 2.0Hi Tom,
Found the “Disable Link” and that fixed the desktop tabbing but still have an issue with the mobile. We don’t have the toggle disabled and we are using the Animated Menu Toggle Settings. Looks like I cannot share a screenshot on this forum but if email would be a better option please let me know.
Thank you,
Teisha- This reply was modified 4 years, 1 month ago by teisha21.
Forum: Plugins
In reply to: [Ultimate FAQ Accordion Plugin] Accessibility update for Ultimate FAQHere’s one of the pages we setup that uses an accessible expand/collapse: https://u-fi.com/faqs/
Here is another simple example as well: https://pauljadam.com/demos/aria-expanded.htmlAlso some more info from WC3 website: https://www.w3.org/WAI/GL/wiki/Using_the_WAI-ARIA_aria-expanded_state_to_mark_expandable_and_collapsible_regions
The main thing is that these buttons/links should be announced to screen readers when they have been expanded or collapsed.
Additionally the user should have the ability to do this with a mouse or a keyboard (I typically use “Enter” key). I believe this plugin did do this but just wanted to note that as well.