Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility issues #6757

Open
distantnative opened this issue Oct 17, 2024 · 4 comments
Open

Accessibility issues #6757

distantnative opened this issue Oct 17, 2024 · 4 comments
Labels
type: a11y 👐 Concerns a change that would make it more accessible to more people

Comments

@distantnative
Copy link
Member

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

@distantnative distantnative added the type: a11y 👐 Concerns a change that would make it more accessible to more people label Oct 17, 2024
@MarcoZehe
Copy link

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
Copy link
Member Author

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

@rkingett
Copy link

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
Copy link
Member Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: a11y 👐 Concerns a change that would make it more accessible to more people
Projects
None yet
Development

No branches or pull requests

3 participants