11 Comments

  1. WPezDeveloper

    “Therefore, organizations which have high risk profiles should consult legal counsel before using it and may want to choose to use the legacy editor instead.”

    Whoa. That’s significant.

    If VIP struggles to book new business, this is going to hurt.

    Report

  2. Keiko

    Having poor eyesight. I have changed the settings in Firefox so I us black background and white text. No matter what settings websites use by default. I can’t see the selected text in Gutenberg.

    Classic TinyMCE Editor
    https://i.postimg.cc/MGGmst45/tinymce.jpg

    Gutenberg
    https://i.postimg.cc/8s8vNmt2/gutenberg.jpg

    Report

    • Stomme poes

      Hi Keiko,
      If you’re using Windows High Contrast, you can’t see selected text in Firefox due to a combination of a Firefox bug and the fact that some parts of the editor use a custom CSS colour for the selection highlight (besides, Firefox also doesn’t change links, though it seems maybe that can be set locally on your Firefox to work better: https://bugzilla.mozilla.org/show_bug.cgi?id=697836)

      You’ll want to use Edge browser instead.

      Report

  3. Per Søderlind

    I’m tech lead for the Norwegian Government WordPress multisite, we have to comply with WCAG 2.1 and can’t use Gutenberg.

    Btw, I have nothing against Gutenberg but must follow the law.

    Report

    • Frederike

      @Per Søderlind, similar here, we also can’t use Gutenberg due to GDPR issues, every page edit loads an external Google webfont and leaks the current user IP to Google, no opt-out possible, no information anywhere about that. The webfont actually would not be necessary at all, it is not used in front-end, but all tickets everywhere about this tracking die silently…

      Report

      • Otto

        If your theme doesn’t use the font, then you should add editor styling to it, so that the theme tells the editor what font to use instead, as well as to set the correct widths and other settings. Themes have control over the editor styling. They have for a long time.

        Report

      • Frederike

        Styling is not the issue here. There is no way to disable the loading of Google webfont and leaking current user IP to Google in WordPress backend editor at every page edit. This voids GDPR. And this excludes Gutenberg from our options.

        Report

  4. toto

    coming in 5.2, Site Health should be audited as well.
    Too many questions about security and accuracy.

    Report

  5. Phil Johnston

    Wow, amazing and thorough work by Tenon! This document is a wealth of information for building accessible interfaces.

    Report

  6. Drew Jaynes

    I really enjoyed the completeness with which the report was written. Anybody can do an audit and come up with conclusions, but the fact that they cited issues and then gave recommendations for how to resolve them really makes this a valuable thing to have. I wish I had one of these for every piece of software I’ve ever written.

    Report

  7. Digital A11Y

    I am a screen reader user & I just started using the Gutenberg editor… I felt that adding blocks is easy but rearranging them was very difficult to me… I used HTML editor to realign the content & some of the blocks are very new & I would prefer a help tooltip explaining me what exactly that block does. While I haven’t explored every feature of the editor, the basic features required to output a post seems accessible to me.

    Gutenberg got lot usability problems & takes time for the users to get used to. As a person with disability I can say that this needs a learning curve, time & energy.

    Report

Comments are closed.

%d bloggers like this: