About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Inclusive employers must verify that assistive technology (AT)—screen readers, voice control, magnification, alternative keyboards—works across the full path: local device, Remote Desktop or web client, session host, and the line-of-business application itself. Remote sessions add latency, audio routing, and focus-model quirks that pass a quick visual test but fail for AT users.
Why it matters
Promising “accessible hosted access” without testing can leave skilled staff unable to do production work and may require employers to assess applicable legal obligations—including duties under the Disability Discrimination Act 1992 (Cth; Federal Register title ID C2004A04426). This is not a statement that any hoster, client, or LOB product is certified accessible. WCAG applies to web content; Windows LOB plus RDP is a stacked accessibility surface where each layer must cooperate. This article frames verification work; it is not a certification statement for any hoster or app.
How it works
Users may run AT locally while interacting with a remote session that renders the LOB UI server-side, or rely on AT tools installed inside the session. Microsoft lists multiple client platforms for RDS but does not publish a single AT compatibility matrix for every LOB product.
Browser-presented sessions (web client) add another boundary: the browser’s accessibility tree may not expose remote content the same way as a native RDP canvas. Microsoft documents optional Group Policy for remote app UI Automation redirection, which, when enabled, allows local UI Automation clients such as Narrator or Magnifier on the user’s PC to interact with UI in a remote session—this is a configuration and pilot item, not a default guarantee for every deployment.
Labelled example — contact centre: Screen reader on Windows with native Remote Desktop client to a published CRM RemoteApp; test call logging task with IT and AT specialist present.
Labelled example — public sector forms app: Magnifier at 200% on dual monitors; verify dialog focus order does not trap keyboard users after reconnect.
What to choose and why
| Verification step | Owner |
|---|---|
| Test with actual AT users/tools | Employer + AT specialist |
| Document supported client + AT combination | IT architecture |
| Retest after client or LOB upgrade | Change management |
| Provide interim accommodations if gap found | HR / workplace adjust |
Do not substitute a sighted tester clicking through menus for structured AT testing. Record client version, session type (desktop vs RemoteApp), and network conditions.
Read next
Related articles you may want next.
- HostingWhat "works in a browser" really means for Windows line-of-business softwareUnderstand what browser access means for Windows business software, then check supported devices, clipboard limits and the workflows your staff need.Read article
- HostingBrowser client or native Remote Desktop for hosted business appsChoose browser or native Remote Desktop access for hosted business applications by checking the devices, printing and everyday workflows your staff need.Read article
- HostingMultiple monitors and display scaling for remote business softwareChoose remote display settings using the correct client support table, then test monitor layouts, scaling and everyday application tasks on your staff’s devices.Read article
Risks and limits
UI Automation redirection behaviour requires policy and pilot validation. No AT session was executed in a lab for this article.
Sources
- Remote Desktop Services roles — accessed 2026-11-16; ms.date 2024-07-03. Client platform list.
- Policy CSP – TerminalServer/RemoteAppUIAutomation — accessed 2026-11-16. Optional UI Automation redirection for remote apps; Narrator/Magnifier example text.
- WCAG 2 Overview — accessed 2026-11-16. Web content accessibility scope.
- Disability Discrimination Act 1992 — Federal Register title ID C2004A04426 (principal Act).
Related reading
- What “works in a browser” really means for Windows line-of-business software
- Browser client or native Remote Desktop for hosted business apps
- Multiple monitors and display scaling for remote business software
- Business solutions (NetLeverage service context)
Learning notes
- AT must be tested on the full client–session–app chain.
- Web-presented Windows apps are not equivalent to accessible native web apps.
- Reconnect and MFA steps need AT retesting, not only the happy path.
- Accommodations may be required while gaps are remediated.
- Accessibility verification is evidence-based, not marketing language.
This article was originally published on .