Does WP Accessibility work with WordPress 5.7 and PHP 7.4.8? A smoke test was performed on .
| 4 | PHP notices |
| No JavaScript exceptions | |
| All test pages loaded successfully | |
| No resource errors |
Memory usage: 22.57 KiB
The average PHP memory usage increased by this amount after activating by the plugin.
Page speed impact:
insignificant.
The plugin didn't make the site noticeably slower.
| WordPress version | 5.7 |
|---|---|
| PHP version | 7.4.8 |
| MySQL version | 8.0.21 |
| PHP memory limit | 256M |
| Last updated | |
|---|---|
| Active installs | 60,000+ |
| WordPress.org page | https://wordpress.org/plugins/wp-accessibility/ |
| Badges |
|
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=wp-accessibility%2Fwp-accessibility.php&plugin_status=all&paged=1&s&_wpnonce=3d8ac2fefe |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.469 s |
| Memory usage | 2.74 MiB |
| JS errors | None |
| Resource errors | None |
| URL | /wp-admin/options-general.php?page=wp-accessibility%2Fwp-accessibility.php |
|---|---|
| Requested URL | /wp-admin/options-general.php?page=wp-accessibility/wp-accessibility.php |
| Aspect | menu-item |
| HTTP status | 200 |
| Load time | 0.461 s |
| Memory usage | 2.71 MiB |
| JS errors | None |
| Resource errors | None |
| URL | / |
|---|---|
| Aspect | front-page |
| HTTP status | 200 |
| Load time | 0.302 s |
| Memory usage | 2.68 MiB |
| JS errors | None |
| Resource errors | None |
| URL | Load time | Memory usage | ||||
|---|---|---|---|---|---|---|
| Inactive | Active | Change | Inactive | Active | Change | |
| /wp-admin/index.php | 0.251 s | 0.267 s | +0.016 s | 2.82 MiB | 2.85 MiB | + 29.83 KiB |
| /wp-admin/edit.php | 0.183 s | 0.191 s | +0.008 s | 2.86 MiB | 2.89 MiB | + 29.52 KiB |
| /wp-admin/post-new.php | 0.870 s | 0.955 s | +0.085 s | 5.02 MiB | 5.06 MiB | + 41.68 KiB |
| /wp-admin/upload.php | 0.466 s | 0.465 s | -0.001 s | 2.7 MiB | 2.72 MiB | + 27.65 KiB |
| /wp-admin/options-writing.php | 0.154 s | 0.160 s | +0.006 s | 2.71 MiB | 2.71 MiB | - 4.38 KiB |
| /wp-admin/media-new.php | 0.270 s | 0.185 s | -0.085 s | 2.67 MiB | 2.7 MiB | + 28.95 KiB |
| /wp-admin/edit-tags.php?taxonomy=category | 0.209 s | 0.185 s | -0.024 s | 2.77 MiB | 2.8 MiB | + 28.73 KiB |
| /wp-admin/post-new.php?post_type=page | 1.112 s | 0.633 s | -0.479 s | 5.01 MiB | 5.05 MiB | + 38.8 KiB |
| /wp-admin/options-discussion.php | 0.252 s | 0.192 s | -0.060 s | 2.67 MiB | 2.7 MiB | + 28.13 KiB |
| /wp-admin/edit-comments.php | 0.227 s | 0.203 s | -0.024 s | 2.78 MiB | 2.8 MiB | + 27.63 KiB |
| / | 0.285 s | 0.233 s | -0.052 s | 2.71 MiB | 2.68 MiB | - 28.23 KiB |
| Average | 0.389 s | 0.334 s | -0.055 s | 3.16 MiB | 3.18 MiB | + 22.57 KiB |
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 48.4% | 1,541 | 496 | 9 | |
| CSS | 38.5% | 1,227 | 123 | 13 | |
| JavaScript | 8.5% | 270 | 6 | 7 | |
| JSON | 3.7% | 119 | 0 | 1 | |
| SVG | 0.9% | 28 | 3 | 4 | |
| Total | 3,185 | 628 | 34 | ||
| Lines of code | 1,510 |
|---|---|
| Total complexity | 290 |
| Median class complexity | 7.0 |
| Median method complexity | 1.5 |
| Most complex class | Wp_Accessibility_Toolbar |
| Most complex function | wpa_update_settings() |
| Classes | 1 |
|---|---|
| Methods | 4 |
| Functions | 48 |
Things that the plugin adds to the site. This section is not intended to be comprehensive. The test tool only looks for a few specific types of added content.
wp_options 18[10-Mar-2021 04:06:58 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 04:06:58 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 04:07:05 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313
[10-Mar-2021 04:07:05 UTC] PHP Notice: WP_Scripts::localize was called <strong>incorrectly</strong>. The <code>$l10n</code> parameter must be an array. To pass arbitrary data to scripts, use the <code>wp_add_inline_script()</code> function instead. Please see <a href="https://wordpress.org/support/article/debugging-in-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 5.7.0.) in /wp-includes/functions.php on line 5313