A fictional gem glossary carousel can offer buttons as an alternative to dragging. This gives a person a way to reach the same legend entries without holding and moving a pointer. The example here concerns reading a glossary, not playing a game, and does not describe a real Fortune500Gems.com control or confirm website conformance.
What Version B changes
Imagine Version A showing four gem cards in a horizontal carousel that moves only when a person drags the strip. Version B keeps that interaction but adds clearly named “Previous” and “Next” buttons. Selecting “Next” displays the next card; selecting “Previous” returns to the earlier card. The text label, gem name, and explanatory text remain associated with the card being shown.
The check is whether clicking reaches the same card information, not merely whether the strip moves.
Why arrow keys alone are different
Version C might let a person place focus on the carousel and use arrow keys. That can be helpful for keyboard operation, but it is not, by itself, the pointer alternative described for an author-created dragging function. The distinction matters because keyboard access and a non-drag pointer method address different interaction needs.
Compare the card reached by dragging with the card reached after selecting “Next”. Confirm that the heading and its explanation change together. If the button advances the strip but leaves the old description in place, it has not provided equivalent glossary navigation.
What to record in a screen note
Use precise wording: “The fictional carousel includes Previous and Next buttons that replace the need to drag between glossary cards.” Do not write that the arrangement proves compliance or that it improves a real product. It makes no claim about game outcomes or payments.
For the underlying accessibility distinction, see W3C guidance on dragging movements. It explains that an author-created drag function generally needs a single-pointer, non-drag alternative unless an applicable exception exists.