Keyboard test Gutenberg, a first try

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.

  • Gutenberg: Plugin version 2.3.0
  • Browser: Chrome Version 64.0.3282.186 (Official Build) (64-bit)
  • OS: MacOS High Sierra, 10:13:3
  • OS Settings: Keyboard shortcuts: full keyboard access set on all control
  • Test done with: keyboard and my eyes only, no screen reader or other assistive technology.

This test results are part of the large scale Gutenberg testing for Accessibility, organized by The WordPress Accessibility team.

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.

Goal of this 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.

I’ve recorded my test session, view it on YouTube. I haven’t looked at Gutenberg for a while and did not look at the code, so be as blank as possible for how things work.

The test

First: add a new post, using the Gutenberg editor

Set up some content

  • enter a title
  • add a paragraph with some texts
  • add an H3 heading with the text “this is a heading”
  • add an image
  • add a list of 5 items (cats, dogs, fish, birds, spiders)
  • add a table with 2 columns, 2 rows and add some data in the cells
  • add the YouTube embed

Actions at the top:

  • preview the post
  • publish the post
  • switch to draft
  • hide and display the settings (the wheel)
  • Open  “More” ( 3 dots) and switch from visual code editor to code editor and back again

Modify the paragraph

  • make a link to on one of the words
  • align the text to the left when you focus the paragraph
  • with the settings on the top, select Fix toolbar to Top, is this usable for you when you change the content of a paragraph?

Block options

Modify the paragraph with the Block options (you can see the blocks by selecting the settings wheel at the top).

  • switch of/off drop cap
  • change font size and reset it
  • change background colour red
  • change text colour light grey
  • clear text and background colour
  • align the block to the left
  • add an additional CSS class wp-caption

Modify a heading

  • change the H3 heading into an H2
  • make a part of the heading italic
  • remove the heading

Modify an image

  • add a link to the image
  • add a caption
  • align image to the right
  • change the size of the image using the Block options

Modify the list

  • add an item to the list
  • delete an item from the list

Modify the table

  • add a row
  • add a column
  • delete a row
  • delete a column

Manipulate the blocks

  • move the image above the H2 heading
  • turn the list into a paragraph
  • delete a block

Found issues and questions

  • How to reach the block options for a corresponding block? I could not find a way to reach the block options because the focus on the item you are working on is lost.
  • How to add a link to a paragraph or caption, the focus is lost before you can add the link to the selected test.
  • For the block type selection: if you tab twice, the focus drops out of the modal.
  • The preview button does not get focus, I can not preview the post.
  • After selecting Publish it’s confusing how to get to the update options. They are hard to reach with keyboard, I couldn’t figure out the tab order for this.
  • How to select a date of publishing, only the time gets visual focus. The date modal could not be closed by keyboard too.
  • What is the logic for showing/not showing the toolbar above for example a paragraph. Sometimes is shows, sometimes it doesn’t.
  • Not keyboard related, but anyhow: The table needs a <th> option.

Looking back on 2015 and forward to 2016

Last year I changed the focus of my company. I wanted to do web accessibility related work only. The plan was to:

  • build and maintain accessible websites only
  • give accessibility training to web developers and graphic designers
  • help developers and companies fixing accessibility issues
  • give talks on WordCamps and Meetups
  • keep contributing to WordPress

Continue reading “Looking back on 2015 and forward to 2016”

Girls can’t code and my English sucks

Last week I had the exact same conversation four times. With four different WordPress developers. All women.

The topic: I want to publish code, discuss issues that matter, ask questions to core developers, blog, make some noise, contribute, but I’m to afraid to do that. It reminded me of myself.

What is the matter with us women? Why the self inflicted self pity and lack of confidence?

“I am not good enough, I don’t know enough, what if they think I’m stupid, my English really sucks.”

Do only female WordPress programmers think that way? Or are women and men with talent and knowledge all over the world hiding themselves, because they think they aren’t good enough? Sobbing under their desks, anxiously staring at the world, hiding from critisim and ridicule. What a waste of talent and possibilities!

So what are we afraid of, why sell we ourselves short?

Every contribution, blog post, piece of code you publish is valuable. Criticism is part of the job, learn from it, don’t hide, embrace it, it helps you getting better! Nobody makes fun of you when you want to contribute and do you best. You are most welcome!

Do you really think all the guys, that make so much noise, always write perfect code and never make mistakes? Hell no, just like you they work and learn, make mistakes, write bugs and try to improve themselves.

Exactly the same as you…

So girl: pull yourself together, put your teeth into it, jump in at the deep end. Study hard and publish what you found useful. Respect is not earned by sitting silently in a corner.

Show what you can do and be proud of yourself, and don’t be afraid to make a mistake. We are all human, boys and girls alike.

The screen-reader-text class, why and how?

Imagine you are blind, how do you understand a website? You would use a screen reader. All the text in a website is read out loud for you, from top to bottom. To navigate a site you can call a link list and a headings list.

The headings list you can use to navigate inside the page. Jump to a heading of interest and read from there. With the link list you can choose where to go next. There are more ways to navigate a site, but links and headings are most commonly used by screen reader users.

How can you decide where to go, when a lot of the links in a page are called “Read more”. Read more about what?

So, if you are a web developer, how can you help your blind visitor to understand your website? First of all: use headings that make sense. And second: use link texts that tell where they are linking to. And here the screen reader text comes in: it hides text from screen, but not from a screen reader.

For example links with the text “Read more”, “Continue reading” or a plain “>” or a font awesome icon. Looks neat and small and is incomprehensible for your blind visitor. But writing the whole post title in the read more link is long and ugly.

How to fix the “Read more” link?

Say you have the HTML:

<a href="url-here">Read more</a>

You can change this into:

<a href="url-here">Read more<span class="screen-reader-text"> about cute kittens</span></a>

For WordPress for example:

<a href="<?php the_permalink(); ?>">Read more<span class="screen-reader-text"> about <?php the_title();?></span></a>

And then you add the CSS in your stylesheet:
Note: this CSS is update on October 2017

/* Text meant only for screen readers. */
.screen-reader-text {
  border: 0;
  clip: rect(1px, 1px, 1px, 1px);
  clip-path: inset(50%);
  height: 1px;
  margin: -1px;
  overflow: hidden;
  padding: 0;
  position: absolute !important;
  width: 1px;
  word-wrap: normal !important;

The element with the class screen-reader-text is made very small with clip, which needs the position absolute. Not visible for the eye, but read out load by a screen reader.

Don’t use display: none; or visibility: hidden. Screen readers don’t speak those, so that’s no use in this case.

Font awesome and other icons

How about your social media icons:

<i class="fa fa-twitter"></i>

It’s just an empty container and the <i> has a semantic meaning: text in an “alternate voice”.

Better use:

<span class="fa fa-twitter"></span><span class="screen-reader-text">Twitter</span>

By the way: You can help changing this inaccessible way of implementing Font Awesome by joining the discussion in the Font Awesome GitHub.

Richard Senior did an excellent write up about WordPress, Font Awesome and Accessibility.

Labels in forms

A form input field needs a label. It’s just good practice and it tells a screen reader user what to fill out. A placeholder is no label, screen readers don’t read them well. But a label takes up space and maybe you don’t want that in your theme. So hide it with screen-reader-text.
For example in the WordPress search form:

<form role=”search” method=”get” class=”search-form” action=”url-here”>
<label for=”search-id” class=”screen-reader-text” >Search this website…</label>
<input name=”search” type=”text” value=”” placeholder=”Search this website…” id=”search-id”>
<input type=”submit”  value=”Search”>

Hiding links

As a service to screen reader users and keyboard only users you can add skip links at the top of a page. That way a visitor can quickly jump to e.g. the content, without having to tab though the navigation.

They look something like this:

<ul class="skip-link">
 <li><a href="#nav" class="screen-reader-text">Jump to main navigation</a></li>
 <li><a href="#content" class="screen-reader-text">Jump to content</a></li>
 <li><a href="#footer" class="screen-reader-text">Jump to footer</a></li>

Some JavaScript is necessary to make skip links work properly.

If a visitor can see, it’s nice if the skip links are visible when they come in focus while tabbing though the links. So you can add the CSS to do that:

.screen-reader-text:focus {
    clip: auto !important;
    display: block;
    height: auto;
    width: auto;
    z-index: 100000; /* Above WP toolbar. */

The screen reader text in more detail

Clip versus absolute positioning

.screen-reader-text {
    position: absolute !important;
    left: -999em;

This technique is pretty solid and works in all browsers however there are two main issues with this technique – its relatively easy to break, and it can cause a page “jump” if applied to focusable elements (like skip links and read more links), which can be very confusing to sighted keyboard users. [Reference:  Jeff Burnz and Jonathan Snook]

Different ways of doing it

Gary Jones collected a few different ways of hiding text with clip. And there are more variations. Pick the one that suits your theme or adjust it to your needs.

What about:

clip: rect(1px, 1px, 1px, 1px);


clip: rect(0, 0, 0, 0);

I couldn’t find a specific reason to use 0 or 1px, they both seem valid.

Back and forward compatibility

Clip is deprecated in CSS3, but supported by most browsers, it’s replaced by clip-path. Internet Explorer below version 8 doesn’t want a comma as separator and up to version 11 it doesn’t support clip-path yet, so you end up with:

clip: rect(1px 1px 1px 1px); /* IE6, IE7 */
clip: rect(1px, 1px, 1px, 1px);
clip-path: polygon(0px 0px, 0px 0px,0px 0px, 0px 0px);

The other way around: hide from a screen reader

The other way around is also possible. If you have an element that’s not relevant for screen reader users, you can hide it by adding aria-hidden=”true“.
This is used for example in the WordPress Admin for hiding a separator in the main menu.

<li class="wp-not-current-submenu wp-menu-separator" aria-hidden="true">


ARIA roles (Accessible Rich Internet Applications) are instructions for screen readers you can add to your HTML.

WordPress and the screen-reader-text

The name of the class is up to you, but “screen-reader-text” is the standard name for WordPress, and is used by WordPress core in the Admin and the front end and in the bundled themes like Twenty Fifteen. As from version 4.2 this class is WordPress generated CSS, so it’s important that you add it to your theme before updating to WordPress 4.2.

The screen-reader-text wil be used for the get_search_form, the comments_popup_link, the archives and categories dropdown widgets and will be used in more cases in future releases.

If you are a WordPress developer and want more controle over this, please support Gary Jones by commenting on his ticket add_theme_support( ‘screen-reader-text’ ).


And if you can’t add the screen-reader-text class yourself to a WordPress theme: there’s a plugin for that.

Read more screen reader text: I knew you would check

  1. Hiding content for accessibility by Jonathan Snook
  2. CSS in Action: Invisible Content Just for Screen Reader Users on WebAIM
  3. Hiding text for screen readers with WordPress Core by Joe Dolson
  4. Clip Your Hidden Content For Better Accessibility by Thierry Koblentz
  5. Understanding the CSS Clip Property by Hugo Giraudel
  6. Using CSS clip as an Accessible Method of Hiding Content in Drupal, by Jeff Burnz
  7. WordPress plugin “.screen-reader-text” theme support by Jaime Martinez

Photo Read More tattoo: Cory Doctorow.