CSS only truly exists in a browser. As soon as we start writing CSS outside of the browser, we rely on guesses and memorization and an intimate understanding of the rules. A text editor will never be able to provide as much information as a browser can.
I reckon a lot of websites have bad accessibility not because folks don’t care, but because they don’t know there’s an issue in the first place.
The headline is begging the question (I don’t think accessible websites are so hard to build), but I agree with Robin’s idea:
What if our text editors caught accessibility issues and showed them to us during development?
This is something that Hidde has been talking about recently too, looking at content management systems.
This is quite nifty: a fully-featured photo editing tool right in the browser, with no log-in or registration required.
Remember when I said that if we want to see CSS exclusions implemented in browsers, we need to make some noise?
Well, Rachel is taking names, so if you’ve got a use-case, let her know.
But despair not—Rachel points to a potential solution. I saw potential solution, because if we want to see this implemented in browsers, we need to make some noise.
If you must add a rich text editor to an interface, this open source offering from Basecamp looks good.
Is it a graphic design tool? Is it a text editor? Is it just good fun?
This is the dumbest publishing platform on the web.
Write something, hit publish, and it’s live.
This is impressive—a fully featured graphics app for creating SVGS right in your browser.
Tuukka Ojala is a programmer working on the web. He’s also blind. Here are the tools of his trade.
Lea has also written an introductory article on Smashing Mag.
Incredibly impressive work from the CodePen team—you can now edit entire projects in your web browser …and then deploy them to a live site!
This looks like an interesting little Markdown editor. I think I’ll take it for a spin.
It’s a bit like CodePen but it shows the whole HTML document, which makes it particularly useful for teaching front-end development to beginners (ideal for Codebar!).
CodePen for snippets; Thimble for pages.
This looks like it could be a very nifty tool to have at your disposal while coding. I like that it’s editor-agnostic.
This could pair up nicely with the most dangerous writing app.
I really, really want to like this article—it’s chock full of confirmation bias for me. But it’s so badly-written …I mean like, just the worst.
Here’s an actual sentence:
So with a capable, HTML-based platform and a well-designed program that makes good use of CSS, one site could support phones, tablets, PCs, and just about anything else with one site.
So, yeah, I’m still linking to it, but instead of it being for the content, it’s because I want to lament the dreadful state of technology writing.
A useful text editor that analyses your writing for excess verbiage and sloppy construction. It helps you process your words, as it were.
From the lovely people behind Editorially comes STET:
A Writers’ Journal on Culture & Technology