GrapesJS Issues

3,464 parsed GitHub issues — 370 solved · 90 open. Search, filter and explore battle-tested answers.

3 issues found

🔍 accessibility
#6634October 28, 2025by ssteele3 answers
0 reactions
questionbugaccessibilitytypescript

Accessibility errors

GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 141.0.7390.123 Reproducible demo link https://grapesjs.com/demo.html Describe the bug Our application serves clients that require all pages to be accessible for all users. I am running the latest grapesjs libraries:...

niemyjski

I'm also seeing this behavior.

artf

This is related to https://github.com/GrapesJS/preset-webpage You're free to update styles on top of that plugin or submit a PR with the fixes there.

ClaudeCode

Thanks for reporting this, @ssteele. Great question about Accessibility errors. The recommended approach with ProseMirror is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the on...

View details
#2390November 8, 2019by sagaranandani171 answer
0 reactions

Accessibility - Keyboard user is unable to get the tooltips which are shown using mouse hover on Grape editor but not appearing using tab navigation

OS version: 1903 (OS Build: 18326.295) Browser: Edge(Microsoft Edge 44.18362.267.0) User Experience: If tooltips are not accessible with keyboard inside editor, than keyboard user will not be able to understand the control purpose and will face difficulties while interacting with it. Steps to reproduce When user moves...

artf

I'd point all accessibility issues here #654

View details
#654December 16, 2017by mgifford3 answers
6 reactions

Needs Accessibility Review

The demo looks great, but points to the need of a serious accessibility review. There is an open issue in the Drupal community looking at this, and we are working on a good pattern. The start though is having elements be focus-able for keyboard only users.

artf

Thanks Mike for pointing this out, I definitely add this to the Roadmap (#74)

ankx06

@artf just wanted to check about the timeline to add this feature. I see that you have moved it to backlog, so what is the plan to support focus on each component via keyboard.

mgifford

Ya, sorry.. Been a while since I posted this link in 2017.. Had kinda forgotten what the focus of GrapeJS is. But ya, as I said 5 days ago, accessibility "isn't something you can just 'turn on'."

View details