I don’t know if this should go in an accessibility forum or here
Unfortunately, there isn’t an accessibility forum on wordpress.org… yet. Can you post a link to a page on your site that demonstrates the problem.
I should point out that I’m not the plugin’s developer but I am keen to promote accessible design amongst WP devs generally. So the more examples of inaccessible development I can gather, the better. Especially if we can develop an alternative, accessible, approach.
Have you seen http://make.wordpress.org/accessibility/ ? Your feedback generally would be very valuable.
Yeah, actually I was reading a big chunk of those posts, but I just might check into it more. I might have a few things to say. About plugins in particular actually.
Ok, a temp post:
http://jennykbrennan.com/?p=792
I can’t click either one of those. And there’s no navigation info on them. I’ve come across more and more of this kind of “invisible” coding and as an old time HTML coder, I find that a bit disconcerting.
🙂
Jen
Plugin Author
Vova
(@gn_themes)
Hi Jen.
Unfortunately, I can’t help you. Because I didn’t know nothing about screenreaders and their browsers. These shortcodes was tested on all major PC’s and Mac browsers, and also on android browser. And it works fine.
I can’t test the shortcodes there, but I think the problem in the screenreader software.
🙂
Thanks for giving it thought, I didn’t really expect a solution; I just want someone to be aware of it.
I can’t agree with you about it being a screenreader problem. It’s about being able to use a mouse and/or hotkeys. That kind of inaccessible button has cropped up in a lot of places and they are all equally inaccessible for most screenreaders. It’s a bit like the flash players. When they first started to appear everywhere, none of them were accessible because of the way the code works. It’s been implemented in adobe flash and nowadays, the question is only whether the developer uses those options or not.
Screenreader people like GW-Micro and Freedom Scientific work uphill to try to keep up and adapt to work with IE, Firefox, and all the rest, with the new things and this might be one of those things that they are looking in to, but since it’s an expensive piece of software, it’s not always possible to update to the latest version even if they do. It should be easier to adapt new flashy things in webpages with accessibility techniques already proven and available.
Maybe just my opinion, sometimes it feels that way.
But hey, I wasn’t going to discuss accessibility problems here, so I’ll drop in to that thread you mentioned.
Cheers, and thanks.
Jen
I’m happy to say that using the jaws cursor does work. Funny thing is that sometimes it does, sometimes it doesn’t. If that is a browser glitch, a jaws glitch, temporary or something else entirely I couldn’t say.
But at least I know I can make it work, and I can tell my visitors how, and that’s the important thing in this particular case.
One problem down, on to the next. LOL
Cheers.
Jen
Just had a look at http://jennykbrennan.com/?p=792. The primary cause as far as I can tell is that the plugin’s implementation of javascript to create a clickable div as opposed to a real link. I don’t think it’s hooking onto the DOM correctly, so isn’t available to jaws. For anyone who is interested, there’s an excellent article on this subject on accessites.org.
Glad to hear I’m not dillusional, thank you.
I’ll check that, even if the java thing still goes over my head. 😀
I found plenty interesting to read there, but wasn’t able to find anything in specific about this topic. maybe I just don’t know what to search for. 🙂
It’s really for theme/plugin developers. 🙂
True, interesting nonetheless. Something I’d love to do if I thought I could.
