WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: WordPress - do screen reader users still need the classic editor?

for

Number of posts in this thread: 5 (In chronological order)

From: Sandy Feldman
Date: Thu, Jan 06 2022 9:02AM
Subject: WordPress - do screen reader users still need the classic editor?
No previous message | Next message →

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>hey all,</p>
<p>I am working on a WordPress blog site for a screen reader user
(JAWS 2022). <br>
</p>
<p>Have the Gutenberg block issues been resolved or should I set the
site up with the Classic Editor? <br>
</p>
<p>Amanda Rush, looking at your <a moz-do-not-send="true"
href="https://www.customerservant.com/">June 9 2021 blog post</a>
I'm guessing Classic Editor. Any change since then?<br>
</p>
<p>thanks so much!<br>
</p>
<div class="moz-signature">Sandy
<p><a href="https://sandyfeldman.com">sandyfeldman.com</a>
<br>
<a href="https://www.a11yready.com/">a11yready.com</a><a>
</a></p>
<a><br>
<br>
</a></div>
</body>
</html>

From: Lucy GRECO
Date: Thu, Jan 06 2022 9:29AM
Subject: Re: WordPress - do screen reader users still need the classic editor?
← Previous message | Next message →

hello:
i personally have tried the block editor and still would want to use the
classic
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Thu, Jan 6, 2022 at 8:02 AM Sandy Feldman < = EMAIL ADDRESS REMOVED = > wrote:

> hey all,
>
> I am working on a WordPress blog site for a screen reader user (JAWS
> 2022).
>
> Have the Gutenberg block issues been resolved or should I set the site up
> with the Classic Editor?
>
> Amanda Rush, looking at your June 9 2021 blog post
> <https://www.customerservant.com/> I'm guessing Classic Editor. Any
> change since then?
>
> thanks so much!
> Sandy
>
> sandyfeldman.com
> a11yready.com <https://www.a11yready.com/>
>
>
> > > > >

From: Sandy Feldman
Date: Thu, Jan 06 2022 9:33AM
Subject: Re: WordPress - do screen reader users still need the classic editor?
← Previous message | Next message →

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks for taking the time to answer Lucy!<br>
</p>
<div class="moz-signature">Sandy
<p><a href="https://sandyfeldman.com">sandyfeldman.com</a>
<br>
<a href="https://www.a11yready.com/">a11yready.com</a><a>
</a></p>
<a><br>
<br>
</a></div>
<div class="moz-cite-prefix">On 2022-01-06 11:29 a.m., Lucy GRECO
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAESOp7oyWCZi3=E2AS8eOrkd8DCQbVY+ = EMAIL ADDRESS REMOVED = ">
<pre class="moz-quote-pre" wrap="">hello:
i personally have tried the block editor and still would want to use the
classic
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
<a class="moz-txt-link-freetext" href="http://webaccess.berkeley.edu">http://webaccess.berkeley.edu<;/a>
Follow me on twitter @accessaces



On Thu, Jan 6, 2022 at 8:02 AM Sandy Feldman <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">&lt; = EMAIL ADDRESS REMOVED = &gt;</a> wrote:

</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">hey all,

I am working on a WordPress blog site for a screen reader user (JAWS
2022).

Have the Gutenberg block issues been resolved or should I set the site up
with the Classic Editor?

Amanda Rush, looking at your June 9 2021 blog post
<a class="moz-txt-link-rfc2396E" href="https://www.customerservant.com/">&lt;https://www.customerservant.com/&gt;</a> I'm guessing Classic Editor. Any
change since then?

thanks so much!
Sandy

sandyfeldman.com
a11yready.com <a class="moz-txt-link-rfc2396E" href="https://www.a11yready.com/">&lt;https://www.a11yready.com/&gt;</a>


List archives at <a class="moz-txt-link-freetext" href="http://webaim.org/discussion/archives">http://webaim.org/discussion/archives<;/a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">List archives at <a class="moz-txt-link-freetext" href="http://webaim.org/discussion/archives">http://webaim.org/discussion/archives<;/a>
</pre>
</blockquote>
</body>
</html>

From: Amanda Rush
Date: Thu, Jan 06 2022 10:47AM
Subject: Re: WordPress - do screen reader users still need the classic editor?
← Previous message | Next message →

Based on personal experience, I'd recommend making the classic editor
available to screen reader users, even if the user in question is proficient
at using complex web applications. I've used it on 5 projects now, ranging
from simple to complex, and there are always places where the misses are big
misses, especially with some of the more complex blocks. Conceptually, I'm
not opposed to the idea of the thing, and it's getting harder and harder to
find plugins that will work well without it that are new. But I find the
block editor in general to be an efficiency nightmare with a screen reader
and only recommend it on sites that have very little complexity, (simple
pages and posts), and for users who are willing to put up with a lot of
changes in a short period of time and who are willing to experiment.

Amanda

-----Original Message-----
From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > On Behalf Of Lucy
GRECO
Sent: Thursday, January 6, 2022 11:29 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] WordPress - do screen reader users still need the
classic editor?

hello:
i personally have tried the block editor and still would want to use the
classic Lucia Greco Web Accessibility Evangelist IST - Architecture,
Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Thu, Jan 6, 2022 at 8:02 AM Sandy Feldman < = EMAIL ADDRESS REMOVED = > wrote:

> hey all,
>
> I am working on a WordPress blog site for a screen reader user (JAWS
> 2022).
>
> Have the Gutenberg block issues been resolved or should I set the site
> up with the Classic Editor?
>
> Amanda Rush, looking at your June 9 2021 blog post
> <https://www.customerservant.com/> I'm guessing Classic Editor. Any
> change since then?
>
> thanks so much!
> Sandy
>
> sandyfeldman.com
> a11yready.com <https://www.a11yready.com/>
>
>
> > > archives at http://webaim.org/discussion/archives
> >
http://webaim.org/discussion/archives

From: Sandy Feldman
Date: Thu, Jan 06 2022 10:54AM
Subject: Re: WordPress - do screen reader users still need the classic editor?
← Previous message | No next message

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks Amanda. No way I want to put this guy through "an
efficiency nightmare"! <br>
</p>
<div class="moz-signature">Sandy
<p><a href="https://sandyfeldman.com">sandyfeldman.com</a>
<br>
<a href="https://www.a11yready.com/">a11yready.com</a><a>
</a></p>
<a><br>
<br>
</a></div>
<div class="moz-cite-prefix">On 2022-01-06 12:47 p.m., Amanda Rush
wrote:<br>
</div>
<blockquote type="cite"
cite="mid: = EMAIL ADDRESS REMOVED = ">
<pre class="moz-quote-pre" wrap="">Based on personal experience, I'd recommend making the classic editor
available to screen reader users, even if the user in question is proficient
at using complex web applications. I've used it on 5 projects now, ranging
from simple to complex, and there are always places where the misses are big
misses, especially with some of the more complex blocks. Conceptually, I'm
not opposed to the idea of the thing, and it's getting harder and harder to
find plugins that will work well without it that are new. But I find the
block editor in general to be an efficiency nightmare with a screen reader
and only recommend it on sites that have very little complexity, (simple
pages and posts), and for users who are willing to put up with a lot of
changes in a short period of time and who are willing to experiment.

Amanda

-----Original Message-----
From: WebAIM-Forum <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">&lt; = EMAIL ADDRESS REMOVED = &gt;</a> On Behalf Of Lucy
GRECO
Sent: Thursday, January 6, 2022 11:29 AM
To: WebAIM Discussion List <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">&lt; = EMAIL ADDRESS REMOVED = &gt;</a>
Subject: Re: [WebAIM] WordPress - do screen reader users still need the
classic editor?

hello:
i personally have tried the block editor and still would want to use the
classic Lucia Greco Web Accessibility Evangelist IST - Architecture,
Platforms, and Integration University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
<a class="moz-txt-link-freetext" href="http://webaccess.berkeley.edu">http://webaccess.berkeley.edu<;/a>
Follow me on twitter @accessaces



On Thu, Jan 6, 2022 at 8:02 AM Sandy Feldman <a class="moz-txt-link-rfc2396E" href="mailto: = EMAIL ADDRESS REMOVED = ">&lt; = EMAIL ADDRESS REMOVED = &gt;</a> wrote:

</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">hey all,

I am working on a WordPress blog site for a screen reader user (JAWS
2022).

Have the Gutenberg block issues been resolved or should I set the site
up with the Classic Editor?

Amanda Rush, looking at your June 9 2021 blog post
<a class="moz-txt-link-rfc2396E" href="https://www.customerservant.com/">&lt;https://www.customerservant.com/&gt;</a> I'm guessing Classic Editor. Any
change since then?

thanks so much!
Sandy

sandyfeldman.com
a11yready.com <a class="moz-txt-link-rfc2396E" href="https://www.a11yready.com/">&lt;https://www.a11yready.com/&gt;</a>


archives at <a class="moz-txt-link-freetext" href="http://webaim.org/discussion/archives">http://webaim.org/discussion/archives<;/a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap=""><a class="moz-txt-link-freetext" href="http://webaim.org/discussion/archives">http://webaim.org/discussion/archives<;/a>
List archives at <a class="moz-txt-link-freetext" href="http://webaim.org/discussion/archives">http://webaim.org/discussion/archives<;/a>
</pre>
</blockquote>
</body>
</html>