There's not really a good general solution here, and you might guess in a way that really screws you up. It's easy for the interviewer to tell if the candidate is attempting a "just feed me what I want to hear" strategy, if the candidate has guessed wrong about what I actually want to hear, and now the candidate appears deceitful, a double-whammy. If they have guessed right, though, it's much harder for the interviewer to pick up on it -- which is why for hiring programmers at least it's common (even if rife with its own pitfalls) to do more objective things like asking for a demonstration of basic coding capabilities, because sometimes some people who must really want the job and have Masters degrees and can talk somebody's ear off in a confident enough way to get this far still somehow can't seem to program when asked, the primary activity we need them to do.
Life's not about maximizing the chances of getting a particular job, though. I like ethical policies of being maximally honest, even if you shoot yourself in the foot by revealing you're a bit crazy about homoiconicity or whatever... And generally speaking it's not a terrible guess to assume the interviewer just wants an honest answer primarily even if secondarily the content of the answer isn't what they were hoping for. It's also easy to execute on that guess, since it's usually easy to come off as honest if you're being honest. If the interviewer asks a question that does seem job related (like this accessibility example), honesty is also helpful in that even if your honest answer differs from the interviewer's expected answer, and you don't get hired like you wanted, you might have dodged a bullet by at least surfacing that the difference in opinion or expectations was apparently a big deal there before actually taking the job. Wasteful interviews are wasteful, but it's even more wasteful to take a job, start going through onboarding, and only then you and/or the employer beginning to realize things probably won't work out.
Though if the interviewer asks a loaded question, i.e. one which is well known to be a topic of contention in the industry, it's worth re-evaluating your guess and to respond accordingly. I wouldn't suggest ever outright lying, but the honest, direct answer might not be your friend and as with any adversarial conversation (interviews are not casual chats at a meetup with industry peers, even if they can sometimes feel structurally similar) giving too much information can be detrimental.
Example, the interviewer might toss out "So, tabs or spaces?" Maybe you honestly believe spaces, and maybe you also honestly believe this is something worth flaming about and are ready to go at it if the interviewer dares claim for tabs. You might reveal the basic answer of "Spaces", I wouldn't advise revealing the latter information. Here's an opportunity to guess the intent though, maybe the interviewer just wants to see if you'll try to be funny about the answer rather than answer directly. Ideally the interviewer would guide the interview so that whatever their intention is will be clear.
> "there are no right or wrong answers in this interview."
It's good to tell the candidates something about what your expectations are, that's my whole point! Though I might rework this one a bit. Some personalities would be instantly alarmed by such a phrase... For myself, I'd ignore it and proceed as normal, though part of me would want to ask "So you've already decided on yes/no? Want to regain the hour?"