If you ever do decide to update this plugin. Please be sure to fix this:
“PHP Warning: The magic method Wa11y::__wakeup() must have public visibility”
Line 114 in wa11y.php:
public function __wakeup() {}
Hello,
Will you tell me Is wA11y – The Web Accessibility Toolbox GDPR Compliant?
Also, is wA11y – The Web Accessibility Toolbox compatible with Avada Theme?
]]>I don’t understand how I can use the plugin.
]]>I get an error using: ” wA11y – The Web Accessibility Toolbox to correct issues on page, but when I search the code I am unable to locate what is causing this error.
Link Text is Unclear
The text “” is unclear without context and may be confusing to screen readers. Consider rearranging the tags or including special screen reader text.
Relevant code:
I don’t see anything on how these tools work or any documentation?
I am using a couple of plugins for accessibility and using the Divi theme on a localhost server. Could that be it? Just not sure how to even test a site.
Thanks!
Hello,
I really appreciate this plugin, but I noticed this issue in the logs :
PHP Warning: in_array() expects parameter 2 to be array, boolean given in XXX/wp-content/plugins/wa11y/wa11y.php on line 447
I’m aware that support for the Wa11y tool is handled on GitHub but this issue is specific to the WordPress plugin, so I’m not sure if I should post it here or on GitHub.
Thanks
]]>This is a very useful tool. Thank you. (Some users might let it become their master, but that would be their mistake, not yours.)
I have noticed two issues. The first is that, using tota11y, it really can’t cope with forms. It sees the background for form fields as the font color, and doesn’t appear to see the true font color at all. Perhaps that’s a problem with tota11y rather than with wA11y, so I’m not sure whether you can do much about it.
The second issue is with your rather clever, if still experimental, wand. I notice that, currently, the wand recognizes hover events, although these are mouse events that, so far as I am aware, would not be seen by a screen reader. On the other hand, the wand does not recognize focus events, when these would be detected by a screen reader.
Thanks again!
]]>