I enjoyed this documentary on legendary sound designer and editor Walter Murch. Kinda makes me want to rewatch The Conversation and The Godfather.
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.
Tantek documents the features he wants his posting interface to have.
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.
I found myself needing to open some old Photoshop files recently, but I haven’t had Photoshop installed on my computer for years (not since Adobe moved to the Mafia pricing model). It turns out there’s an online recreation of Photoshop!
I remember when this was literally the example people would give for the limitations of the web: “Well, you can’t build something like Photoshop in the browser…”
Editing is hard because you realize how bad you are. But editing is easy because we’re all better at criticizing than we are at creating.
My essay was garbage. But it was my garbage.
This essay is most definitely not garbage. I like it very much.
This is quite nifty: a fully-featured photo editing tool right in the browser, with no log-in or registration required.
Well, this looks like it could come in handy—no more tedious time in Photoshop trying to select turn a person into a separate layer by hand; this does it for you.
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.
This is an interesting tool: mess around with styles on any site inside Chrome’s dev tools, and then hit a button to have the updated styles saved to a URL (a Gist on Github).
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.
A plug-in that lets multiple people collaborate on the same document in Atom. Could be useful for hackdays and workshops.
This is quite impressive—you edit the audio file by editing the transcript!
Tuukka Ojala is a programmer working on the web. He’s also blind. Here are the tools of his trade.