Desktop, mobile and accessible interaction sweep
Read every panel and finish representative forms on actual supported clients.
Prerequisites: the tester’s actual desktop browser, mobile browser and Discord clients, plus a character with at least one completed activity. Run the same scenario on each available client and record which ones were actually observed. Automated Chromium alone is not this human test.
Step by step
Tick a step after observing the expected result. Saved on this device only.
01Record the client setup
Note the game build, client/application version, operating system, viewport or device size, input method and chosen test path.
A later reviewer can distinguish browser, Discord desktop and Discord mobile evidence.
02Open all game sections
Visit Overview, Explore, Professions, Workshop, Character & builds, Encounters, Journal, Leads & approaches, Market & cargo, Companions, Guild & facilities, Campaigns and Rules & registry in the browser. Open each /play group in Discord.
No empty error screen or script exception appears. Empty inventories and absent encounters have readable empty states.
03Search and page a large catalogue
In /play select a large recipe or action catalogue, search for the ration recipe, move between result pages and continue the form. In the browser search Manufacturing.
Selected values remain correct through search and paging; long labels are still distinguishable.
04Use keyboard and text zoom
On desktop navigate menus and a review dialog using keyboard only, inspect focus visibility, press Escape to dismiss an uncommitted dialog, and try enlarged text/200 percent browser zoom.
Essential controls remain reachable and labels readable. Record actual focus loss, clipping or inaccessible fields as failures rather than assuming support.
05Check mobile layout and form recovery
On a narrow device open Workshop, Character & builds, Campaigns and Leads. Open a form, rotate or resize if supported, cancel it, then reopen.
The main document does not require unintended horizontal scrolling; chosen fields and errors remain usable.
06Measure ordinary interactions
Execute a local Visit and a real work review/commit on each Discord client. Time acknowledgment, result display and refresh behavior.
Record actual latency and failures. No unmeasured performance target is claimed by this guide.
07Reconnect and compare
Close and reopen each client, then inspect the same completed activity or lead.
Character identity and recorded outcomes agree across supported clients and sessions.