That horizontal rule is styled in my style sheet to look like a bunch of cute birds on a wire. The horizontal rule above that specific paragraph was sort of as a “live demo” for the ideas and code discussed in the article. The birds-on-a-wire illustration above this very paragraph is a styled element. In fact, if you haven’t seen it before, then you might have just done that. If you’re a frequent reader of this blog, then you’ve most likely already seen what a horizontal rule looks like on here. In my previous article about creating creative yet accessible horizontal rules, I discussed how I created the birds-on-a-wire horizontal rule style that I use on this Web site.Īfter the article’s introduction was a horizontal rule, and a paragraph that read: If your idea requires CSS to visualize, provide a markup-only alternative. The more we think about the Web in layers, the more robust experiences we can design.ĭesigning for reading, there are a few things we can learn and do to improve our users’ reading experience ( and other users’ experiences as well!): 1. The more I consume content in reading apps, the more I am reminded of the importance and the power of progressive enhancement as a strategy to create resilient and malleable experiences that work for everyone, regardless of how they choose to consume our content. So a question I think we should constantly be asking ourselves is: Is our content still understandable without CSS? Or are we relying too much on visual styles to put ideas across? Does the HTML layer alone provide a decent and sufficient experience to our users? Is our CSS truly the enhancement it is meant to be, or are we relying too much on our own preferences rather than our users’ to communicate our ideas? Reader modes and Forced Color modes are two common environments where content is typically stripped of our CSS. My content-the HTML markup-though, defines your experience and can either make it or break it. In either case, the visual style enhancements I have applied to the content don’t really matter much anymore. You might be reading this very blog post in a reading app right now, or maybe even listening to it being read out loud to you. And unless we always keep that in mind, we risk creating incomplete or even broken experiences for users of those technologies or tools. Many apps, tools, and environments that people use to browse the Web strip our content of our CSS and apply their own styles to it. Our content will not always look the way we expect it or want it to. Keep the core experience clutter- and distraction-free: Hide non-core content by default and show it with CSS when it’s OK to do so. Keep content where it belongs: in the markup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |