A review against WCAG 2.2 AA left places a screen reader user could not work: - Key bindings: a key's button says the command and the key, the clear button which command it clears; a new key is said aloud and focus comes back to its row. The on-screen keyboard is reached with Tab and walked with the arrows. - Number fields read their label; the spin buttons are named and left out of Tab. - Dialogs: Enter presses the main button, Esc closes, focus starts on the first button and the message is read with it. - Consist: every change is said - added, removed, turned, moved, replaced, undone - and the strip is a named list; a turned card says so. - Searches say how many entries are left once typing pauses. - Hasler tapes, the black box timeline, timetable and cab panel take focus, work from the keyboard, read their value as it changes and draw a focus frame. - Section reset and level controls, the crew button and the tabs carry names; English names from Avalonia's templates are read in the starter's language; sort and crew menus are radio items. - Input borders reach 3:1 against the panels; Tab starts at the top bar; the splash screen has a title and its progress reads the loading step.
StarterNG
Launcher for the MaSzyna train simulator, written in C# with Avalonia.
Building a native (NativeAOT) build
The project publishes as a self-contained NativeAOT binary — no .NET runtime is
needed on the target machine. The commands below are the same ones CI runs, see
.github/workflows/dotnet.yml.
Requirements:
- .NET SDK 9
- Linux: a native toolchain and zlib headers —
sudo apt install clang zlib1g-dev(Debian/Ubuntu) orsudo dnf install clang zlib-devel(Fedora) - Windows: the Visual Studio C++ build tools (Desktop development with C++)
Restore for the target runtime first, then publish:
dotnet restore StarterNG/StarterNG.csproj -r linux-x64
dotnet publish StarterNG/StarterNG.csproj \
-c Release -r linux-x64 --self-contained true --no-restore \
-p:PublishAot=true -p:PublishTrimmed=true \
-o publish/linux-x64
For a Windows build swap both linux-x64 occurrences for win-x64 (and the
line continuations for PowerShell backticks). NativeAOT does not cross-compile,
so the Windows package has to be built on Windows and the Linux one on Linux —
that is why CI uses a windows-2022 and an ubuntu-22.04 runner.
The output directory is the whole distributable: the Starter executable, the
Skia/HarfBuzz native libraries and startercfg/ with the translations and the
default key bindings. The .dbg (or .pdb) file next to it is debug symbols and
can be dropped from a release. Trim/AOT analysis warnings during the publish are
expected and do not fail the build.
CI builds both runtimes on every push and pull request to main and staging,
and on manual dispatch. Pushes additionally replace a rolling pre-release with
the packaged artifacts — tagged latest for main and staging for staging.
Development build
dotnet build StarterNG/StarterNG.csproj