Ancestors

Toot

Written by Robert Kingett backup on 2024-10-17 at 02:34

Gave @getkirby a try and, while I only had access to the demo for about an hour, some Accessibility thoughts.

The navigation is very smooth. I didn't find many problematic areas except for buttons appearing to be split into two elements but do the same action, like, for example, there will be an unlabeled button right next to the edit button but that unlabeled edit button still leads to the edit button.

Radio buttons are read nicely! Almost all form fields are labeled nicely for posting content, except for the forms where I had to actually write post bodies.

To post, you first choose a block. I genuinely don't understand how this is more intuitive than taking 5 minutes to learn some #Markdown but anyway, after you pick a block, another dialog opens where you actually do the writing. This is the most problematic. The more than a few unlabeled buttons above the text areas appear to be formatting buttons but I was unable to tell, when picking the, markdown block, for example.

When I picked a heading block, I was to pick what heading level I wanted, and this was very accessible, but when it came time to save my block, somehow, I kept missing the save button or whatever that would actually add the block when I'm all done.

Other than that, with a few accessibility tweaks and attention, this could be a great CMS for static sites and otherwise. This is just a personal thing, but I just could not get the hang of blocks. I like writing text and going back up to review it and so on. Still, this CMS is far more accessible than I had assumed.

[#]CMS #Accessibility #Kirby

=> More informations about this toot | More toots from weirdwriter@tweesecake.social

Descendants

Written by Kirby CMS on 2024-10-17 at 03:07

@weirdwriter thank you so much for the feedback! This is great input for us to improve accessibility further. The blocks field is by the way completely optional - many user asked for a more visual editing experience at some point. But you can set up your blueprints also just with normal text and textarea fields using Markdown and KirbyText. So if you like that, that’s there out of the box (though textarea formatting buttons might have the same accessibility problem, we will look into this).

=> More informations about this toot | More toots from getkirby@mastodon.social