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

Read this thread and @scottaohara's article https://www.scottohara.me/blog/2023/03/21/visually-hidden-hack.html.

I agree with most of the points — it's better to fix specific issues rather than adding a hack to the specification.

However, there are cases where `visually-hidden` is used today and aren't fix in future specifications. For example, headings that don't fit into the design are often visually hidden, and the same goes for form elements without a label. I like to create quality websites, but as a developer, I don't have the final say on how the product will look. If the designer and client decide that a section shouldn't have a heading or a form element shouldn't have a label, I implement them using `visually-hidden`.

What solution do you see as better than the standard display: `visually-hidden` for addressing designs without headings or form elements without labels?

-- 
GitHub Notification of comment by alkorlos
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/560#issuecomment-2338521692 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 16:09:01 UTC