#quillforall — Public Fediverse posts

I write this post publicly, not just for @quillforall folks, whom I promised the test with Braille to. I will share it here, because this experiment can be useful to other blind Braille users as well.
Guess what?
PoEdit, the translation editor for Windows, version 3.9.1, has the same bug found on QUILL 0.8.0 Beta 1. Braille display with JAWS screen reader doesn't detect selection highlighting with 7 and 8 dots under each single character and space.

NVDA behaves correctly instead, both on QUILL and PoEdit, characters are properly selected. Unfortunately I have no idea whether Narrator can work with Focus Braille display, otherwise I'd have no issues in testing this as well.
This makes me suppose it's a @freedomscientific JAWS bug. I have mentioned them here as well, to make them aware. I have no idea of how to report a bug directly to them.
I think that not many blind professionals have reported the bug, as maybe most of them use commercial software more often, such as the Microsoft Office suite or, like me, simply surrendered to it.
As far as I can rememmber, the bug has always been there.
Today it's the first time I have properly identified it, and hopefully I can report it, as in 2006 I already tried to report an issue and it was fixed about 7 years later, it was even worse than this one because it prevented from using Sticky Keys for one-handed people. And my ex, who's blind and his left hand is injured, was definitely stuck. A vendor literally said in front of both of us "this bug has low priority as few people use sticky keys". Literally saying to a mobility impaired user, "you paid me but I don't cover your needs because you don't count". That was solved in JAWS 15.0, and the bug was there since 4.5.
NotePad++ editor behaves even more strangely for text selection, I always thought it was random but I managed to test it in deep today:
let's assume you have a blank file, so it starts with the line "1"; from margins and borders, in notepad++ settings, line number view must be checked on.
JAWS behavior: Notepad++ blank file, you type a sample sentence, let's say "QUILL for all".
You place the cursor on the q, then you select the whole line. You'll notice that the two l's of "quill for all" will not have the Braille cursor highlights.
What JAWS does: it highlights all the characters, including the line number. It behaves the opposite of how it should. It should highlight the text but not the line number. And the non-highlighted characters increase according to how long the line number is, space included. So, if "QUILL for all" is written on the 2800th line, the line number will be 2800, then space, then Q. Result? Braille display will highlight the line number with related space, then QUILL FO. Other letters are visually selected, but left behind.
If I deactivate the line numbers view, JAWS selects everything correctly. But then it's more difficult for me to work on code files, managing the lines.

NVDA behaviour: in notepad++ it doesn't read line numbers, but selects correctly with proper Braille highlighting. In fact I have learnt to work with both. When I must check lines I turn JAWS on, when I have to select and correct, especially after second or third revision, I use NVDA.
BTW, I think this about Notepad++ is not concerning JAWS but Notepad++ itself.
My 2 cents. Hope it helps.
#blind #braille #bugReport #quill #QuillForAll

I have just opened an issue on Github about Braille in quill - the accessible Windows screen reader-based writing suite. SPOILER: Braille users don't feel the difference between selected and non-selected text.

Issue here:

https://github.com/Community-Access/quill/issues/813

cc @bitsacb @quillforall

#blind #Braille #BugReport #quill #quillforall

@itsfoss Even though this was meant for people who are blind or low vision, maybe people who are sighted might benefit as well. http://quillforall.org #quill #quillforall

It showed the HTML, so I will just post the link. http://quillforall.org #quill #quillforall

Now, let's see what happens if I use HTML to post a hyperlink to Mastodon. <a href="http://quillforall.org">quill for all web site</a> #quill #quillforall

This is a test to see if I can post to Mastodon from Quill. If you are seeing this post, it means it worked. #quill #quillforall

Damn, I'm trying to download latest QUILL editor version 0.6.0 but on the site quillforall.org I still find 0.5.0. #quill #QuillForAll

We're excited to announce that QUILL 0.5.0 Beta is now available!
QUILL is a screen-reader-first writing environment for Windows built around the needs of those who work extensively with text, including people who are blind or low vision, screen reader and keyboard users, writers, students, researchers, developers, and accessibility professionals.
QUILL was designed with accessibility as a core requirement. The result is a powerful writing environment that combines document editing, navigation, review tools, customization, automation, optional AI assistance, and much more.
Curious about QUILL? Join us for QUILL Office Hours on Saturday, June 20, 2026, from 1:00 to 3:00 PM Eastern to learn more, see it in action, ask questions, share feedback, and help shape its future.
Register here:
https://us06web.zoom.us/meeting/register/m7oKZPRKSD-0SBWsHd0YRA#/registration
To learn more about QUILL or download the beta, visit:
https://quillforall.org/
#BITS #Accessibility #QuillForAll

For more about BITS visit:
http://bits-acb.org