It is no longer possible to open Media with a Screenreader for editing
-
Hello, it is no longer possible to open Media in sites or posts with a Screenreader for editing. This fails with the Android App, the iOS App and also in the Dashboard. Our temporarily workaround is to close the Screenreader and to open the image by hand. Finally restarting the Screenreader for editing the image now.
The blog I need help with is: (visible only to logged in users)
-
Are you using the new Block editor? Does it still work in the classic wp-admin dashboard (reached by adding /wp-admin to your URL).
-
Hello and many thanks for your reply
The problem is the same if using the new block editor or not. And it is also impossible to reach an image by screenreader with the classic wp-admin dashboard. -
We made some additional tests. It seems you’re right. There’s a link to the to the new editor. Images posted with the old editor cannot opened with a screenreader for editing. Images posted with the new editor can now be reached by the screenreader.
For visually impaired people is this fact very bad. They cannot edit older posts anymore by screenreader. -
-
-
Hi there,
Can you please provide a link to a post where you have this issue?
Is this specifically when you have the block editor enabled, and are trying to edit an image in a post published with the classic editor only? Can you edit any other content in that post, or is the problem exclusively with editing the images? What kind of changes are you trying to make, or are you completely unable to even select the image in the post?
What browser and what screen reader software are you using? If possible, please include the version numbers as well.
This fails with the Android App, the iOS App
The block editor is not available yet in the mobile apps, so if you have similar issues there it’s likely unrelated. Please use the Help and Support option in the apps themselves to contact the mobile support team directly. That will include information about your app and device in the support ticket which will help them troubleshoot the issue there.
-
Hello and thank you very much for your reply.
The described issue occurs when editing again a published post or until writing a new post with an already inserted image in the WordPress-App. It is no longer possible to mark embedded images with the screenreader. This problem occurs with Samsung Galaxy S7, Android 8 and Talkback, WordPress App 12.4. Also with iPhone 6, actual iOS, VoiceOver and newest WordPress App. And various other tested tablets, too.
Example-Link: https://blogieblogdorf.home.blog/2019/05/16/test/
The Screenreader moves the cursor downwards to the end of the post. For every image on this way, I can hear a short beep. At the end there’s a message, that the cursor was moved and now text may be inserted. That’s all.
The issue occurs not with Amazon’s VoiceView and WordPress App 12.4Thank you for your help and with best wishes for a nice day – Matthias
-
So, this is rather interesting.
Visually on your post, I see this:
A small yellow rectangle.
A small red rectangle.
A small green rectangle.
A small blue rectangle.
A taller orange rectangle.
An even taller purple rectangle.
An image of a bench.
A taller than the previous rectangle blue rectangle.
An even taller brown rectangle.
A really tiny red rectangle.
A centered red rectangle.
And another really tiny red rectangle.I see those rectangles are actually the uploaded image files themselves, so if what I described is what you intended, that is what’s being presented.
But it sounds like the issue is with editing them, yes? If so, would you please verify if this issue is new as of the release of the WordPress App 12.4? If not, do you recall anything else in your setup that changed right before the problem?
-
Hello and thank you for your interest!
Yes, the issue is while editing/writing in the Classic Editor.
And no, there were no changes in our setups. And also, there is a couple of various devices involved by this issue.
The issue occurred a few updates ago. But it took some time for us to realize, that this referred to an obvious fault. And then, it was necessary too, to do some additional tests.Best regards – Matthias
-
-
-
Hello macmans,
did the Android Developer Team find out anything, meanwhile?Best regards – Matthias
-
I’ve just followed up with the team as we have not heard back. Someone will post an update here once we have more news to share.
-
-
Just a quick update to let you know our development team is looking at this now. I’ll report back with news once I know more.
-
- The topic ‘It is no longer possible to open Media with a Screenreader for editing’ is closed to new replies.