Most releases lead with a headline feature. This one leads with a principle. We spent this cycle making QuickBox Pro easier to actually use - easier to read, easier to drive from the keyboard, and easier to run from the terminal if that is where you live. Accessibility is not a checkbox at the end of a project for us. It is the shape of the whole release. Two features ride along with it that we think you will like on their own, but the thread running through everything is the same: the dashboard, and the qb command behind it, should be comfortable for everyone who touches them.
Accessibility across the dashboard
If you have ever squinted at a faint label, tabbed into a control and lost track of where you were, or hit Enter a half-second too fast on a confirm box, this release is for you. We went through the dashboard surface by surface and fixed the things that quietly make software harder to use.
Text you can actually read. We raised text contrast to the readable floor across the board. The muted labels, the placeholder text in inputs, the small print on cards, and - this one matters - the red danger text and the accent text that were the hardest to read all now meet the standard contrast ratio for normal text. Nothing important is a faint gray whisper anymore.
Keyboard-visible focus, everywhere. Every interactive element now shows a clear focus ring when you reach it with the keyboard, including the close buttons on dialogs and popovers that used to swallow focus silently. You can tab through a page and always know exactly where you are. There is a skip-to-content link at the very top of every page, so keyboard and screen-reader users can jump straight past the navigation to the thing they came for.
Confirms that cannot bite you. Every confirm dialog now opens with focus on the safe choice, the Cancel button, not the action. So if you open a "delete this?" box and your finger is already on Enter, nothing destructive fires. You have to deliberately move to the confirm. Small change, real peace of mind.
Names for screen readers. The icon-only controls that drive your apps - start, stop, restart, expand - now carry proper accessible names, so a screen reader announces what each button does instead of reading a blank. The settings section headers and their master toggles are fully keyboard-operable too, so you can open a section and flip its main switch without a mouse.
None of this is flashy, and that is the point. It is the kind of work you only notice when it is missing. If you want the specifics, the Accessibility docs lay out exactly what changed.
Search that takes you straight there
The other thing you will feel every day is search. Press Cmd or Ctrl and K from anywhere in the dashboard and a search box drops down. Type a few letters and it finds what you are after - a page, a setting, a single control buried a few sections deep - and it reaches across the whole dashboard now, not just the top-level pages.
Two things make it genuinely quick. First, every result tells you where it actually lives: results group under their true page, so a user setting shows up under "User Management" or "General Settings" instead of a vague "Settings", and each one carries a one-line description of what it does. Second, and this is the part we are proud of, picking a result does not just drop you at the top of a page and leave you to scroll. It takes you straight to the exact section - whether that section is on the page you are already looking at or clear across the dashboard.
It is built to be driven without a mouse: open it, type, arrow through the results, press Enter to go. It respects your reduced-motion setting, so if you have told your system to ease off on animation the jump is instant rather than a long scroll. And you only ever see what your account can reach - results on admin-only or feature-gated pages simply do not appear for someone who cannot open them.
Application Control, rebuilt
The App Dashboard is where you actually run your software, and its Application Control view got the most visible share of this work. This is the default view when you open the dashboard - the list of your installed apps, each one a row you expand for status and the service controls.
Every row now reads cleanly, the status is unmistakable, and the start, stop, and restart controls announce themselves properly to assistive tech. On a phone the whole layout changes shape: instead of a wide table squeezing itself onto a small screen, each app becomes a proper touch card with the controls sized for a thumb. Names and buttons stop overlapping, and nothing gets cut off at the edge.
If you want the full tour of what the App Dashboard can do - installing from the catalog, service control, config editing, backups, and live logs - it is all written up in the App Management docs.
The full qb menu, for people who live in the terminal
Accessibility is not only about the browser. A large part of our community runs everything over SSH, and for years the qb command asked you to remember flags and dig through --help. Not anymore.
Run qb with no arguments and you now get a full interactive menu. It is the whole CLI, laid out in front of you, no memorizing required.
There are nine categories - Software, Updates, Manage, Fix, System, Clean, SSL and DNS, Users, and Support - and you only ever see the ones your account is allowed to touch. Pick one and it opens to that category's own list of actions.
The best part is how it walks you through a command. Pick an action and it prompts you for exactly what it needs: choose the target user from a list, then pick which of that user's installed apps, then the operation, all as real selectable lists instead of arguments you have to get right the first time. Anything destructive, like a database restore or a software rollback, asks you to confirm before it runs. It is gated by role the whole way, so a regular user only ever drives their own apps, and every label is translated across all seven supported languages.
The System category is a highlight on its own: it pulls live dashboard data straight into the terminal. System telemetry - CPU, memory, and history - and streaming analytics like top titles, top users, devices, and geography, all rendered as clean aligned tables right there in your SSH session.
This is the initial launch of the menu. It already covers the bulk of the CLI, and we will keep porting commands in and extending it every release. The per-command details still live in the CLI reference docs if you want the flag form of anything you find in the menu, and there is a full walkthrough of the menu itself in the Interactive Menu docs.
Delete Protection
One more thing shipped in this release, and it fixes a problem that has bitten real servers. Deleting a very large file - a fifty gigabyte usenet download, a big media file - could pin a CPU deep in the kernel and make the whole box unreachable until a hard reboot. Delete Protection paces those large deletes so your server stays responsive the entire time. The file still deletes. It just does not spike the machine.
It is opt-in and off by default. You turn it on with the Delete Protection switch under Settings > General > Feature Flags. Flipping that switch does two things: it starts protecting your detected media apps and download clients, and it reveals the Delete Protection page in the System menu.
On that page you get the controls to shape it. A server-wide protection master switch, a live "large deletes safely handled" counter so you can see it working, a per-app on and off, and a per-app size threshold. That last one matters: a heavy deleter like SABnzbd and a lighter app can each carry their own floor, so protection kicks in at the right size for each. It covers the media servers - Emby, Plex, Jellyfin, and the *arrs - and the download clients - SABnzbd, NZBGet, and the torrent clients.
Prefer the terminal? It is all there too, under Manage in the new qb menu, or as qb manage delete-safety on the command line. There is a full write-up in the Delete Protection docs, including a section on choosing a threshold for your workload, and a shorter troubleshooting guide if a big delete ever caught you off guard before you turned it on.
Where this goes next
This release sets a bar we intend to hold. Every new page, every new control, and every command we bring into the menu gets the same treatment from here: readable, reachable from the keyboard, and safe to drive whether you are in the browser or the terminal. If something still reads too faint, traps your focus, or reads wrong to a screen reader, tell us. That feedback is exactly how this release happened, and it is how the next one gets better.