Skip to content
Open the app

Readable console text, printable reports, and guided walkthroughs on branded previews

This week's thread is that what staff read, hear and print should be as clear as what they see on a good screen, plus an update to how we describe the services that handle data on our behalf.

Console text that was faded is now readable

A few short lines in the staff console were being dimmed on top of an already muted grey, which pushed them below the contrast level accessibility standards ask for. They are now at full strength: the hint under Request tickets in the Inbox, the sublabel under the Insights chart, and the week numbers on the home chart for weeks still to come. They read clearly at normal and high contrast, in both light and dark themes.

Screen readers announce every Insights figure

Twelve figures in the Insights week-by-week breakdown had no spoken label, so a screen reader said nothing for them. Each one now announces its figure and what it describes. Nothing changes visually.

Reports print properly from dark mode

Printing a student morale report, or the Support for Students evidence pack, from a console set to dark mode used to produce near-white text on white paper. Printed pages now always use the light colours, so the document is readable and suitable to attach to a submission. Screen display is unchanged, and a reader who has chosen high contrast keeps it on paper.

Branded previews open with the guided walkthroughs

Branded previews that hide the demo bar had also lost the guided walkthrough, leaving a prospect with no goal cards and no guide panel. They now open with the walkthroughs, and a preview can be tailored to the institution with its own intro line, suggested goals and short notes on individual stops. The guide menu also lets a visitor switch between the student view and the staff console.

What did not change: the walkthrough is scripted. It makes no AI call and stores nothing except a note in the visitor's own browser. It never writes to the shared preview cohort.

Subprocessor list and website hosting

Webflow is no longer listed as a subprocessor. The optional demo lead forwarding it covered was never switched on, and the code path has been removed. Separately, our website now runs on the same platform as First Six itself, and the privacy policy and subprocessor list say so.

What did not change: no student data is involved in either change. Website enquiries are First Six's own marketing data, and the data processing agreement's Schedule 2 is unchanged by the hosting move.

Was this helpful?
Need more help?

The fastest answer is usually one question away.

Contact us
Edit this page on GitHub