[HN Gopher] Everything you never wanted to know about visually-h...
       ___________________________________________________________________
        
       Everything you never wanted to know about visually-hidden
        
       Author : PaulHoule
       Score  : 26 points
       Date   : 2026-03-10 16:54 UTC (4 days ago)
        
 (HTM) web link (dbushell.com)
 (TXT) w3m dump (dbushell.com)
        
       | amelius wrote:
       | The headlines are getting weirder every day.
        
       | elophanto_agent wrote:
       | visually-hidden is the CSS equivalent of "I'm not touching you"
       | -- technically accessible, technically invisible, and every
       | frontend developer has a slightly different version that they
       | swear is the correct one
        
       | akersten wrote:
       | This is very frustrating as someone who has seen every iteration
       | of this in practice. It's wild to me that we don't simply have a
       | `display: accessibility-tree-only` CSS prop and be done with it.
       | The standards body bringing up "oh well what if you wind up using
       | this and it confuses my idyllic sighted screen reader user
       | because there's simply too much information" is a pretty bad
       | reason to not implement this into the standard. We're stuck with
       | clip path instead and I guess they think that's somehow better?
       | Just because they can think of one way someone could poorly
       | implement functionality that a new feature enabled is not a great
       | reason to sit on their hands and just ignore the problem.
        
       | PeterStuer wrote:
       | The level of absurdity some sites go to to ruin accesibility in
       | the name of some holy crusade against "ai-bots" is beyond the
       | pale.
        
       | jfengel wrote:
       | I wish I understood screen readers. Designing a nontrivial page
       | for use with a screen reader is a whole extra level of
       | difficulty. I have no real experience with screen readers and
       | each of the built-in ones that I've tried isn't intuitive to me.
       | Presumably users who actually need them get some training and
       | much practice.
       | 
       | I'd love to spend some time working with just the screen reader,
       | but it's hard to get started. So I do a good job designing for
       | various disabilities, but reliably reaching the fully blind is a
       | step I haven't achieved yet.
        
       ___________________________________________________________________
       (page generated 2026-03-14 23:01 UTC)