Hello guys.
I have a suggestion in respect to the blo… eu act - and your “nemesis” elementor. The folks from elementor give actually a pretty chunk of attention to this issue. So, if you want to have an edge or more likely close the gap, I’d suggest you clarify some points in cornerstone like
-
the distinction between a link and a button by default. I mean the tags <“a”> and <“button”>. Yes, you can set it manually, but this should be a default thing. at the moment, if you insert a “button” it’s a by default. For “unaware” people you might add a new element like “link button” and “script button”. link button = <“a”>, script button = <“button”>. An example for a script button would be e.g. looper navigation. these are links right now. empty links triggering scripts.
-
I know, this does not address cornerstone in first place but there is a pretty big issue with ubermenu and empty links (all those indicators which have all “#” as address). If you include this plugin into the cornerstone package, your position to address this thing to the ubermenu team is a bit more powerful than the the average joe’s.
-
navigating with the tab. Well right now, using the tab jumps from link to link. not from element to element. Ok, you may say, we leave this to the third party developers or promote your “one” services, if the other party does it for free, well then… and if the other party does not, I’d see this as an opportunity.
-
Social media links and embedding youtube content - oh boy. wave (https://wave.webaim.org/) screams like a haunted piglet, when it stumbles upon.
pls make this code mentioned in this thread: Web Accessibilty Issue - Link of social media icons contains no text
default.
Just some thoughts… Don’t get me wrong, I’m aware of the effort.