Mark your calendars! WordPress 6.8 is set to launch on April 15, 2025. WordPress 6.8 will be the first major release of 2025 and will focus primarily on being a polished and bug-fix release. Get ready for a more refined and seamless WordPress experience than ever before! 

Testing early means fewer surprises for users down the line! Whether you have a few minutes or a few hours, your help in catching bugs early during the release cycle ensures a smoother upgrade experience for millions of users after the stable release. Every contribution counts and is deeply appreciated. 

Let’s work together to refine WordPress 6.8! 💪

Stay up to date with the latest pre-release builds by checking the WordPress 6.8 Release Schedule. For real-time updates and discussions, join the #core-test Slack channel. Engage in the testing community by participating in weekly scheduled team meetings and test scrubs.

Table of Contents:

• Testing Tips
• Ways to test WordPress Beta versions
• General Testing Checklist
• Key Features to Test
  • Editor
    • New default rendering mode for editor via post type supports
  • Design Improvements
    • Stylebook improvement for classic theme
    • Reset Button for Color Control
    • Zoom-Out Mode Enhancements
    • Improved Font Picker Previews
    • Success notices for image editing with Undo link
  • Support for Speculative Loading
  • Polishing the Query Loop
    • Fix: Sticky Posts Not Working with Default Query Type
    • “Ignore” Option for Sticky Posts
    • Set Depth Limit for Query Loop
    • Removal of Redundant Sticky State
    • Query Total: Add interactivity.clientNavigation block support
  • Refining Data Views
    • Unify layout behaviour
    • Add confirm dialogue before delete
    • Density option in table layout
    • Use badge component in data view grids
    • Set Featured Image directly from block
  • API launches and iterations
    • New withSyncEvent() function in Interactivity API
    • Block Hooks API
  • Security enhancements
  • Additional performance improvements
• What to Notice
• Where to Report Feedback
• Changelog

Testing Tips

WordPress doesn’t require you to be a certified software tester or professional QA to contribute to testing; use WordPress as you normally would for your own needs. If you encounter any issues or feel something isn’t working as expected, please report them. 

Not sure about the expected behaviour? No worries! Join the conversation on WordPress Slack or create a ticket on Trac, where a helpful global WordPress community is always ready to assist.

Recommendations for Testing WordPress BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process./RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Versions:

• Test CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Features that Matter to You:  Use your site for the purpose it was created. For instance, if you’re a blogger, running a social platform, or managing an e-commerce store, set up a staging site (ask your hosting provider if you’re unfamiliar with the staging site). Update WordPress in the staging environmentStaging Environment A staging environment is a non-production copy of your site. This is a private place to build the site -- design, copy, and code -- until your client approves it for production or live. Sometimes used in addition to, or as a Development Environment., and continue using your site as you would daily. This will help you identify any issues that may affect your regular workflow. Take note of any issues or troubles you experience after the update. Do not test or update your live site with a beta version for testing purposes.
• Use the General Checklist provided in the post below to verify that everything functions as expected after the update.

Ways to Test WordPress Beta Versions

There are multiple ways to test WordPress development or beta versions:

Playground

Playground is an easy and fast way to test beta or release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. versions of WordPress without setting up a full environment. You can quickly spin up a test environment using WordPress Playground.

Local Hosted Site

You can make use of software like Local or wp-env to create a local WordPress site. Once the site is ready, you can install the Beta Tester plugin to switch to the beta version of WordPress.

Setup Steps:

1. Download and install Local.
2. Create a new WordPress site.
3. Once your site is up and running, you can use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party to switch it to the development or beta version of WordPress. This plugin makes it easy to install pre-release versions of WordPress.
   To use the plugin:
   1. Install and activate the WordPress Beta Tester plugin.
   2. Navigate to Tools > Beta Testing.
   3. Choose the Bleeding Edge or Point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. with Nightlies option, depending on what you want to test.
   4. Click on Save Changes
   5. After the changes are saved, you should receive the update notification. Kindly update your WordPress version.

For more detailed instructions, follow this guide.

Via WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/

If you prefer working with command-line tools, use WP-CLI to install a WordPress beta version quickly. 

Steps:

1. Create a local WordPress site using your preferred method.
2. Once the site is set up, open your terminal and navigate to the root directory of your WordPress installation.
3. Run the following command to update to the latest beta/RC version:

wp core update --version=6.8-beta1

OR

wp core update --version=6.8-RC1

(Keep updating the version number as needed. E.g. –version=6.8-beta2)

This method helps you to switch between different versions quickly, making it easier to test specific builds.

Using a Staging Site

Create a staging site for your live production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. and update it to the WordPress beta/RC version. This lets you safely test the new version without impacting your live site. Make sure everything functions as expected before applying updates to your production environment.

Testing Patches

If you plan to test patches, follow these instructions to set up a WordPress development version locally.

Using Playground, you can also easily test individual Core tickets without installing any software in your system, and this is the fastest way to test any PRs.

If there is a specific PR in the wordpress-develop or gutenberg repo that you’d like to test in the browser, you can do so using the following links. Enter the PR number, and the rest will be taken care of.

• https://playground.wordpress.net/wordpress.html 
• https://playground.wordpress.net/gutenberg.html 

General Testing Checklist

If you want to quickly test the updated WordPress version’s compatibility with your site, please verify the following important checks. Enable debugging in wp-config.php to capture the warnings, errors or notices.

1. Update your theme and plugins to the latest versions.
2. Switch to the Beta/RC/Night build you want to test.
3. Check Site Health to see if there are any new errors or warnings.
4. Confirm there are no layout breaks or misaligned elements.
5. Test links and permalinks to ensure there are no 404 errors.
6. Verify that posts, images, and media are displayed correctly.
7. Ensure the sitemap and robots.txt files are functioning properly.
8. Ensure full access to the admin dashboard without errors.
9. If your site has custom blocks, create content in a new blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and edit existing content.
10. Create a new post: 
    1. Add content
    2. Copy-paste text
    3. Manually add media files. 
    4. Save the post
    5. Observe the console for any issues.
11. Create a new page:
    1. Add content
    2. Verify its display in different browsers.
    3. Verify its display in responsive mode.
    4. Verify that the functional part is working as expected regardless of browser or device type.
12. Keep the browser’s developer console open and check for any errors, warnings, or notices.
13. Open the error log file and check for notices, warnings, and fatal errors.
14. Review user roles and permissions to ensure they remain intact.
15. Verify that any scheduled posts or automated tasks (like backups) still function as intended.
16. Ensure all integrated services (like payment gateways or analytics) are operational.
17. Open your site in different browsers and verify that all functionalities work as expected.

Key Features to test

Editor

New default rendering mode for editor via post type supports

The GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ PR #69286 introduces a new approach to setting the default rendering mode in the WordPress block editor based on post-type support. This enhancement allows developers to define how content is rendered in the editor by specifying parameters within the support property of a post type.

Test Steps:

1. Install and activate any block theme. E.g 2025
2. Open a new page
3. Verify that it renders in a template-locked state.
4. Now, disable the “Show Template” in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and reload the page.
5. Verify that it uses “post-only” as the default rendering mode.
6. Re-enable “Show Template” from the sidebar bar.
7. Open a post and confirm that it still renders in “post-only”.
8. Now, switch to a classic theme. E.g. 2011
9. Confirm that posts and pages both are loading correctly without showing the template.

Design Improvements

The design focus is refinement and fixing issues requiring design feedback. Let’s check them one by one.

Stylebook improvement for classic theme

The Style Book now provides a more structured layout, making it easier to preview and understand site colours, typography, and block styles.

Support is available for classic themes that either support editor styles via add_theme_support( 'editor-styles' )  or have a theme.json file. 
Each block example and style group is labelled for better clarity. For classic themes, the Style Book now supports site patterns, which have been relocated to Appearance > Design > Patterns for a more intuitive experience. Previously, patterns were listed under Appearance > Patterns.

Testing Instruction:

Please help identify potential issues and suggest areas for improvement by logging your feedback on #68036. Follow PR 66851 for more details about this fix.

Reset Button for Color Control

A new Reset button has been added to the colour control, allowing users to quickly revert the color changes.

Testing Instruction:

Test Steps:

1. Create a page and a paragraph block. 
2. Add text/background/link colors to the paragraph.
3. Observe the change in the color.
4. Now, hover/focus on the element and observe the presence of the reset(-) button.
5. Clicking on the reset button resets the applied color.

If you encounter any issues or have suggestions, feel free to drop your feedback in this ticket #41866.

Zoom-Out Mode Enhancements

Users can now apply different section styles and designs directly from the toolbar.

Testing Instruction:

Test Steps:

1. Navigate to Appearance > Editor
2. Edit the page and choose the pattern.
3. Enter into zoom-out mode.
4. Observe the toolbar with a newly added icon.
5. Verify that there should be no shuffle button present and that the change design option should be visible.
6. Click on the icon, and it will change color based on the different styles.

Follow PR #67140 for a detailed understanding of the implementation path.

Improved Font Picker Previews

The font family list in Global Styles now previews each font directly in the dropdown. This provides a better visual indication of how the font will look before applying it.
Testing Instruction:

Check #67118 for more information.

Success notices for image editing with Undo link

The outcome of the Image manipulation method is now better communicated in the block editor. The success notices are now displayed at the bottom of the editor. The notices also come with a handy Undo link to revert to the original if necessary.

Testing Instruction:

Test Steps:

1. Create a post or page, insert the Image block and select an image.
2. Try different editing options for Image – edit, zoom, crop, rotate.
3. A correct message should be displayed after processing the media.
4. Also, confirm you can easily undo changes using the snack bar action.

Both these changes are part of different PRs #67314 and #67312 

Additional changes as part of design:

Post Comments Link: Add Border Support. (#68450)

Post Template: Add Border and Spacing Support. (#64425)

Query Total: Add Border Support. (#68323)

Background supports: Add default controls supports. (#68085)

Block supports: Show selected item in font family select control. (#68254)

Fix: Ensure consistency in editor tools for navigation buttons and delete options. (#67253)

Global Styles: Fix handling of booleans when stabilizing block supports. (#67552)

Support for Speculative Loading

We are excited to announce that WordPress 6.8 includes native support for speculative loading, a feature designed to enhance site performance by enabling near-instant page load times. 

What is Speculative Loading?

Speculative loading leverages the Speculation Rules API to automatically prefetch or prerender certain URLs on a page based on user interactions, such as hovering over a link. This proactive approach allows subsequent pages to load more quickly when users navigate to them. 

Default Configuration

WordPress 6.8 configures the speculative loading feature by default to prefetch URLs with a conservative eagerness setting. This means the browser will prefetch resources only when there is a strong indication that the user intends to navigate to a particular link, balancing performance benefits with resource usage. 

Testing Instruction: Customisation via Filters

While there are no options or user interface controls to modify the behaviour of speculative loading as we have in the Speculative loading plugin, developers do this by customising its functionality using the newly added filters with different combinations of values. 

Please check this comment for a more detailed explanation of how to test.

Use a browser that supports the Speculation Rules APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. (e.g., Chrome 108+, Edge 108+) because not every browser supports it. Please refer to caniuse.com for a comprehensive support overview of speculation rules.

Impact on Existing Plugins

With the integration of speculative loading into the WordPress core, the existing Speculative Loading plugin that provides similar functionality will be updated to use the core implementation. The plugin will continue to use its approach to prerender URLs with moderate eagerness, now by adjusting the default configuration set by Core. 

We encourage developers and site administrators to test this new feature in their environments and provide feedback. Your insights are invaluable in ensuring that speculative loading enhances performance effectively across the diverse WordPress ecosystem. 

Please check this ticket #62503 for more information about this enhancement. Feel free to comment and share your feedback/queries/issues regarding performance and speculative loading integration.

Polishing the Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.

Fix: Sticky Posts Not Working with Default Query Type

Previously, sticky posts did not appear at the top when using the default query type in the editor. This issue has now been fixed.

Testing Instruction:

Test Step:

1. Have at least one sticky post on the blog
2. Open the template using the editor’s query loop block (index, archive, etc.).
3. Notice that the sticky post is at the top.
4. Open the front of the site and see the sticky post at the top.

Please refer to this #68570 ticket for more details about this fix.

 “Ignore” Option for Sticky Posts

A new “Ignore” option for Sticky Posts has been added to the Query Loop block, giving users more control over including or excluding sticky posts in the query. It adds a new option for the Query block’s sticky post setting: “Ignore,” which doesn’t prepend sticky posts at the top but displays them in the natural order of the query.

Testing Instruction:

Test Steps:

1. Have at least one sticky post on the blog.
2. Create a page and add a simple Query block.
3. Confirm that the sticky post is displayed at the top by default.
4. Change the sticky post setting to “Ignore”.
5. Confirm that it’s now displayed in natural order.

If you find any issues while testing this enhancement, please feel free to share your findings here in issue #66221

Set Depth Limit for Query Loop

The Query Loop block retrieves posts from all levels, and there is no built-in option to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. only top-level posts as they do not have a parent field that can be set to 0. 

The current solution partially addresses the issue by allowing “parents”: [0] to be set programmatically but not providing a UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. option. This PR includes an example Query markup for testing. As for the UI, the Parent filter will be updated once a suitable design proposal is available.
Please share your feedback by commenting here on the issue #68620

Removal of Redundant Sticky State

The redundant sticky state in the Query Loop block has been removed for a more streamlined user experience.

Testing Instruction

Test Steps:

1. Insert a Query Loop and select a pattern with some posts.
2. Open the inspector controls of the block.
3. Verify that the Post Type field is working as expected:
   1. The “Sticky Posts” field is visible when “Post Type” is “Post“
   2. The “Sticky Posts” field is hidden when “Post Type” is “Page“

Query Total: Add interactivity.clientNavigation block support

With RC1 we have introduces the support for interactivity.clientNavigation within the Query Total block. This enhancement enables the Query Total block to interact seamlessly with client-side navigation, ensuring that the displayed total number of query results updates dynamically as users navigate through content without requiring the full page reloads.​

Testing Instruction:

Test Steps:

1. Create a page
2. Add Query Loop block
3. Within the Query Loop, insert a Query Total block.
4. In the Query Loop block, toggle off “Reload full page” from right sidebar.
5. In the Query Total block, change display type to “Range display”.
6. Save the change and open the page in the front end
7. Observe that client navigation is now working as expected.

Please refer to the PR #69661 for more details.

Refining Data Views

“Refining Data Views” allows the customisation and improvement of how data is displayed and managed within the WordPress editor, particularly by utilising the “Data Views” feature which allows users to filter, sort, and organise content more effectively through various options and settings, ultimately leading to a cleaner and more efficient workflow when working with large amounts of data on a website.

WordPress 6.8 release comes with additional improvements and fixes, as mentioned below.

Unify layout behaviour

This update aims to improve the user experience by providing a more intuitive interface. The implementation includes adjustments to the existing components to integrate the new media field seamlessly. This enhancement is part of the ongoing efforts, and to keep up with the progress, please check this issue #67391

Testing Instruction:

Test Steps:

1. Open the different data views for Pages, Templates, and Patterns
2. Check the design of the different layouts for List, Grid and Table
3. Check how the “properties” menu works with the different layout

Add confirm dialogue before delete

The existing ‘Permanently Delete’ action lacked clarity and did not include essential safeguards, such as a confirmation modal. This absence increased the risk of accidental deletions. To improve the user experience and minimize errors, this PR introduces a confirmation modal, ensuring users confirm their intent before deleting selected posts.

Testing Instruction:

Test Steps:

1. Go to the WordPress admin dashboard area.
2. Go to Appearance > Editors > Pages
3. Click on the page that you want to delete
4. The page will move to the TrashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days.
5. Now, select the trashed page and use the “Permanently Delete” option.
6. Confirm the deletion in the modal dialogue.
7. Observe the success or error notices appearing for both individual and bulk deletion options.

Please check PR #67824 for more details.

Density option in table layout

This PR #67170 introduces a density option to the table layout while allowing layouts to define specific controls. Instead of a generalized density abstraction, this approach ensures better clarity and avoids confusion for table layouts.

Testing Instruction

Test Steps

1. Go to the WordPress admin dashboard area.
2. Go to Appearance > Editors > Pages
3. Go to Pages/Templates/Patterns 
4. Change the layout to Table View
5. Now, click on the settings icon
6. Observe the newly added Density option
7. Please play around with all three options, “Comfortable, Balanced, and Compact,” and share your feedback if you have it.

Use badge component in data view grids

This update improves consistency in the Site Editor by using a standardised badge for synced patterns. It ensures a uniform look while keeping the existing functionality unchanged. The new Badge component is integrated into the DataView grids to enhance consistency and maintainability.

Testing Instruction:

Testing Steps:

1. Navigate to the WordPress dashboard
2. Go to Appearance > Editors > Patterns
3. In the Patterns list, identify any patterns labelled as “synced”.
4. Confirm that these “synced” patterns display a badge utilizing the new Badge component, ensuring consistency in design and functionality.

For more details, follow this PR #68062

Set Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. directly from block

WP Core now has a new toggle set under the settings for the post. If a feature image is not set for the post, enabling the toggle control will set the selected image as the feature image for that post. Follow the steps mentioned below.

Testing Instruction

Test Steps:

1. Create a new post.
2. Add an image block. 
3. Enable the “Set this image as featured image” toggle from the settings.
4. Verify that the selected image is set as the post’s featured image.

For more details, visit PR #65896

API launches and iterations

New withSyncEvent() function in Interactivity API

As the first step of running Interactivity API event listener callbacks asynchronously by default (see #64944), a utility function called withSyncEvent is introduced. Developers should use this function to wrap event handlers that require synchronous access to event data or methods, such as event.preventDefault(). For other event handlers that don’t need synchronous event data, the system can defer their execution, enhancing overall performance by reducing the load on the main thread.

Follow the testing instructions mentioned here in the description of PR #68097

Block HooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. API

The Block Hooks API is an extensibility mechanism that allows you to dynamically insert blocks into block themes. In WordPress 6.8, work will continue on improvements to Block Hooks.

• Filtered post content is truncated in post-content block
  • This release also includes a fix for the Post ExcerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. block to display an extra “>” character at the beginning of the excerpt when no custom excerpt is set and the Query Loop block is added to a page. Additionally, for sticky posts without a custom excerpt, the beginning characters of the excerpt are missing.
  • Please follow the testing instructions mentioned here in issue #68903
• We have also updated the document of the block hooks section of the block registration reference guide. Please check issue #65454 for more details on what has been updated.

Security enhancements

The underlying algorithm used to hash and store user passwords in the database has been changed in WordPress 6.8 from phpass portable hashing to bcrypt. Application passwords, user password reset keys, personal data request keys, and the recovery mode key will switch from using phpass to the cryptographically secure but fast BLAKE2b hashing algorithm via Sodium. The full details of this change can be found in the announcement post.

These changes should work and should be invisible to users. Passwords and security keys that were saved in prior versions of WordPress should continue to work after updating to 6.8. Users don’t need to change or reset their passwords; logged-in users should remain logged in, and their sessions should remain valid.

Here are some testing steps that can be taken:

Remaining logged in after the update

• Ensure you have remained logged in to your account after updating to 6.8
• Confirm that logging out and back in again works as expected
• Confirm that the user_pass field for your user account in the wp_users table in the database has been updated — after logging out and back in again it should be prefixed with $wp$2y$ instead of $P$

Password resets

• Start with the “Lost your password?” link on the login screen and initiate a password reset
• Click the confirmation link sent to your email inbox
• Follow the process of resetting your user password
• Confirm you can log in with your new password

Personal data requests

• Log in as an Administrator
• Initiate a data export from Tools -> Export Personal Data
• Click the confirmation link sent to the email address and confirm that the export gets triggered as expected

Remaining logged in after the update

• Ensure you have remained logged in to your account after updating to 6.8
• Confirm that logging out and back in again works as expected
• Confirm that the user_pass field for your user account in the wp_users table in the database has been updated — after logging out and back in again, it should be prefixed with $wp$2y$ instead of $P$

Password resets

• Start with the “Lost your password?” link on the login screen and initiate a password reset.
• Click the confirmation link sent to your email inbox
• Follow the process of resetting your user password
• Confirm you can log in with your new password

Personal data requests

• Log in as an Administrator
• Initiate a data export from Tools -> Export Personal Data
• Click the confirmation link sent to the email address and confirm that the export gets triggered as expected

Additional performance improvements

The additional performance improvements are also part of the WordPress 6.8 release, and details are provided in their respective issues/PRs, as explained below.

• Slow site editor when navigation block has multiple submenu items
• StyleBook for Classic Theme: Resize is not smooth

What to Notice

• Was everything intuitive and easy to use?
• Did you notice any performance issues, such as slow loading or lag?
• Were there any visual inconsistencies or layout issues across different browsers or devices?
• Did the drag-and-drop functionality work as expected, especially in patterns?
• Did the preview mode accurately reflect how the content appeared once published?
• Did what you created in the editor match what you saw on your site?
• Did you observe any other accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues like –
  • Colour contrast or focus management?
  • Did it work properly using only a keyboard?
  • Did it work with a screen reader?
• Did it function smoothly on a mobile device?
• What aspects of the experience did you find confusing or frustrating?
• What did you especially enjoy or appreciate?
• What would have made site building and content creation easier?

Where to Report Feedback

If you find any issues but aren’t sure if it’s a bug or where best to report the problem, share them on the alpha/beta forums of WordPress. If you are confident that you found a bug in WordPress Alpha/Beta/RC, report it on Core Trac for rollback auto-updates and the Gutenberg GitHub repo for every other feature. 

For helpful reporting guidelines, refer to the Test Reports section of the Test Handbook and review the Core Team guidelines for Reporting Bugs.

Changelog

1.0.0 – Initial Post

1.1.0 – Update the post for “Query Total: Add interactivity.clientNavigation block support” (as part of RC1)

Props to @joemcgill @flixos90 @jeffpaul @ankit-k-gupta @desrosj for peer review and a big thanks to @pavanpatil1 for preparing the visuals for testing instructions! 🙌

#core-test