[GH-ISSUE #7033] [Bug] Accessibility - Screen reader does not announce editor content #3107

New issue

Open

opened 2026-03-23 21:27:39 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 21:27:39 +00:00

Owner

Originally created by @jquesada2016 on GitHub (Dec 22, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7033

Bug Description

I am a user who is legally blind. I am using the NVDA screen reader. I noticed that the editor is currently unaccessible while editing content. As you move the text cursor around, nothing is announced by the screen reader, nor are selections. Currently, the only way to have the screen reader announce what's in the editor is to make a selection, copy it, and have the screen reader read aloud the contents of the clipboard. The other way is to mouse over the text, and it will read it aloud, but this is much too slow.

How to Reproduce

Download and install NVDA
Open AppFlowy
Write some content in the editor
Use the arrow keys on your keyboard to move around, and notice nothing is announced by the screen reader
Make a text selection, either with the keyboard or mouse, and notice nothing is announced by the screen reader

Expected Behavior

I expect NVDA to be able to tell when text is edited and the cursor/selection changes state.

Operating System

Windows 11

AppFlowy Version(s)

0.7.8

Screenshots

No response

Additional Context

No response

Originally created by @jquesada2016 on GitHub (Dec 22, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/7033 ### Bug Description I am a user who is legally blind. I am using the NVDA screen reader. I noticed that the editor is currently unaccessible while editing content. As you move the text cursor around, nothing is announced by the screen reader, nor are selections. Currently, the only way to have the screen reader announce what's in the editor is to make a selection, copy it, and have the screen reader read aloud the contents of the clipboard. The other way is to mouse over the text, and it will read it aloud, but this is much too slow. ### How to Reproduce 1. Download and install NVDA 2. Open AppFlowy 3. Write some content in the editor 4. Use the arrow keys on your keyboard to move around, and notice nothing is announced by the screen reader 5. Make a text selection, either with the keyboard or mouse, and notice nothing is announced by the screen reader ### Expected Behavior I expect NVDA to be able to tell when text is edited and the cursor/selection changes state. ### Operating System Windows 11 ### AppFlowy Version(s) 0.7.8 ### Screenshots _No response_ ### Additional Context _No response_

mirror added the

platform-windows

editor

bug

labels

2026-03-23 21:27:39 +00:00

mirror commented

2026-03-23 21:27:40 +00:00

Author

Owner

@KevinCCucumber commented on GitHub (Dec 22, 2024):

While not being affilitated with appflowy in any way, this seems to be a flutter issue currently being worked on:
https://github.com/flutter/flutter/issues/103464

@KevinCCucumber commented on GitHub (Dec 22, 2024): While not being affilitated with appflowy in any way, this seems to be a flutter issue currently being worked on: https://github.com/flutter/flutter/issues/103464

mirror commented

2026-03-23 21:27:40 +00:00

Author

Owner

@jquesada2016 commented on GitHub (Dec 22, 2024):

I just checked out the linked issue. Can we do something different? What we can do is have a hidden alert. Whenever the cursor position changes, or text selection, we can change the content of the hidden alert. This should allow NVDA and other screen readers to pick up the change.

This is definitely not ideal, but it should make at least basic navigation possible.

@jquesada2016 commented on GitHub (Dec 22, 2024): I just checked out the linked issue. Can we do something different? What we can do is have a hidden alert. Whenever the cursor position changes, or text selection, we can change the content of the hidden alert. This should allow NVDA and other screen readers to pick up the change. This is definitely not ideal, but it should make at least basic navigation possible.

mirror referenced this issue

2026-03-23 22:19:20 +00:00

[PR #3107] [MERGED] feat: disable moving page into the database #5571