UI Automation or MSAA for Windows 8 Metro Apps: Choosing Rich API Support vs Legacy Compatibility

Developers building Windows 8 Metro‑style applications must decide which accessibility API to implement for reliable keyboard‑only navigation.

The goal is to provide screen‑reader users with accurate role, state, and focus information while keeping development effort reasonable.

UI Automation offers a modern object model, custom control patterns, and tighter integration with Narrator, but requires targeting the Windows Runtime and writing provider code.

MSAA remains usable through the UI Automation compatibility layer, giving broader reach for legacy assistive tools, yet it lacks support for newer patterns such as toggle, range value, and text flow, which can impair keyboard navigation fidelity.

Given these trade‑offs, what factors should weigh most heavily when choosing between the two approaches?

• Is the added implementation cost of UI Automation justified by the improvement in keyboard navigation accuracy for touch‑optimized controls?
• Can reliance on the MSAA compatibility layer meet accessibility requirements without sacrificing essential UI Automation patterns?
• How does the choice affect long‑term maintenance and future platform updates?