How does Gutenberg 2.3 perform with keyboard only? I’ve set up a test and looked for issues. The test, the results and a YouTube with the test are included.
Goal of this Gutenberg test is to see where currently the problems are and collect data to write a manual for keyboard users. Also I want to learn and construct a standard test for other assistive technology. The test is set up to do the most common tasks for a content manager (who is not a developer). Like add and modify text, headings, images, lists, tables, and embeds.
The test results are part of the large scale Gutenberg testing for Accessibility, organized by The WordPress Accessibility team.
HTML elements like check buttons, radio buttons or select options can be hard to style with CSS in a custom design. There are many workarounds for this, but are they accessible? Here’s my point of view.
HTML elements like check buttons, radio buttons or select options can be hard to style with CSS in a custom design. There are many workarounds for this, based on two different approaches:
- Hide the form elements from sight and apply the styling on a container or related element
How do you create content that can be understood by everyone, also for people that use the web in another way than you would expect? Keeping your content accessible isn’t hard. You just need to look at your text differently. Continue reading “Workshop accessible content”
A few months ago I asked in the Human Made general Slack channel: “What shall I talk about at WordCamp Europe?”
And the honourable Ant Miller replied: “Accessibility in the age of the headless CMS.”
Great, I thought. A new subject, much to learn and tell about, I started to read up on the subject. And then I realised: oh no, I have to learn React!