You shouldn't actually build your entire website in CSS -- it's going to be inaccessible no matter what because CSS isn't really for content.
But it's cool to see what's possible, mostly because learning how to overcome these challenges to use a tool in a way it shouldn't be used often requires you to learn more about how the tool works. That the tool is ill-suited is the point.
Of course, not that there isn't value in you pointing out that CSS content isn't accessible :) -- I have seen developers get tripped up by that in production settings particularly when building things like hover labels, so a reminder is always appreciated.
Recent Firefox doesn't, but good old Opera 9 lets you select the text just fine. (On the other hand, no animation nor background, but maybe that's a reasonable tradeoff.)
Comments
And none of the text is selectable :(
You shouldn't actually build your entire website in CSS -- it's going to be inaccessible no matter what because CSS isn't really for content.
But it's cool to see what's possible, mostly because learning how to overcome these challenges to use a tool in a way it shouldn't be used often requires you to learn more about how the tool works. That the tool is ill-suited is the point.
Of course, not that there isn't value in you pointing out that CSS content isn't accessible :) -- I have seen developers get tripped up by that in production settings particularly when building things like hover labels, so a reminder is always appreciated.
Ah so it's more like a pure css mobile app.
Recent Firefox doesn't, but good old Opera 9 lets you select the text just fine. (On the other hand, no animation nor background, but maybe that's a reasonable tradeoff.)
Browser bug? Seems like it's debatable although the spec leans in the direction of generated content being selectable: https://stackoverflow.com/questions/24385171/is-it-possible-...
Noticed the same. Would be interested to know what the page is like for people who use screen readers. Does the whole page seem blank for them?