getkirby / kirby

Kirby's core application folder
https://getkirby.com
Other
1.32k stars 168 forks source link

Accessibility issues #6757

Open distantnative opened 4 weeks ago

distantnative commented 4 weeks ago

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.

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

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.

Experience described based on the Demokit. https://tweesecake.social/@weirdwriter/113320426101633134

MarcoZehe commented 4 weeks ago

I remember running into similar issues when I tried Kirby out a way while back. However, due to my health related energy constraints, I could not pursue this further. But what Robert described sounds very familiar. I also didn't see the option to switch to a Markdown and KirbyText based entry format, as was mentioned here: https://mastodon.social/@getkirby/113320553949991637

distantnative commented 4 weeks ago

@MarcoZehe instead of the blocks field you can use the textarea field in your blueprints: https://getkirby.com/docs/reference/panel/fields/textarea

rkingett commented 4 weeks ago

I was using the web demo, so could only navigate the blocks, but the issues are cross browser ones, including the duplicate elements issue with having duplicate buttons do the same action.

distantnative commented 4 weeks ago

@rkingett not debating these that's why I opened the issue to get those fixed.

My comment was only to explain how to set up fields that are markdown based as Marco was wondering.