Does anyone else use the Grammarly browser extension? I just noticed that it recently started adding aria-label="To enrich screen reader interactions, please activate Accessibility in Grammarly extension settings" to each mceEditable area when editing a page, and that attribute is getting saved with the page. It hasn’t always done this. I only see it in pages that I have edited in the past couple of days.
For now I have just disabled the Grammarly extension, but I hate to do that. I rely on it pretty heavily.
Anyone else have this problem? Is there an easy fix?
What a pain! As a band-aid, certainly an onOutput handler could be used to look for that exact HTML and strip it from front-end page source. Doing a bit of googling for “tinymce + grammarly” I don’t see others reporting this exact issue but definitely some ups-and-downs with various grammarly releases. We do currently strip certain Google Docs specific markup on save, if this continues to be an issue please let us know and we can file it as a suggested “markup to auto-strip” for core.
I enabled accessibility in Grammarly settings (like the aria-label suggested) and things are better. It doesn’t add that message anymore. But it still adds aria-label="" and spellcheck="true" attributes. I will probably add a handler to remove those attributes.