spacemonkey214
Forum Replies Created
-
Forum: Plugins
In reply to: [Block Accessibility Checks] Bug: Plugin not locking pages ?Heya Troy,
Sorry for the late response, new year and all that 🙂
Yes ! It works now.
I am unsure whether that is related to a change in this matter, but i’ve tested it the same way again and now when i add an image without an alt-text it correctly shows that there is an error. When i try to remedy that mistake by adding an alt-text it focusses the element after the first input. So if i try to write “abc” i can only input “a” and then the focus shifts to the image itself and i have to navigate to the textbox again. I don’t remember that being the case before, but consider it a small price to pay.
So for all intents and purposes, i consider this solved. Thank you for your hard work !
Best regardsForum: Plugins
In reply to: [Block Accessibility Checks] Bug: Plugin not locking pages ?Hey Troy,
thanks for your effort, i really appreciate it. I think i’ve found in the meantime what’s happening in my case. I’ve tried it on a fresh instance, only default plugins, except this one ofc, and a default Twenty-Twenty-Three theme.
Apparently, the page is correctly prevented from being published as long as “Show Template” is not selected. I don’t really understand why that is.
To illustrate:
The full page:As you can see, the error is correctly shown as there is no alt-text.
However, as you can see the page can be published here. That is because of the “Show template” selection here:Without the selection, the page cannot be published as expected:
This might be my inexperience with wordpress speaking, but i am no longer sure if that is a bug, but either way it appears that the publish prevention can be circumvented that way.
Forum: Plugins
In reply to: [Block Accessibility Checks] Bug: Plugin not locking pages ?The validation itself seems correct. I am getting the expected a11y-figure and correct error description in the side bar as expected.
What confuses me is the “Publish prevention” if errors are present. When content is edited in a “Post” and errors are present saving the post is prevented correctly as expected.
However when done through “Pages” the validation is still happening within the blocks, but saving the Page is still possible even with errors still being unresolved.
Is that intentional ? I would have expected that when validation is possible in that view the prevention would also apply.
In particular i added an image to the page/post and left the alt-text empty which is being evaluated correctly as an error, so nothing fancy really. In both cases the image is not marked as decorative.
The observed effect is that with the same content in “Posts” the publish button has aria-disabled=”true” while errors remain, and in Pages it is aria-disabled=”false” no matter what.
If that is intentional, because pages could have all kinds of content, would it be possible to extend the plugin to behave in the way i would have expected ?