Plugin Assessment Questionnaire

Would you like to complete Part 4: Accessibility*

This part of the questionnaire is optional for you. If you do not complete it, OIT staff will complete it on your behalf. Note: The more information you’re able to submit now, the faster the review process will be completed.

Accessibility

Some questions in this part may require you to have a local development installation of WordPress in order to run tests on your plugin.

To complete all tests, we recommend:

Make sure your local dev site is running the latest version of WordPress and a version of PHP with active support (opens in a new tab).
In your wp-config.php file, be sure to add define('WP_DEBUG', true); to enable error reporting.
Install WP CLI (opens in a new tab) on your dev site. Help installing WP CLI with MAMP (opens in a new tab).

If you do not already have a local dev site to test with, see Local (opens in a new tab) or MAMP (opens in a new tab) to get started.

If you’re not sure how to do complete any of the items listed below, feel free to skip to the next item. Someone from OIT will fill in the rest.

Set up accessibility plugin unit test

I have set up the accessibility theme unit test data on my dev site

The WordPress Accessibility Team has created sample content for testing plugin accessibility. Save the contents of a11y-theme-unit-test-data (opens in a new tab) as an XML file and import it using the WordPress content importer.

Create test content for custom functionality

I have created test content for any custom functionality.

Based on what was documented in Part 2 of this questionnaire, create any test content using the custom post types, blocks, shortcodes, or widgets added by this theme. Be sure to make your test content representative of how they’re intended to be used.

Set up axe-cli

I have set up axe-cli for use on my dev site

axe by Deque (opens in a new tab) is an accessibility testing tool. It includes a free Chrome browser extension, and is frequently used behind the scenes in other testing tools (eg. Google’s Lighthouse).

@axe-core/cli (opens in a new tab) is a package for running axe from the command line. Install this package!

Output from axe for each unit test page and post.

In this field, paste the axe output for every post and page on your website. You can do this easily with WP CLI by running the following commands on your dev site:

wp post list --url=[your dev site URL] --post_type=page --field=url | xargs -n1 -I % axe %
wp post list --url=[your dev site URL] --post_type=post --field=url | xargs -n1 -I % axe %

Repeat for any custom post types added by the plugin.

Manual Test: Keyboard navigation test

All interactive elements have a visible focus indicator
Skip link is first element in the page
Header is keyboard navigable
Navigation menu (including dropdown menus) is keyboard navigable
Content is keyboard navigable
Sidebars is keyboard navigable
Footer is keyboard navigable

Check all elements of the page that can be reached using the keyboard only and appear in a logical order.

Manual Test: Alternative text

All images included with the plugin have meaningful alt text (or are purely decorative)

Manual Test: Links

Links are underlined, or sufficiently distinguished from content around them (not using color alone)

Manual Test: Color contrast

Text has sufficient contrast against the background in all settings (content, header, footer, etc)
All interactive elements have sufficient color contrast to distinguish them from surrounding context

Manual Test: Landmarks and headings

ARIA landmarks are used correctly to describe areas of the page
Hard-coded headings are correctly nested

Additional comments on accessibility

Plugin Assessment Questionnaire

Plugin Assessment Questionaire

Requestor information

Plugin information

Inventory of features/functionality

Security and code quality

Accessibility

Support resources