ElyOffice/tasks/reviews/R4.1-r3.md

FAIL

1. ../Ely-GPUI-Components/src/menus/draw.rs:186 — Enabled icon buttons expose no accessible activation action. The handlers are attached only to mouse-down; GPUI advertises Click through a click handler or an explicit accessibility action. In the native Windows probe, UI Automation reports enabled Cut and Paste as Buttons with no Invoke pattern, while a normal Button in the same window exposes Invoke. A screen reader's activation command therefore cannot run Paste, contrary to PRD UX-12. Connect accessible activation to the same choose-and-close operation and add a regression that invokes the button through accessibility and checks that it runs once and closes.

2. ../Ely-GPUI-Components/src/menus/draw.rs:116 — Keyboard selection is exposed only as visual highlighting. Open the icon row, press Down then Right to select Paste: Enter runs Paste, but the native accessibility tree remains unchanged, with neither a focused/active descendant nor a selected state for the icon. GPUI logs that the focused menu element has no accessibility role and that assistive technology will announce the whole window. A screen reader cannot identify the command selected by arrow navigation, contrary to PRD UX-12. Expose the active icon through the menu's accessible focus/selection semantics, including its focus owner, and add a regression checking the announced item after arrow navigation.