michaelb4g

This free plugin is intended to help you make your website more accessible.
It is responsive and works on desktop computers & mobile devices
You can dock the accessibility panel to any of the 4 sides in desktops and to 2 sides in mobile devices
The accessibility panel opens from an toggle icon that can be set to any of the 4 corners from the admin option panel
All the icons have a keyboard shortcut so you can control the accessibility from the keyboard even with the accessibility panel hidden 
If you know any other language beside English and want to help translating the icons names to other languages please leave me a message with your email
LEGAL DISCLAIMER: 
This plugin does not guarantee that your website will comply with any regulations. 
You can download it and install it at your own risk. 
All information has been obtained from sources, which are believed to be reliable, but accuracy and thoroughness cannot be guaranteed. Readers are solely responsible for how they use this plugin and for their results.
<h3>WordPress Admin Options</h3>
WordPress Admin Options (under WordPress Control Panel->Plugins->cool-accessibility): 
Cool Accessibilty Declaration & Icon Screen position Settings 
1. Accessibilty Declaration Page Slug (URL ) 
default page slug: site_url/website-accessibility-declaration 
(Accessibilty Declaration example at the end of this file) 
if you have multiple languages and you are using the Polylang plugin, cool-accessibility plugin will pick the parallel page in the current language
<ol>
<li>
Accessability Icon position: 
Bottom-right (default) 
Bottom-left 
Top-right 
Top-left
</li>
<li>
Skip menu settings
</li>
<li>
Highlight link color override
</li>
<li>
Highlight title background color override
</li>
</ol>
<h3>Advance settings for website developers</h3>
FONT SIZE:
<h3></h3>
changing the font size intenially doesn’t affect the tag
HIGHLIGHT_LINKS:
<h3></h3>
toggles the class ‘coolaxs_highlight_links’ in all the header tags ( “:focusable,a” )
HIGHLIGHT_TITLES:
<h3></h3>
toggles the class “coolaxs_highlight_titles_colors” in all the header tags (‘h1,h2,h3,h4,h5,h6’)
READABLE_FONT:
<h3></h3>
toggles the class “coolaxs_readable_font”
Keyboard Navigation (Tab / shift Tab icon)
<h3></h3>
if you want to change things in css – this icon adds the folowing class: 
 coolaxs_focus_css_activated
Keyboard Navigation Skip Menu:
<h3></h3>
the “skip to page content” message with fixed position is added to the top of the page 
with a css z-index:99 (because the zoom-text magnify glass of the cool-accessibility plug-in should be on top of that) 
 if there is a
<
nav> tag in the page
so this means that if there is a fixed header on the top of the page its z-index should be less than 99
PREVENT ANIMATION:
<h3></h3>
1. 
 // the following suffix should be at every animated gif or static so javascript could toggle between them automatically 
 var str_normal_image = “_static.gif”; 
 var str_animated_gif_image = “_animated.gif”;
2.
the plug in also toggles between these 2 embeded video autoplay modes 
so the video will not autoplay upon page load
embeded video
<
iframe src=”…?autoplay=1″> 
embeded video
<
iframe src=”…?autoplay=0″>
3. 
if there is an automatic loop flexslider it stops it:
BRIGHT / DARK CONTRAST
<h3></h3>
1. 
the plug in adds the following classes so you can further modify your css file: 
coolaxs_bright_contrast 
coolaxs_dark_contrast
2. 
there is also an automatic image / background image flipping mode if you prefer by the suffix of the image name
2a. 
if you have 3 images – 1 for normal contrast 2. for dark contrast 3. for bright contrast
add to your normal contrast image / background image the following suffix: “_normal_to_both” 
so your image name becomes: 
 imagename_normal_to_both.jpg 
 (or imagename_normal_to_both.png or imagename_normal_to_both.gif)
and provide in the same directory 2 more images (assuming a jpg image type) 
imagename_bright_contrast.jpg 
imagename_dark_contrast.jpg
2b. 
if you have only 2 images – 1 for normal contrast 2. for dark contrast 
and for bright contrast you use the normal contrast image 
then modify your original image / background image to this: 
imagename_normal_to_dark.jpg 
 (or imagename_normal_to_dark.png or imagename_normal_to_dark.gif)
and provide in the same directory 1 more image (assuming a jpg image type) 
imagename_dark_contrast.jpg
2c. 
if you have only 2 images – 1 for normal contrast 2. for bright contrast 
and for dark contrast you use the normal contrast image 
then modify your original image / background image to this: 
imagename_normal_to_bright.jpg 
 (or imagename_normal_to_bright.png or imagename_normal_to_bright.gif)
and provide in the same directory 1 more image (assuming a jpg image type) 
imagename_bright_contrast.jpg
List of all added JavaScript classes
<h3></h3>
This is the list of all the classes that the Javascript file adds/toggles so you can modify your CSS file if you want to custom your site to this plugin: 
 $html.addClass(‘coolaxs_mobile’); 
 $html.addClass(‘coolaxs_mobile_landscape’); 
$(‘#coolaxs_letter_spacing_group’).addClass(‘coolaxs_acivated_button’);// to all the cool accessibility plugin buttons
<pre><code> $( ":focusable,a" ).addClass('coolaxs_highlight_links');
 $( 'h1,h2,h3,h4,h5,h6' ).each(function(i, val){ $(val).addClass( "coolaxs_highlight_titles_colors" ); });
 $(val).addClass( "coolaxs_bright_contrast" ); if ( coolaxs_hasBkgcolor(val) ) $(val).addClass( "coolaxs_bright_contrast_bkg_color" );
 $(val).addClass( "coolaxs_dark_contrast" ); if ( coolaxs_hasBkgcolor(val) ) $(val).addClass( "coolaxs_dark_contrast_bkg_color" ); 
 $("html").addClass("coolaxs_prevent_animations");
 $("*,body,a,span,li *").addClass( "coolaxs_readable_font" ); 
 $("*").not(':focusable,a,span').addClass( "coolaxs_big_white_cursor" ); 
 $("*").not(':focusable,a,span').addClass( "coolaxs_big_black_cursor" ); 
 $('body').addClass('coolaxs_focus_css_activated');// keyboard navigation
 $('body').addClass('COOL_ACCESSIBILITY_right_accessibility_panel');
 $('body').addClass('COOL_ACCESSIBILITY_left_accessibility_panel');
 $('body').addClass('COOL_ACCESSIBILITY_bottom_accessibility_panel');
 $('body').addClass('COOL_ACCESSIBILITY_top_accessibility_panel');
</code></pre>
Accessibility declaration example
<h3></h3>
#### attaches great importance to providing a high quality, professional and accessible service to all residents, including those with disabilities.
Measures are being carried out in order to make this website accessible.
Accessibility adjustments were made based on the recommendations for Intenet Contents at AA rating.
Browsers support:
This website support popular browsers such as: 
Mozila Firefox, Google Chrome 
Questions about accessibility:
For questions or suggestions regarding accessibility you may send an email to ##########
Email to: ###@#####
Telephone: ########## 
Accessibility adjustments that were made:
In order to meet the accessibility requirements, several adjustments were made to the site:
<pre><code>
</code></pre>
For your knowledge :
The site uses the ?local storage? entries option in the browser to maintain the menu preferences settings and the accessibility of the pages of the site. 
This ?local storage? is not sent back to the server and therefore does not provide any information about your browsing. 
These ?local storage? entries are deleted when you delete cookies ? and you can set any browser to delete all cookies upon closing the browser 
Or alternatively if you want the accessibility menu preferences to be preserved ? do not delete the cookies files
Thank you and happy surfing.

Cool Accessibility

Accessibility plugin - Make the site easier to read and navigate

WordPress.org

David Perez

Evan Herman

Dion Hulse

Gustavo Bordoni

Alex Sanford

Francisco Torres

Plugin Check is a tool for testing whether your plugin meets the required standards for the WordPress.org plugin directory. With this plugin you will be able to run most of the checks used for new submissions, and check if your plugin meets the requirements.
Additionally, the tool flags violations or concerns around plugin development best practices, from basic requirements like correct usage of internationalization functions to accessibility, performance, and security best practices.
The checks can be run either using the WP Admin user interface or WP-CLI:
<ul>
<li>To check a plugin using WP Admin, please navigate to the Tools > Plugin Check menu. You need to be able to manage plugins on your site in order to access that screen.</li>
<li>To check a plugin using WP-CLI, please use the <code>wp plugin check</code> command. For example, to check the “Hello Dolly” plugin: <code>wp plugin check hello.php</code>
<ul>
<li>Note that by default when using WP-CLI, only static checks can be executed. In order to also include runtime checks, a workaround is currently necessary using the <code>--require</code> argument of WP-CLI, to manually load the <code>cli.php</code> file within the plugin checker directory before WordPress is loaded. For example: <code>wp plugin check hello.php --require=./wp-content/plugins/plugin-check/cli.php</code></li>
<li>You could use arbitrary path or URL to check a plugin. For example, to check a plugin from a URL: <code>wp plugin check https://example.com/plugin.zip</code> or to check a plugin from a path: <code>wp plugin check /path/to/plugin</code></li>
</ul>
</li>
</ul>
The checks are grouped into several categories, so that you can customize which kinds of checks you would like to run on a plugin.
Keep in mind that this plugin is not a replacement for the manual review process, but it will help you speed up the process of getting your plugin approved for the WordPress.org plugin repository, and it will also help you avoid some common mistakes.
Even if you do not intend to host your plugin in the WordPress.org directory, you are encouraged to use Plugin Check so that your plugin follows the base requirements and best practices for WordPress plugins.

Plugin Check (PCP)


I found a problem in the plugin and created a new issue in the repo. They fixed it and released a new version in less than 24hs! Very responsive team 👏


Speedy feedback by the team


That a great tool! Thank you guys. It can help us quickly identify some issues with our code that might otherwise be overlooked. 



I hope it gets better by the time and save time to a lot of people :)


Thanks for this


Great tool. It will probably save a lot of time for those who are waiting for their plugins to be reviewed, and would probably get a lot of homework to do.



Great initiative. Well done!



Hopefully it will make new plugins to get an approval faster. 🤞


Must have for any plugin developer


Unfortunately, one of the most dangerous PHP functions shell_exec is required and this is not specified anywhere from what I can see.


shell_exec is required


Awesome plugin to learn and improve code and myself. Thank you!


Must-have for any developer!


Wonderful plugin.Looking forward to more features.


Now you can be closer to Wordpress development standards


A great way to validate plugins against WordPress ecosystem standards. Yet another useful tool.


That's a great start


We always use this plugin before submit to Wordpress plugin repository


Great Plugin


DevTools for WordPress is an essential toolkit for WordPress plugin developers, providing a comprehensive suite of features to simplify and accelerate the development process. This plugin is designed to enhance your coding efficiency, improve testing workflows, and ensure seamless integration of your custom plugins into WordPress environments.


Useful plugin for plugin Developer


This tests for a ton of different aspects of plugins. A must have for developers


A must have for plugin development!


Thanks, it is useful to find security issues like missed escape function or sanitization even if you do not plan on submitting the plugin to wordpress.org.


Useful to find security issues


I am very impressed with this plugin. I am in the final steps of submitting a new plugin and through the approval process this has helped speed up the process.



I am developing a script that will install this plugin if not already installed then run the cli tool to create a report. Eventually this will be a step in the CI/CD pipeline.



cli usage can be found on the project's GitHub project under docs/CLI.md



I got some ideas for this plugin to make it more friendly for GitHub, starting that convo with the contributors next.


This is awesome! WP-CLI supported!!!


Run it on any plugin, including popular ones like Woo and you'll see tons of nonsense "Error" messages about inescaped output. This doesn't help anyone. These so-called error messages appear even for static text or well trusted data. 



Just a random example from Woo:The plugin reports "WordPress.Security.EscapeOutput.ExceptionNotEscaped" for this:throw new \Exception( sprintf( __( 'Could not find classname for order ID %d', 'woocommerce' ), $order_id ) );$order_id is already int, ensured by the function, and additionally %d ensures it cannot output anything dangerous. You have to either make this smart enough to find real issues or remove these nonsense messages entirely.How is this helping anyone?






Tons of false positives


This tool is a must for every WordPress plugin developer. You can use phpcs with WordPress standards and other useful tools, but this is an essential step to check your plugin, not only if your intention is to publish to WordPress public repo. Accomplish these standards is a must for everyone who works as plugin developer.



Thanks, plugin team, for this powerful tool. Now our developer lives are easier.


The best tool for WordPress plugin developers


This plugin is excellent for catching common mistakes before submission. It significantly saves time by reducing the back-and-forth process. I used it for the first time, and I really liked how efficiently it worked.


Very useful , Thanks !!


This plugin is extremely helpful for developers and is indispensable for reviewing and refining code before release. Thank you to the WordPress team for developing such a truly useful plugin.



I have a suggestion regarding the code inspection feature—it would be beneficial to integrate function call analysis. For example, when source code calls intermediary functions that handle nonce verification, sanitization, and other input validations within shared classes, it may result in false positives. This could potentially impact the efficiency of the plugin review process.



Overall, this plugin is fantastic for me! Many thanks to the WordPress Team!



Warm regards,


Essential Plugin for Developers


Simple and effective plugin check tool, there is room for improvement and adding more functionality with AI, but overall it currently still gets the job done.


Simple and effective tool for quick plugin checks


By it's nature this is going to flag false positives - potential issues that you've dealt with in different ways, or issues that don't necessarily apply to your particular case - and it does. But it's a really useful tool to run a quick check and uncover little omissions or improvements to be made.


Helpful

Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices.

Cool Accessibility vs Plugin Check (PCP)