Users don't usually expect functionality like UI Options on a website. Because it's not an existing convention, how do we construct a recognizable call-to-action for it?
A button named "User Interface Options" is unlikely to be well-understood
A button named "Display Preferences" is more likely to be understood, but doesn't accurately reflect the breadth of options (e.g., audio descriptions, text-to-speech)
Users might not have the vocabulary to articulate what they need (they might not even know what they need). Avoiding technical jargon seems sensible, but how should we label preferences that users don't already have any vocabulary for? (e.g., "audio feedback", "focus highlighting", etc.)
On the one hand, we can expect when users play with options to gain an understanding thru seeing their effects in real-time;
But, will users play with options in the first place if they don't have some expectation of what will happen? (i.e., how many users will explore thru the preferences freely?)