Skip to content

Windows parity: Standard-control UIA, sidebar selection and Narrator qualification remain #745

Open

Description

@coneilen

Current reconciliation - 2026-11-09

The 2026-10-13 narrowed scope below supersedes the original terminal-text/edge-element/live-announcement demands: macOS exposes none of those as required parity surfaces. The remaining contract is named roles/actions for macOS-presented dialogs, sheets, alerts, menus and standard controls, correct sidebar selection, daemon-driven tree updates, and live UIA/Narrator qualification.

Merged PR #911 migrates forms to the shared native sheet framework; PR #965 adds the native New Workspace form/Create & Open path. PR #963 supplies bounded selected-pane focus/input qualification, not general accessibility conformance. Still open / Partial: the complete standard-control matrix, Graph/Quick Chats native selection #801, daemon-to-tree integration and Narrator behavior. Existing default integration includes button/command fallbacks; it is not complete physical-pointer fidelity or direct proof of the application's separate pipe handle.


The original report, acceptance criteria and historical evidence below are preserved; the dated scope/progress above supersedes obsolete missing-feature claims.

Is your feature request related to a problem?
Parity row UI Automation tree (Accessibility, input, and visual behavior) in investigation/ui-parity-matrix.md is Partial.

macOS: Names, roles, selection, invoke/toggle, focus and live status for every visible surface.

Windows today: A broad UIA tree with named fragments across the shell.

Gap: Native terminal text results, applied selection, visible caret/geometry, range/HRESULT conformance, retained-generation behaviour, atomicity, daemon-to-model UIA integration and some dialogs need implementation or evidence.

Describe the solution you'd like
Implement the terminal TextPattern and selection exposure and the remaining dialogs, then a UIA conformance pass.

Describe alternatives you've considered
N/A

Additional context
This is an implementation gap: work remains in the product before the row can be validated. Parity status and the beta25 Dev Box review are recorded in #719.

Activity

  1. added
    enhancementNew feature or request
    parityWindows/macOS UI parity ledger row (investigation/ui-parity-matrix.md)
    on Oct 13, 2026
  2. coneilen commented on Oct 14, 2026

    @coneilen
    CollaboratorAuthor

    Narrowed to macOS scope (2026-10-13). macOS is the ground truth, so requirements macOS does not have are no longer parity requirements. This was checked against macOS source by the parity extras audit; citations are in the audit and the ledger.

    Dropped: terminal text, edge elements and live announcements (macOS exposes none of these).

    Remaining requirement:

    Every dialog, sheet, alert, menu and standard control that macOS presents is in the UIA tree with a name, role and invoke or toggle, sidebar rows report selection, and daemon-driven changes update the tree. Verify with a live UIA client and Narrator.

  3. added
    P2 featureParity priority 2: features macOS has that Windows lacks
    on Oct 14, 2026
  4. changed the title [-]Windows parity: UI Automation tree terminal text, selection and remaining dialogs need work[/-] [+]Windows parity: Standard-control UIA, sidebar selection and Narrator qualification remain[/+] on Nov 9, 2026
  5. self-assigned this
    on Nov 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2 featureParity priority 2: features macOS has that Windows lacksenhancementNew feature or requestparityWindows/macOS UI parity ledger row (investigation/ui-parity-matrix.md)windowsWindows port

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions