Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add visibility: aural #13

Open
ghost opened this issue May 21, 2017 · 6 comments
Open

Add visibility: aural #13

ghost opened this issue May 21, 2017 · 6 comments
Labels

Comments

@ghost
Copy link

ghost commented May 21, 2017

I'm not sure exactly where to place this issue, so here you go. The Web needs a simple way to hide text for screen readers. We've been dealing with hacks for years. WIA-ARIA use is spotty at best. And the newish hidden attribute doesn't serve this purpose.

Let's introduce a new value for visibility, simply call it aural and hide it always from the screen before another 10 years of hacks get added to the Web.

@ghost
Copy link
Author

ghost commented May 21, 2017

@herrernst
Copy link

I would very much like to see such a property!

@herrernst
Copy link

As a side note, the value probably would better be display: at-only or display: assistive, because such content should be available to all assistive technologies (not only screen readers, but also braille displays e.g.) via accessibility APIs (and their accessibility tree).

@patrickhlauke
Copy link
Member

at-only or assistive is probably too specific. what about user agents like alexa or similar? they're not AT per se, but they may want to expose/announce content specifically aimed at aural output.

@herrernst
Copy link

Does Alexa really read web pages based on the visual DOM (sorry, don't know much about it)? IMHO it would be appropriate if such speech agents would use @media speech rules, but as you have discussed in w3c/csswg-drafts#1751, there seems to be no real-world support for it ATM. Other options I can think of would be display: invisible or display: visually-hidden.

Another point to consider: what about .textContent (probably show) and .innerText (probably hide, in contrast to .sr-only)?

@digilou
Copy link
Contributor

digilou commented Sep 16, 2020

APA revisited this today. They will bring to TPAC 2020 to see if progress was made on writing a proposal for this csswg-drafts 560

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants