In a hypothetical text-only gem screen, a rotation prompt can hide the help a reader needs. Imagine a phone fixed in portrait mode showing a gem glossary. The page asks the reader to “rotate to landscape”, while the glossary is covered by that prompt. Assess the help text, not the actual game’s orientation needs.
What the prompt changes
Suppose the prompt hides a glossary definition after its first line. The reader cannot compare complete entries. A mounted-device user may not be able to rotate the phone easily. Therefore, a portrait view that wraps the same glossary into narrower lines is a useful comparison: it preserves access to the explanation without assuming that landscape is available.
Separate the authored restriction from the phone lock
There are two different causes to identify. An authored restriction is a page or interface that demands one orientation. A device orientation lock is a setting or condition on the phone that prevents rotation. They should not be treated as the same fault, and one screenshot cannot establish which caused the prompt. The relevant accessibility principle is that viewing and operation should not be limited to one orientation unless that orientation is essential. See the W3C explanation of orientation accessibility.
How to compare the help views
Hypothetical check: view the fictional gem glossary in portrait and then in landscape only if rotation is possible. In portrait, check whether the heading, complete definition, navigation labels, and any return control remain available by wrapping or scrolling vertically. In landscape, check whether the prompt disappears and whether the same information is still present. If landscape reveals more content but portrait hides the explanation behind a forced prompt, the prompt is the barrier to help reading.
This conclusion is limited to the help interface. It does not decide whether a game’s orientation is essential, assess every screen, or show that Fortune500Gems.com has such a control or has passed any conformance test.