Accessibility and application information

UI Automation and MSAA can expose text, control identifiers and geometry. Browser extensions and application interfaces can provide URLs, links, selections or files.

UIA configuration

Merge rules into conf/default/uia.toml.

ini

[uia_property]
name=30005
value=30045
auto_id=30011

[uia:e:notepad]
def=name|value|@auto_id

e selects a process, c a window class, ec a process/class combination, e+c a process/control combination, and c+c a class/control combination. More specific matching configurations take precedence.

Ordinary fields participate in classification. The @ form keeps the corresponding original field without the same classification behavior. UIA fields commonly use a uia_ prefix.

MSAA configuration

ini

[acc:e:example_app]
def=value|name|role|pos

Replace example_app with the actual process identifier. Software-specific messages, pipes and title processing are configured separately through attach.toml.

Verify the provider

Inspect the actual fields before writing conditions. The target application must expose the information, an extension must be connected when needed, and the collection must complete for that interaction. Enabling a local service alone does not supply browser data.