A frame-rate review is usually framed as performance testing, but it can also reveal accessibility barriers. Unstable pacing, camera motion, blur, auto-updating interfaces, unreadable overlays, or a mode that resets accessibility settings may affect whether a player can comfortably configure and use the game. Review the experience around the number, not just the average frames per second.
Define modes and test conditions
List every player-selectable mode, target frame rate, resolution behavior, refresh requirement, synchronization option, platform, display, power mode, and supported accessibility setting. Record the actual build, scene, input method, display path, and measurement tool. Label estimates and unavailable measurements.
Warm the system consistently and collect multiple runs. Review frame time and visible stutter alongside average FPS. Include gameplay, menus, loading transitions, cinematics, overlays, and accessibility settings screens. Test the same representative actions across modes so a difference is attributable to the mode rather than a different scene.
Check motion comfort in every frame-rate mode
Microsoft's visual distractions and motion settings guidance recommends controls for moving, blinking, scrolling, and auto-updating content and for camera effects such as motion blur, shake, bobbing, sensitivity, and field of view. Verify that these controls still work in each frame-rate mode.
Test slow camera turns, rapid turns, sprinting, vehicle motion, weapon effects, screen shake, damage effects, and transitions between gameplay and menus. Ask whether unstable pacing or a lower-performance mode makes text, aiming, navigation, or camera motion harder to tolerate. Provide an immediate way to pause and change settings when a selected mode causes discomfort.
Verify settings are reachable and persistent
The frame-rate selector, display mode, motion controls, and related descriptions need keyboard or controller access, visible focus, narration support where provided, and understandable values. Microsoft's UI navigation guidance recommends accessible pathways to accessibility settings from initial launch.
Confirm that the selected accessibility and performance settings persist after restart, account change, display reconnect, update, and safe-mode recovery as designed. A benchmark mode must not silently replace the player's motion, subtitle, contrast, narration, or input preferences.
Review text, cues, and timing under load
Watch subtitles, captions, tutorials, quick-time prompts, menus, reticles, status indicators, and notification toasts during the heaviest scenes. Confirm that frame drops do not shorten required reading time, skip focus movement, delay input recognition, or cause cues to disappear before the player can respond.
Keep essential information available through more than one sensory channel where the design supports it. Test audio, visual, and haptic cues with each channel reduced or disabled. Do not assume higher FPS automatically fixes inaccessible cue design.
Test controls and assistive paths
Use the supported input methods, including keyboard-only, controller remapping, alternate devices, toggle versus hold options, and reduced rapid-input settings. Check whether frame-rate modes change polling, dead zones, input buffering, menu responsiveness, or perceived timing windows.
Measure from input to visible response when the tools support it, but keep that result separate from frame rate. A smooth average can coexist with delayed input, irregular frame delivery, or network latency. Describe the measurement boundary precisely.
Include failure and recovery scenarios
Test a display that cannot accept the requested refresh rate, a frame-rate target that the hardware cannot sustain, a foreground/background transition, thermal or power constraints, and recovery after a crash. The game should fall back to a usable mode without trapping the player behind an unreadable or inaccessible confirmation dialog.
Preserve a known-good settings file or rollback procedure where appropriate. Avoid flashing comparisons, rapidly alternating modes, or test sequences that could create avoidable discomfort for participants.
Record accessibility outcomes separately from performance
For each mode, record average and variation, frame-time behavior, visible stutter, control response, text readability, cue timing, motion settings, accessibility-setting persistence, test participant context, issue severity, and rollback. Do not turn one person's comfort report into a universal claim.
A frame-rate mode is ready when its requirements are explained, settings are reachable, visual and input behavior remain stable, motion controls work, essential information remains perceivable, failures recover safely, and limitations are disclosed. Performance success does not replace accessibility review, and accessibility review is not a promise that one mode suits every player.
Sources
- Xbox Accessibility Guideline 117: Visual distractions and motion settings — Microsoft Learn
- Xbox Accessibility Guideline 112: UI navigation — Microsoft Learn