Skip to main content

Platforms

What is proven on a device

Where the platforms' promises have been run, and where they haven't. A promise run in CI on an emulator or a hosted runner is evidence, and this page says which kind the platforms have, so you can decide what to test on your own hardware.

Web
Where its checks run: Real browsers in CI, and the screen readers VoiceOver on macOS and NVDA on Windows before a release.web
A phone's or a tablet's own browser, and other screen readers.web
Apple
Where its checks run: GitHub's macOS runners, with the SwiftUI package built and tested there.apple
A run on an iPhone, an iPad or a Mac that someone owns is not recorded here.
Windows
Where its checks run: GitHub's windows-latest runner, which is Windows Server.windows
A Windows client machine: the runner lacks the App Actions runtime and the On-device Agent Registry, so CI shows the package registers its doors but not that Windows lists them to agents.windows
Android
Where its checks run: Emulators in GitHub's CI.android
A real phone or tablet; a device run is still to come.open

What this means for you

  • Treat a native kit's green CI as the floor of what its components do, not as proof for your own devices. Run your app on the hardware and assistive technology your people use before you tell them it works there.
  • If you have a Windows client machine or an Android device and run a kit on it, say so on the kit's issue and the result goes in the table above.open

Claim sources