Post #2316945

@matt Hey Matt, long time no speak. I am reaching out because I am working on an interdepartmental working group to develop a desktop software accessibility testing methodology for the government of canada. We are starting with Windows. We ran into some complex discussions about the intersection of OS APIs/AT. They asked if anyone knew someone with direct experience with screen readers on windows who might be willing to share their insights during 1 of our meetings. (These are primarily compsci professionals who work in digital accessibility in the GC) Given your background in writing adaptive technology I thought immediately of you and was wondering if you would consider it. We are focusing on the technical intersection between accessibility APIs, adaptive technology behavior, and desktop software design. Specifically, they were looking to ask questions around: How software exposes information to the operating system through accessibility APIs such as UI Automation and IAccessible2 The reality of how adaptive technology like JAWS and NVDA intercept and translate API calls Semantic mapping between native Windows controls and custom UI elements How desktop applications populate the accessibility tree and handle focus changes Differences in how native Windows applications handle off-screen content compared to web browsers The relationship between system themes, performance, and accessibility API communication Methods to verify the complete chain from software through API to adaptive technology to the user We would benefit greatly from your insights on how AT interprets what the API provides and where the most common breakdown points occur. Thank you for considering this.