Browser Extension enhancements

Improved icon states in browser toolbar

We introduced a disabled state for the Browser Extension icon in the browser toolbar, that makes it easier for users to identify whether the extension is enabled or disabled on a webpage.

• Enabled: The icon appears in light blue.

• Disabled: The icon appears in grey.

This update helps prevent confusion when users forget that they previously disabled the Extension on a specific page and wonder why it does not open the next time they visit.

Browser Extension

Quick Scan progress bar

We replaced the static spinner on the Quick Scan screen with a progress bar. This enhancement provides users with clear visibility into the scan’s progress, and shows which stage it is in and how far along it has progressed.

Removal of legacy score calculation

The legacy compliance score calculation option has been fully removed from the Optimize UI. This feature previously allowed users to use an older method of calculating compliance scores in Acquia Optimize.

As part of this change, we have also removed the Account Settings menu in Admin Settings, where users previously enabled or disabled legacy score calculations.

Accessibility

• Resolved an issue where Mobile Accessibility guidelines were missing from the Features dropdown in Edit Domain, despite being enabled for the account.

Quality Assurance

• Fixed an issue where bulk actions in Misspellings were not working.

Statistics

• Resolved an issue where the Actions tab in Events displayed no data when the UI language was set to a language other than English.

Scans

• Fixed time out issues when the scan encounters pages that use Office365 login.

Browser extension

• Fixed an issue where double scrollbars appeared in the Content section.
• Resolved a scenario where the Extension displayed "No issues found" in modules even when issues were present.
• Added a toast message to confirm successful action when users click “Clear Extension Cache”.
• Resolved an issue on the View Options screen where the "Screen Resolution" section appeared twice.

New articles in the Accessibility Guide¶

• Heading is descriptive
• iframe elements with identical accessible names have equivalent purpose
• Each label describes its associated input element

These new articles provide guidance on best practices for resolving accessibility issues.