Question: why *CAN'T* we add ARIA directly to CSS? I haz use-cases | @glazou @mollydotcom @fantasai @tabatkins
1
1
@thierrykoblentz @johnfoliot @vick08 @glazou @fantasai @tabatkins ARIA is document layer, full stop. CSS is pres layer. GC is pres layer.
2
1
@mollydotcom When you "present" information visually, you need to encode it semantically as well
1
So @johnfoliot, 1. Presentation is not just visual. 2. Semantics are the duty of the structural layer. Mixing the two is a step backwards
1
1
1
@mollydotcom @johnfoliot surely the argument is flawed. Anything worth making accessible should be in the semantic HTML, not CSS generated.
2
@benmacgowan @mollydotcom consider: .important:before {content:url(exclamation.png);aria-label:"Important";} - now we have attached meaning
2
@johnfoliot @mollydotcom but why should that be generated content rather than an image in the HTML?
1
Replying to @benmacgowan
@benmacgowan @johnfoliot Ben, that's the point. A critical piece of accessibility related information should NEVER be in GC.

Jul 17, 2012 路 6:06 PM UTC

2
Replying to @mholzschlag
@mollydotcom You are right, it should never be there. But it is; and often. Now what?
1
@johnfoliot Teach people best practices. We cannot mix those layers. It would be death to the entire direction we've committed ourselves to.
1
Replying to @mholzschlag
@mollydotcom @johnfoliot agreed. I only see the use of generated content for purely presentation layer items and which add no significance