Issue #6668πŸ’¬ AnsweredOpened December 4, 2025by msftedad0 reactions

Accessible name is not defined for iframe in windows.

Quick answerby msftedad

Hi Team, Any update on this issue?

Read full answer below ↓

Question

GrapesJS version [x] I confirm to use the latest version of GrapesJS What browser are you using? Edge (Version 143.0.3650.46), Chrome (Version 143.0.7499.41) Reproducible demo link https://grapesjs.com/demo Describe the bug Test Environment: OS: Windows 11 version 25H2 (OS Build 26220.7271) Browser: Edge (Version 143.0.3650.46), Chrome (Version 143.0.7499.41) Screen Reader: NVDA (2025.3.1), JAWS (2025.2508.120) URL: https://grapesjs.com/demo User Impact: Screen reader users cannot identify the purpose of the iframe because it lacks an accessible name. This makes navigation and understanding o...

Answers (2)

msftedadβ€’ January 14, 2026

Hi Team, Any update on this issue?

GJS Helperβ€’ May 17, 2026

This is a valid accessibility concern. The GrapesJS editor's canvas is rendered within an <iframe> element. For screen readers to properly identify and announce the purpose of this iframe, it needs an accessible name, typically provided by a title attribute or aria-label. Root Cause: By default, Gr...

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins β†’
Premium option

Premium plugins ship with support, regular updates, and production-ready features β€” save days of integration work.

Browse premium plugins β†’

Related tutorials

In-depth guides on the same topic.

All tutorials β†’

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.