Steam Deck Verified Autumn 2026 Refresh - What the Refreshed Cert Lane Actually Tests and How Indie Teams Should Prepare

Four Seasons artwork - hero image for the autumn 2026 Steam Deck Verified refresh deep-dive

Why this matters now

Valve announced an expanded Deck Verified cert lane refresh that landed in early autumn 2026, the largest tightening of the rubric since Deck Verified launched in 2022. The refresh is not a redesign of Deck Verified - it is a sharpening - and the failure modes that teams considered "edge cases" before September 2026 are now the default review path.

Three pressures stacked on top of each other forced the refresh:

The Steam Deck OLED 2-year revision and third-party SteamOS handhelds (Lenovo Legion Go S, Asus ROG Ally X SteamOS edition) expanded the verified hardware list past what the original rubric anticipated.
Proton 9.x and 10.x compatibility ranges stabilized differently across DXVK and VKD3D-Proton lanes, exposing games that ran "fine" on older Proton branches but degrade on the autumn 2026 reviewer image.
Player return rates within the first two hours of Deck purchases revealed specific failure clusters that previous Verified rubrics did not screen for, notably resume-from-sleep save discipline and HUD text legibility at the Deck's native 1280×800.

The result: six specific test paths that the autumn 2026 cert lane now exercises that older test plans missed. Teams who passed Deck Verified before September 2026 are not grandfathered - the next patch you submit re-enters the refreshed lane. If your last Deck Verified review was in early 2026 and you have shipped a content patch since, you are due for a revalidation.

This post walks the six changes one by one, with the verification step for each, the indie-team prep plan, and the failure modes most teams will hit. The accompanying tactical drill that exercises this stack inside a single week is the 7-Day Vertical Slice Demo Challenge for Steam Next Fest October 2026. The 48-hour clear-a-fail case study is We Cleared Steam Deck Verified Fail in 48 Hours. If your build still does not have Steam Input wired correctly, start with How to Add Steam Input Correctly in Unity 6.

Who this post is for

Indie teams with a Deck Verified status that predates September 2026.
Indie teams about to submit for Deck Verified for the first time after September 2026.
Steam Deck-only-target indies finalizing a handheld-first design for late 2026 launches.
Anyone who saw "Playable" or "Unsupported" appear on a previously-Verified game's library entry after a recent patch and wants to know why.

What is unchanged - read this before you panic

The autumn 2026 refresh is additive, not a redesign. These pillars remain exactly the same:

The three Deck Verified tiers: Verified, Playable, Unsupported. The criteria for each tier are unchanged at the headline level.
The submission flow in Steamworks Partner Portal. Same form, same depot binding, same beta-branch test path.
The 24-72 hour typical review SLA, with surge times during Next Fest and holiday weeks (now formalized as expected, not exceptional).
Cloud Saves and Family Sharing parity rules.
Achievement parity between Deck and desktop.
The passive-cooler thermal target (no fan ramp ceiling, but no thermal throttling under typical play).

If you only read one paragraph: the rubric did not change. The review depth changed. The reviewer image got tighter Proton ranges, broader controller archetypes, stricter HUD text checks, and a real resume-from-sleep test. Your prep plan does not need to start over; it needs to sharpen.

Change 1 - Controller glyph routing tightened across more archetypes

The single biggest cert-lane change. Before autumn 2026, you could ship a build with the legacy GetGlyphForActionOrigin_Legacy call and the reviewer accepted a generic Xbox glyph for an Xbox Elite or DualSense Edge controller. As of September 2026, that fails.

The refreshed lane checks eight controller archetypes:

Steam Deck (LCD)
Steam Deck (OLED)
Xbox Series controller (baseline)
Xbox Series 2 controller (new archetype)
Xbox Elite Series 2 (new archetype)
PlayStation DualSense
PlayStation DualSense Edge (new archetype)
Third-party SteamOS handhelds with their own glyph maps (Lenovo Legion Go S, ROG Ally X SteamOS)

For each archetype, the reviewer connects the controller (or simulates via Steam Input device emulation) and verifies that the in-game prompt UI shows the correct glyph for that controller specifically. A generic Xbox A button glyph in place of an Xbox Elite ring-paddle prompt is a fail, not a warning.

Migration step:

Replace SteamInput::GetGlyphForActionOrigin_Legacy with SteamInput::GetGlyphPNGForActionOrigin (or GetGlyphSVGForActionOrigin for vector UIs).
Extend the VDF action manifest under controller_base/ to include xbox_series_two_*, xbox_elite_two_*, ps_dualsense_edge, and the new SteamOS-handheld archetype rows.
Subscribe to SteamInputDeviceConnected_t and refresh the glyph cache on connect (the autumn 2026 reviewer image hot-swaps controllers during the test).

Verification step: With Steam Input device emulation enabled, swap between every archetype above and visually confirm each in-game prompt updates within one frame. The reviewer does this exact sequence.

Change 2 - Fullscreen toggling expectations extended to dock + external monitor

Before September 2026, the cert lane checked that Alt+Enter (or your in-game fullscreen toggle) cycled between borderless windowed and exclusive fullscreen on the Deck's native display. Pass.

After September 2026, the cert lane also checks:

Deck-in-dock with an external monitor at 1080p and 1440p outputs.
Surface-area-change handling when the player toggles dock mode mid-session.
HiDPI scaling if the external monitor is HiDPI.

The failure mode the refresh screens for: a game that locks itself to 1280×800 even when docked to a 1440p monitor, or a game that crashes on resolution change events fired by SteamOS when the dock is plugged in or unplugged.

Migration step:

Handle Application.SetResolution (Unity) or equivalent on every OnApplicationFocus(true) event because SteamOS fires focus changes when the dock state changes.
Make sure UI scaling responds to the active resolution rather than hard-coded pixel sizes.
Test the mid-session dock-and-undock sequence at least once before submission.

Verification step: Connect a 1080p external monitor via the dock, start the game, dock and undock five times during a single play session, and confirm no crashes, no UI overflow, and resolution actually changes (not just the swap chain).

Change 3 - Steam Input default action set must exist on the demo branch too

The demo-branch-specific change. Before September 2026, the reviewer accepted that the Steam Input default action set lived in the main depot and assumed the demo depot inherited it.

After September 2026, the reviewer explicitly verifies that the demo depot has its own controller_base/ folder with the VDF action manifest. The most common autumn 2026 rejection class is STEAM_INPUT_DEFAULT_CONFIG_MISSING on the demo branch.

Migration step:

Confirm the VDF action manifest lives in both the main depot's controller_base/ folder and the demo depot's controller_base/ folder.
Re-promote the demo depot from a clean SteamPipe run, with explicit --include-config if your tooling supports it.
Open the Steamworks portal and verify the demo branch shows the green "Steam Input default config detected" indicator under the build's metadata view.

Verification step: Install the demo from the Deck (via your Steamworks reviewer key on the demo branch) on a fresh user, launch, confirm controller prompts work without manually choosing a community config.

This change pairs directly with the planned help-plan item Steam Next Fest October 2026 demo upload rejected missing Steam Input default config metadata fix - watch the help index for that article.

Change 4 - Proton compatibility range narrowed for the reviewer image

Before September 2026, the reviewer image ran a wide Proton range and tolerated games that worked on at least one Proton minor version. After September 2026, the reviewer image runs a narrower range: Proton 10.x stable, with a fallback to Proton 9 LTS only if the developer flags the game as legacy-pinned in the Steamworks Compatibility settings.

The DXVK and VKD3D-Proton lanes tightened around:

VKD3D-Proton for D3D12 games: stricter validation against missing render-pass barriers; some Unreal Engine 5.6/5.7 patterns that produced warnings in Proton 9 now fail outright in Proton 10.
DXVK for D3D11/D3D9 games: tightened around D3DERR_DEVICELOST recovery during resume-from-sleep (which ties to Change 6 below).
Steam Input library version pinned to a 2026.10 release minimum in the reviewer image.

Migration step:

Test your game against Proton Experimental (which previews the reviewer image's compatibility range) before submission.
If you are pinned to an older Proton for cause (anti-cheat compatibility, specific licensed middleware), set the Compatibility settings in Steamworks to declare the pin and document the rationale in your submission notes.
For Unreal Engine projects, audit your custom render passes for missing barriers using RenderDoc's frame capture on the Deck.
For Unity URP/HDRP projects, check that any custom render features handle the depth-copy variant the autumn 2026 reviewer image expects.

Verification step: Use protontricks from the Deck's developer mode to inspect the active Proton prefix during play. Confirm the game does not log vkd3d-proton: validation error or d3d11_device::OpenSharedResource: WARN repeatedly during normal play.

For the broader compatibility picture, see Godot 4.5 Vulkan Validation Errors on Intel iGPU for the Vulkan-side companion treatment (the Deck shares some validation behavior with Intel iGPU lanes).

Change 5 - HUD text legibility minimums tightened at 1280×800

The refreshed lane runs an automated text-legibility check at the Deck's native 1280×800. The check screens for:

HUD body text below 9 pixels x-height at native resolution. Fails.
Subtitle text below 14 pixels at native. Fails unless the game offers an explicit subtitle size scale in accessibility options.
Contrast ratio for HUD text against typical backgrounds below 4.5:1 (the WCAG AA threshold). Warns; combined with low x-height, fails.
Critical UI prompts (interact prompts, store currency, health/ammo counters) below 12 pixels x-height. Fails.

The reviewer does not run a manual line-by-line audit; the check is a screenshot OCR pass plus targeted human review of any flagged frames. Once you fail a frame, the reviewer manually re-checks the surrounding UI.

Migration step:

Run the Pixel Art UI Readability 2026 audit - the rules transfer directly to Deck native resolution checks.
Add a Settings → Accessibility → "Subtitle Size" scale (1.0x, 1.5x, 2.0x). This single change alone protects against the subtitle-size fail class.
Audit every HUD element at 100% scaling in 1280×800 mode in your Unity Game view or Godot editor - then re-audit at the actual Deck.
For pixel art games, audit your scale factor: integer scaling (2x, 3x) often produces 7-pixel x-heights at native that fail the 9-pixel minimum.

Verification step: Take a screenshot of every screen in the game on the Deck. Open each in any image editor. Measure the x-height of the smallest readable text. Verify it is at least 9 pixels for HUD body and 14 pixels for subtitles.

Change 6 - Resume-from-sleep save discipline now actively tested

The autumn 2026 reviewer actively suspends and wakes the Deck during a play session. Before September 2026, this was a recommended but not actively-tested check. After September 2026, the reviewer:

Starts the game.
Plays for 5-15 minutes through normal gameplay.
Presses the power button to suspend the Deck.
Waits 10-30 minutes.
Wakes the Deck.
Resumes the game without manual intervention.

The failure modes screened for:

Lost session state. If the game did not save the active state to disk before suspension (or did not restore it on wake), the reviewer's progress is gone. Fail.
Network handshake reset crashes. Games that hold a persistent network connection without a graceful resume path crash on the second action after wake. Fail.
Audio device reacquisition. Games that silently lose audio after wake. Warn; if audio does not return after a scene change, fail.
Save corruption. If the suspend happened mid-save and the game cannot recover the previous save on wake, fail.

Migration step:

Hook Application.focusChanged (Unity) or notification(NOTIFICATION_APPLICATION_FOCUS_OUT/IN) (Godot) and treat the focus-loss event as a save trigger.
Add a robust autosave-on-focus-loss pattern: save to disk, flush, then optionally pause.
On focus regain, verify the save is intact (a quick checksum) before resuming. If corrupted, restore from the previous snapshot rather than continuing on top of a broken save.
Test the 20-minute suspend cycle at least three times during pre-submission QA.

Verification step: During QA, suspend the Deck mid-gameplay, wait 30 minutes, wake, and continue playing. The game should remember your exact position. Do this with a save mid-action (mid-attack, mid-dialogue, mid-menu) to stress the save serialization.

This pairs with Reliable Save Migration Unity Godot for the broader save-discipline framework.

How to prepare in 5-7 days

If you are submitting or revalidating for Deck Verified within the next two weeks, here is the focused prep plan:

Day 1 - Audit current state. Run the six change checks above against your current build. Score each as PASS / FAIL / NEEDS WORK. Write the audit to a deck-verified-2026-autumn-audit.md file in your repo.

Day 2 - Glyph migration. Migrate to GetGlyphPNGForActionOrigin (or SVG variant). Extend the VDF manifest. Test with at least three controller archetypes (Xbox Series, DualSense, Steam Deck native).

Day 3 - Dock + external monitor pass. Wire dock-state handling, test mid-session dock-and-undock five times, verify resolution change events do not crash.

Day 4 - Demo branch parity + Proton compatibility. Confirm demo depot has its own controller_base/. Re-promote the depot. Test the game against Proton Experimental on the Deck.

Day 5 - Text legibility. Audit HUD x-height at native 1280×800. Add subtitle-size scale to Accessibility settings. Re-screenshot.

Day 6 - Resume-from-sleep. Add autosave-on-focus-loss. Test the 20-minute suspend cycle three times. Verify save integrity check on resume.

Day 7 - End-to-end Deck QA. Play the full demo end-to-end on a Deck (or a Deck reviewer image via SteamOS). Document any remaining issues. Submit to Deck Verified review.

If you are a 1-2 person team, compress Days 2-3 and Days 4-5 into single calendar days where you can. Skip nothing; the six checks are independent failure modes.

Common mistakes most teams will make

Assuming previously-Verified status carries forward. It doesn't. The next patch re-enters the refreshed lane.
Migrating to GetGlyphPNGForActionOrigin but forgetting the VDF manifest extension. The new call returns a generic glyph if the action manifest does not declare the new archetypes.
Testing only on a developer Deck with admin user. The reviewer runs as a fresh user; admin Decks bypass some default-config detection. Use the Deck in "fresh user" mode for final QA.
Setting Compatibility to "force Proton 9" without declaring the legacy pin in submission notes. The autumn 2026 reviewer treats unflagged Proton pins as suspicious.
Skipping the resume-from-sleep test because "we don't think anyone sleeps the Deck mid-game." Players sleep the Deck constantly. The reviewer's bias matches the average player's behavior, not the developer's.
Adding subtitle size scale but defaulting it to a still-too-small size. Default to 1.0x where 1.0x is the 14-pixel minimum, not the legacy 9-pixel size that you might be inheriting from the desktop UI.
Running the entire week from one Deck. Borrow or rent a second unit if possible. The cross-Deck variance (battery age, screen calibration drift, OS minor version) catches edge cases a single unit hides.

Pro tips for the cert reviewer's perspective

The reviewer is not your adversary; they are a tired professional running ten reviews per shift. The way to pass quickly is to make the reviewer's job easy:

Pre-mint the audit file. Attach your deck-verified-2026-autumn-audit.md to the submission notes. Reviewers love evidence they can scan.
Show the screenshot grid. A 3×2 grid of screenshots demonstrating all six change checks (one per change) reduces the reviewer's verification time and lifts your perceived professionalism.
Declare known limitations explicitly. "Game does not support external monitor at 1440p; will degrade gracefully" is better than silence. Declared limitations get accepted; surprises get fail-flagged.
Pin a developer test build for the reviewer. A debug build that prints overlay timestamps and reports save events to a HUD ribbon helps the reviewer confirm the resume-from-sleep behavior in 30 seconds rather than 5 minutes.
Submit Monday morning UTC. The autumn 2026 review queue surge is heaviest Wednesday-Friday; Monday submissions get reviewed faster on average.
Watch the Steamworks portal email queue. Reviewer questions can land mid-review; a same-day reply often unblocks the review before the SLA timer expires.
If you fail, request the verbatim reviewer notes rather than a paraphrase. The notes are the canonical record of which of the six change checks fired.

Steam Deck 2 - does this refresh apply?

The Steam Deck 2 is rumored but not officially confirmed as of May 2026; Valve has signaled a refresh of the OLED branding but a "Deck 2" SKU has not been dated. The autumn 2026 cert refresh is forward-looking and explicitly anticipates additional handheld archetypes. The reviewer image's controller archetype list and HUD legibility checks were designed assuming new SteamOS handhelds will land in 2026-2027.

Practically, this means: prep for the autumn 2026 refresh now; the Deck 2 will not invalidate the prep. If anything, the prep will hold across a Deck 2 launch because the cert lane is now archetype-agnostic.

For the broader Deck 2 hardware speculation context, see Steam Deck 2 Handheld Dev - What We Know 2026.

Decision tree - refresh now or wait?

If any of the following are true, refresh now:

You plan to ship a content patch in the next 8 weeks. The patch re-enters the refreshed lane regardless.
You are within 8 weeks of a Steam Next Fest or other festival submission window.
Your last Deck Verified review was in early 2026 or earlier.
You have shifted controller support significantly since your last review (added new controller types, changed action sets).
You changed your save format or persistence layer in the last 6 months.

If none of the above are true and you are not planning a near-term patch, you can defer the refresh prep to your next planned release cycle - but allocate a 5-7 day prep slot at the start of that cycle. Do not bolt the prep on at the end; the six change checks are independent and need their own measurement and verification each.

Key takeaways

The autumn 2026 refresh is additive, not a redesign. The rubric did not change; review depth did.
Six change checks now run on every submission: controller glyph routing, dock + external monitor, demo-branch Steam Input default config, Proton compatibility ranges, HUD legibility at 1280×800, and resume-from-sleep save discipline.
GetGlyphForActionOrigin_Legacy is now a fail in the refreshed lane. Migrate to GetGlyphPNGForActionOrigin and extend the VDF action manifest with xbox_series_two_*, xbox_elite_two_*, ps_dualsense_edge, and SteamOS-handheld archetype rows.
Demo depots need their own controller_base/. The STEAM_INPUT_DEFAULT_CONFIG_MISSING rejection class on demo branches is the dominant October 2026 surprise.
The reviewer image runs Proton 10.x stable with a Proton 9 LTS fallback only if legacy-pinned. Test against Proton Experimental before submission.
HUD body text minimum is 9 pixels x-height; subtitles 14 pixels. Add a Subtitle Size scale to Accessibility settings.
Resume-from-sleep is actively tested. Autosave-on-focus-loss + save integrity check on focus regain is the canonical pattern.
Previously-Verified status does not carry forward. The next patch you submit re-enters the refreshed lane.
5-7 day prep plan: audit Day 1, glyph migration Day 2, dock pass Day 3, demo branch + Proton Day 4, text legibility Day 5, resume-from-sleep Day 6, end-to-end Deck QA + submit Day 7.
Decision tree: refresh now if a patch is within 8 weeks, a festival is within 8 weeks, your last review was early 2026 or earlier, controller support changed, or save format changed. Otherwise defer to next release cycle with a dedicated prep slot.

FAQ

1. We passed Deck Verified in March 2026. Do we need to do anything? If you have not shipped a content patch since March, your existing Verified status holds for the moment. Your next patch submission re-enters the refreshed lane, so plan the 5-7 day prep into your next release cycle. If you have already shipped a patch since March, you may have already entered the refreshed lane silently - check your Steamworks Partner Portal for any Deck Verified status changes.

2. We are Steam Deck-only target. Should we still test Xbox Elite and DualSense glyphs? Yes. The reviewer connects external controllers via the Deck's USB-C port and Bluetooth, and the controller-glyph check runs against the full archetype list regardless of your "primary" platform. A Deck-target game that fails the Xbox Elite glyph check still fails Deck Verified.

3. Our demo branch passes Steam Input but the main branch failed. Is that normal? No - that pattern usually means your main branch is missing the new controller archetypes in its VDF action manifest while the demo branch was rebuilt more recently. Extend both manifests; re-promote both depots.

4. Can we use community Steam Input configs as a fallback? The reviewer specifically tests with no community config. Your game must work with the developer-provided default. Community configs are a player-side feature, not a developer's submission fallback.

5. How much of the 5-7 day prep can we automate? Glyph migration (Change 1), demo branch VDF parity (Change 3), and Proton testing (Change 4) can be partially automated via CI checks. Dock + monitor (Change 2), HUD legibility (Change 5), and resume-from-sleep (Change 6) require physical-hardware QA on a Deck. Automate what you can; budget Deck time for the rest.

Why this matters now

Who this post is for

What is unchanged - read this before you panic

Change 1 - Controller glyph routing tightened across more archetypes

Change 2 - Fullscreen toggling expectations extended to dock + external monitor

Change 3 - Steam Input default action set must exist on the demo branch too

Change 4 - Proton compatibility range narrowed for the reviewer image

Change 5 - HUD text legibility minimums tightened at 1280×800

Change 6 - Resume-from-sleep save discipline now actively tested

How to prepare in 5-7 days

Common mistakes most teams will make

Pro tips for the cert reviewer's perspective

Steam Deck 2 - does this refresh apply?

Decision tree - refresh now or wait?

Key takeaways

FAQ

Related reading