@Anneke @mahryekuh Oh I see. Yeah that would work, but it's unnecessary -- since width and height are both defined the same, it doesn't actually matter which way round their axes flow. @matuzo

@mahryekuh Which logical properties are you using for that? @matuzo

@mahryekuh No, in fact we shouldn't ever use the offset method. See: https://www.tpgi.com/the-anatomy-of-visually-hidden/#position @matuzo

@jupiter_rowland Yeah it would be making stuff up, but I mean (literally and figuratively speaking) -- all stuff is made up.

Does it matter if a description only amounts to "what if", if the alternative is no description at all?

The underlying question is about what might be useful for this group of users, but it seems to me that's slightly at odds with a desire for strict empirical accuracy.

So maybe the question is -- what's more important?

@jupiter_rowland Can you imagine what unreal surfaces would feel like? For example, if it’s shiny or rough or looks plasticky, you could mentally conceive of what it might feel like, and then describe that.

You can make it clear in descriptions that you’re talking about virtual content and so the descriptions are speculative, and that would still be of value to a reader who otherwise gets nothing they can relate to.