Version 5.4.1. Same-day patch.
Interaction Sweep focus-indicator detector rewritten. The v5.4.0 detector reported false positives when checking JavaScript-rendered sites because it used a runtime approach that browsers deliberately do not surface for programmatic focus. The v5.4.1 detector inspects the page's stylesheets directly and only reports when no CSS rule with :focus, :focus-visible, or :focus-within applies visual styling to the element.
Finding clustering: identical repeated findings now collapse into one row that names the count and lists sample elements, so a page with 200 identical issues shows 1 row instead of 200.
Site Crawl UI rewritten in plain English.
No new permissions.

Version 5.4.0 ships the new Interaction Sweep engine.
Four runtime detectors that static accessibility rules cannot catch.
Focus-accept. Focuses every element in tab order and flags any that decline. Catches SPA route transitions where an element is still in the tab order after its ancestor has unmounted.
Focus-indicator. Snapshots outline, box-shadow, border, and background before and after focus. No change means no visible focus indicator. Catches sites shipping outline zero via utility CSS without a focus-visible fallback.
Keyboard-trap. Focuses each element and dispatches synthetic keydown for Tab, Shift plus Tab, and Escape. Flags any handler in the propagation path that calls preventDefault on those keys. Catches modal focus traps and Escape-swallowing dialogs.
Unreachable-clickable. Finds cursor-pointer or onclick elements that are not natively focusable, have no focusable role, and no tabindex zero or higher. Mouse users can click them; keyboard users are locked out.
Triggered by a real-user report on 2026-09-29 that neither AMASAMYA nor any other automated auditor flagged a public government site as inaccessible despite the site being unusable with NVDA and JAWS. Root cause was architectural: every static rule engine looks at the DOM at one point in time. Interaction Sweep observes runtime behaviour.
No new permissions.

Version 5.3.5. Two fixes.
Focus parity on Alt+Shift+1. On Firefox, browser.sidebarAction.open() opened the sidebar but left focus on the triggering page, so a keyboard user pressing the shortcut had to Tab back into the sidebar manually. Sidebar panel.js now focuses the first tab on load and on visibility change, so the shortcut lands you on the first panel tab immediately.
Version display now reads from the manifest. The panel header, About section, and footer previously showed a hardcoded "v4.3" that did not update as the extension patched. Panel.js now reads the version from browser.runtime.getManifest() at load and writes it into every version slot, so what you see in the panel matches the installed version.

v5.3.4 maintenance patch. Removes the "Learn in AMASAMYA Academy" row from the finding detail disclosure inside the results table. The Academy programme was retired on 15 September 2026 and the previous link now redirects to the product home. The finding detail still shows Element, Criterion, Computed, Required, and How to Fix. No new permissions, no behaviour changes.

v5.3.3 Firefox-only patch, two bugs fixed.

One. The suggested keyboard shortcut in the manifest was Ctrl plus Shift plus U, which Firefox reserves. Users reported it never worked. Now Alt plus Shift plus 1, matching Chrome and Edge.

Two. background.js called chrome.sidePanel.open on toolbar-button click, which is a Chromium-only API and silently failed on Firefox, so the sidebar never opened. Now uses browser.sidebarAction.open.

No new permissions.

v5.3.2: two screen-reader improvements to the findings-table results view.
• Affected component (CSS selector) is now part of every row's aria-label, so NVDA / JAWS users hear which element failed without expanding the row.
• New "Accessible PDF" button in the export toolbar. Opens a print-ready report in a new tab and auto-triggers window.print(); user picks "Save as PDF" as the destination. No new permissions.

v5.3.0 adds GIGW 3.0 and IS 17802 audit engines for India-specific accessibility standards, a VPAT 2.4 ACR exporter, and visual diffs on audit history. Same permissions as v5.2. No new outbound data flows.