Home › Per GAG (Advanced), implementing SCREEN READER s…
Per GAG (Advanced), implementing SCREEN READER support for game UI is challenging primarily because of which?
AScreen readers cannot read more than 200 words/minute
BScreen readers require a console-only firmware build
CScreen readers always conflict with audio mixing
DCustom UI is not exposed to OS accessibility APIs by default
Answer & Solution
Correct answer: D. Custom UI is not exposed to OS accessibility APIs by default
GAG Advanced + Brandon Cole (Last of Us 2 accessibility review): game UIs use custom rendering. Engine must expose roles + labels via UI Automation / NSAccessibility / TalkBack APIs.
Related questions
Per CELIA HODENT (cognitive UX) and GAG, GOOD COGNITIVE accessibility includes which desigPer Game Accessibility Guidelines, AIM ASSIST as an accessibility feature differs from typPer Last of Us Part II + Forza Horizon 5 accessibility postmortems, AUDIO CUES that mirrorPer GAG (Basic), text in game UI should ideally be RESIZABLE to do which?Per GAG + W3C WCAG, AVOIDING FLASHING content at certain rates aims to prevent which medicPer GAG + Xbox Adaptive Controller docs, REMAPPABLE CONTROLS at the system or game level aPer GAG + Microsoft Inclusive Design Toolkit, the SITUATIONAL DISABILITY frame argues whicPer W3C WCAG 2.1 + GAG, the minimum CONTRAST RATIO for normal-size text against its backgr