v1.9.0-beta.1

Overview

This beta release features streamlining codebase efficiency and improving system information. Key updates include the optimization of issue summary logic with better code structure and readability, a refactor of the system information to the WordPress core site health information, and several bug fixes.

Changelog

• Created: a class that creates the accessibility statement on activation
• Removed: custom database query that checked for existing accessibility statement in exchange for the get_page_by_path() function
• Fixed: bug with trying to compare the simplified summary ordinal value and added fallback
• Removed: wp_send_json_error() from simplified_summary Ajax function when the simplified summary is empty
• Added: simplified summary grade-level, message, and icon logic to the summary() Ajax
• Fixed: issue with the submit button text showing as Submit Query in Firefox.
• Updated: missing transcript rule to skip certain types of links
• Added: missing UTM parameters to the welcome page URLs.
• Removed: legacy system information code
• Removed: cbschuld/browser.php composer package
• Added: class structure for site health
• Added: site health health information for free, pro, and audit history plugins
• Added: update database class
• Removed: edac_before_page_render functions from the main file
• Added: frontend validate class
• Added: frontend validate unit tests
• Removed: unused new window warning meta update functions
• Fixed: front end highlight focus issue
• Added: summary generator class to replace the edac_summary() function
• Deprecated: edac_summary() function

Feedback

Your insights and experiences with this beta version are invaluable to us. We're especially interested in hearing about:

• Usability: How is your experience with the new features? Are there any aspects that are particularly useful or, conversely, challenging to use?
• Performance: Have you noticed any performance improvements or issues compared to previous versions?
• Bugs and Glitches: Please report any bugs or unexpected behavior you encounter. Details about your environment (like OS, browser version, etc.) along with steps to reproduce the issue are highly appreciated.
• Suggestions for Improvement: We welcome your ideas on how we can make this software even better. If there's a feature you'd like to see in the final release, let us know!

To provide feedback, you can use the following channels:

• Issue Tracker: For bug reports and feature requests, please use our GitHub Issues page.
• Direct Contact: Feel free to reach out via email or our general contact form for more direct or detailed feedback.

Thank you for participating in this beta. Your input is crucial in helping us shape a better, more robust final release!