All notable changes to Interactive Tour are documented here.
The format follows Keep a Changelog, and this project uses Semantic Versioning.
[0.2.0] - 2026-09-15
Fixed
- Alerts, table rows, icon-only buttons and password fields now pick up the
corrected shared styling. The corrections were released earlier in the shared look-and-feel package, but this app was still pinned to an older release, so none of them were reaching the screen.
Changed
- The release notes page now uses the shared platform component, so it renders
formatted releases instead of raw text and follows the selected language instead of always showing English.
Fixed
- Buttons and links near the top of a page can be clicked again. The bar across the top of the
application floated above the page instead of sitting above it, so it covered roughly the first 85 pixels of every page and swallowed any click that landed there. Page headings in that strip were also partly hidden behind the bar.
Changed
- The application now uses a newer release of the shared application frame. Alongside the fix
above it carries the shared-frame work of the past weeks, so some surfaces may look slightly different.
Two fixes that arrive together, both from picking up a corrected version of the shared appearance package that this application had been left behind on.
The colours shown for the fraction of a second before a page finishes loading now match the colours the page actually settles on. They were drawn from a set of names the application had stopped using, so the very first paint could look wrong before correcting itself.
The button that switches between the light and dark appearance now describes itself properly to screen readers and to anyone hovering over it. It had been announcing an internal placeholder instead of a sentence, so people relying on a screen reader were told the button's internal name rather than what it does.
Ticked checkboxes and selected radio buttons stay clearly visible when you point at them. Previously the coloured fill of a ticked checkbox faded to a barely-there tint as soon as the pointer reached it, leaving its white tick almost invisible; a selected radio button faded the same way, and because the filled dot is the only thing marking a radio button as chosen, it briefly looked as though the selection had been lost.
In the dark appearance the accent colour used for selected and focused controls is also a touch brighter. It had been very slightly too dark to stand out against the raised panels that cards, tiles, and dialogs are drawn on, so a tick box, a selected radio button, a switch, or a slider inside one of those panels was harder to pick out than it should have been. The keyboard focus outline benefits most: it is the only thing showing which control you have moved to with the keyboard, and inside a panel it had been right at the edge of being too faint to see.
Button labels remain just as legible, the light appearance is unchanged, and selected rows in tables, highlighted text, and slider and progress tracks keep the soft tint they have always had.
Form fields, dropdowns, checkboxes, radio buttons, and outlined buttons now have a clearly visible outline in both light and dark themes, meeting the accessibility contrast requirement for control boundaries. Previously these outlines were too faint to separate a control from the surface behind it, and because the dark appearance is what most people see by default, the weaker of the two was the common case. Pointing at one of these controls in the dark appearance now brightens its outline instead of making it vanish, so it stays clear which one is under the pointer. Dividers, table rules, and panel outlines are deliberately unchanged and stay understated.
These styling updates also now reach people who have visited before. Previously the browser could keep using its saved copy of the shared styling after an update shipped, so a returning visitor might have continued seeing the old appearance for a while. Each update is now published under its own address, so browsers pick it up immediately while still caching aggressively between updates.
Two changes that arrive together, from picking up corrected versions of the shared appearance and layout packages this application had been left behind on.
The warning and information colours shown when the appearance service cannot be reached are darker, so the text on them is legible. They had been too light against the page background to meet the accessibility contrast standard.
Switching to another application from the app menu now lands on the page that application nominates rather than its bare address. Where an application asks to be entered through its sign-in page, that is where you arrive: with a session already open you arrive signed in rather than as a stranger, and without one you are asked to sign in at the door. This tour itself needs no account, so for its visitors that is a sign-in prompt where a public page used to appear.
Fixed
- Update shared theme packages with the corrected dark error foreground and
consistent filled, outlined and text action colors.
The tour no longer skips a step when the thing it wants to point at is slow to appear or sits partly off the edge of the screen. A step used to be passed over in silence if its target had not finished being drawn at the moment the tour looked for it, or if any part of that target lay outside the visible area. The tour now waits a moment for the page to settle, and treats a target as visible when it can be seen at all rather than only when it fits entirely on screen. The same correction runs the other way too: a step whose target is genuinely hidden is now recognised as hidden and passed over, where before it could draw a small empty highlight in the corner of the screen pointing at nothing.
[0.1.1] - 2026-07-07
Added
- Added product version metadata, a public changelog page, and a footer version
link.
Changed
- Improved shared app shell styling so returning users get current visual
updates.
- Improved app-switcher responsiveness on static pages.
Removed
- Removed unused sign-in UI from the public tour because the tour is
intentionally public.
[0.1.0] - 2026-06-25
Added
- Established 0.1.0 as the first Interactive Tour SemVer baseline for
deployed services.