Some of you might remember that a good while back, I started looking into, and using, @classicpress for a personal blog instead of WordPress. The main reason was, and still is, that I am put off by Gutenberg and the bloat that comes with it. Inconsistent keyboard behaviour, inconsistent screen reader exposure, and the general slowness that is inherent to such web-based applications that run almost entirely in the browser. I contributed to that project for a while, but essentially didn't really see it go anywhere useful, despite some very talented people from the accessibility community trying to contribute.
ClassicPress is, in essence, WordPress without the block editor. It is a fork of a recent WordPress version, stripped of all that is the block editor and related components. Moreover, there is on-going work to minimize the footprint by reducing reliance on other, sometimes even no longer maintained, JavaScript libraries such as JQuery. Much of the logic is moved back to PHP, or where there JavaScript is needed, is using vanilla JavaScript. Just the other day, the site customizer was rewritten to stop its reliance on these JS libraries. This is now in a nightly build, and on a test installation, works really well. All in all, the admin backend is really fast nowadays. It reminds me of the old WordPress days where you could quickly move through the admin using a screen reader because everything was behaving like a website should
At the same time, polyfills are rewritten in HTML 5 with since long supported and accessible elements instead of relying on custom JS to simulate interactions for keyboard and screen readers. Also, a huge load of WordPress plugins work with ClassicPress. Essentially all plugins that don't rely on blocks should just work. Same goes for themes that don't rely on block functionality.
They also have a plugin for WordPress that allows to switch to ClassicPress. It runs a series of checks to make sure plugins that are currently installed still work afterwards, and makes suggestions for modifications to the current install to ensure a smooth transition. Once everything checks out, the current WordPress installation is replaced with ClassicPress. Of course, all suggestions to make backups beforehand apply.
I’m currently in the process of setting up a new blog where I will resume blogging regularly in English. And it'll run on ClassicPress. And the greatest: Ulysses, my favorite writing tool on the Mac, works with ClassicPress, too. You just add a self-hosted WordPress and point it at your ClassicPress install. It'll work, including an app specific password, just like that. Lovely! Stay tuned for more info here.
Jason J.G. White
in reply to Marco Zehe • • •Jakob Rosin
in reply to Marco Zehe • • •Great episode, thank you very much.
My biggest issue is audio management. While this is fantastic on the Mac side, it gets very complex when you throw in virtual machines. Virtual machines are pretty much non-negotiable if you need to work with Microsoft Office, which I do every day. If I want to present something on PowerPoint, I would need to do this on the Windows side. Most virtualization software sees just one audio device, so this means now I cannot distinguish between NVDA audio and the PowerPoint audio and switch between those two easily.
For example, if I want to show a live demo of a website with NVDA, I couldn't toggle the sound output because it gets handled by the Mac side and sent through one channel only. I realize this is probably a very edge case situation, but this is one of the biggest issues I'm having with Mac and its accessibility. I cannot use native office apps properly, and managing audio between the Windows side and the Mac side is a very complex one. Sure, I could throw in small external sound cards and do the management via this, but this adds too much complexity for my taste for managing live professional presentation situations. With Windows, I can just walk up with my laptop, plug in the HDMI, and get HDMI out as a separate audio device, which I can then use to choose either the System Audio or the NVDA Audio.
Chris Cooke
in reply to Jakob Rosin • • •Marco Zehe
in reply to Jakob Rosin • • •