Re: [csswg-drafts] [css-display] create a display property value for visually hiding an element while making it available for AT (#560)

form controls w/out a label sounds like an aria-label use case.  so nothing really to discuss there.  (re: mention of translation issue as to why people advocate the hack - fix the issue, don't enshrine the hack).

headings that don't exist in the design sounds like a use case for standardizing a feature to mitigating poor design - and that seems wrong to me.

Or, the heading isn't actually necessary and properly labeling landmark containers might be the right solution - if the UI somehow makes it clear the purpose of the section of the content.  hard to tell exactly we're both imagining the same scenario - but having come across many scenarios that seem like they'd fit this - that's my take at least until given more information to determine otherwise.

again, standardizing what might work for visually hiding a heading (the standard ruleset that essentially creates an invisible 1x1px container) would be rubbish to use on a visually hidden control that may or may not need to remain visually hidden when focused (button, checkbox, etc.) for the reasons i've already written about.

since there are a variety of ways one should/could be visually hiding content, i continue to fail to see a way this can get standardized that doesn't require it essentially boil down to only handling the position absolute, opacity 0 aspects of the classic ruleset... 

or, if something does get standardized that handles more than that, then a bunch of usage caveats need to be introduced, and then people will complain the thing they need to do isn't a single property for them to declare.


i still question why some instances of the big visually hidden ruleset can't just be written as the following (so long as people don't need to handle legacy browser support - which, any new standardized property wouldn't be useful for anyway...so...)
```
.example:not(:focus) {   /* remove :not(:focus) if needed */
 scale: 0;
 position: absolute;
}
```

other instances of needing to visually hide something but still having it discoverable if searching by touch, or screen readers that announce what's being hovered, then something like the below would be more appropriate.

.example2 {   
 opacity: 0;
 position: absolute;
  /* it would not always be appropriate - if at all - to show on hover/focus.  e.g., visually hidden controls
      replaced by more robust design controls would not be expected to unhide.  but other controls that
      are meant to be hidden by default but overlay other content would become full opacity on hover/focus.
}




-- 
GitHub Notification of comment by scottaohara
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/560#issuecomment-2338720687 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 9 September 2024 17:48:00 UTC