A11y Features of WordPress and Wix
WordPress
WordPress’ editor isn’t bad, in all honesty. It’s comparable to our version of CKE in what it can do and the kinds of content it can produce. It has a bit more than CKE in that it has font formatting options whereas CKE strips those out so as to have the focus on a11y. That said, WordPress’ editor offers NO help on a11y authoring, and barely any emphasis on headings or structural markup. While this is essentially the norm, this is what we aim to change. They get points for having the title be its own entity. A bonus for WordPress is the ability to edit with a visual editor or an HTML editor. The HTML editor would allow someone with certain knowhow to add extra markup that may be useful in certain situations (ARIA, etc.) though it’s hard to tell a) if that’d be necessary or b) conflict with the general backend of WordPress. WordPress also encourages (though perhaps not explicitly) alt text on images.
Wix
Wix’s editor is a fair bit worse than WordPress’. This is due to the lack of HTML editing directly available – there’s no advanced editing. Additionally, though it’s nice to see the pictographic representations of what to add, there is NO styling ability. No header options, limited bold/emphasis, and it says alt text is purely optional. This is the case for only select photos. Overall, this was a pretty quick decision – Wix’s editor isn’t very a11y friendly. Having components of the Wix editor (visual cues) may be a nice thing to add to our version of CKE though.