#braille — Public Fediverse posts

These are the elevator buttons where I work.

Both have blind-accessible Braille text.

The down-arrow text means "down".
The up arrow text is also four characters, so, what could it mean?
Uppp?
High?

NO!

It means: Someone just took the down button, turned it 180 degrees, and slapped it on. 😅

So, at least from my amateurish knowledge...it means nothing.

Sure, you can abstract that the "not down" button means up. And I also think the arrows themselves can easily be felt but...that's damn stupid?

That...that's not the way stuff is handled, right? You can't just turn Braille upside down?!

I really wonder if I should...report this somewhere, but I have no clue if we have any accessibility responsible person. 😅

#Accessibility #Braille

These are the elevator buttons where I work.

Both have blind-accessible Braille text.

The down-arrow text means "down".
The up arrow text is also four characters, so, what could it mean?
Uppp?
High?

NO!

It means: Someone just took the down button, turned it 180 degrees, and slapped it on. 😅

So, at least from my amateurish knowledge...it means nothing.

Sure, you can abstract that the "not down" button means up. And I also think the arrows themselves can easily be felt but...that's damn stupid?

That...that's not the way stuff is handled, right? You can't just turn Braille upside down?!

I really wonder if I should...report this somewhere, but I have no clue if we have any accessibility responsible person. 😅

#Accessibility #Braille

The discussion on In Touch this week about the future of #braille left me feeling a bit annoyed. I feel a rant coming on.

The discussion on In Touch this week about the future of #braille left me feeling a bit annoyed. I feel a rant coming on.

Visitors to our booth got hands-on with our newest products—the Orbit Flow and Strata—as well as many of our classic devices. We loved your feedback and can't wait to see more of you this summer at the ACB and AER conferences! #AssistiveTechnology #Braille #Accessibility

Visitors to our booth got hands-on with our newest products—the Orbit Flow and Strata—as well as many of our classic devices. We loved your feedback and can't wait to see more of you this summer at the ACB and AER conferences! #AssistiveTechnology #Braille #Accessibility

We had a fantastic time exhibiting at the NFB Convention in Austin, TX! It was great connecting with the community, educators, and accessibility professionals from across the country. Thank you to everyone who stopped by our booth! #NFB26 #Accessibility #Braille #OrbitResearch

Good news: the European Commission (Innovation Radar) recognises InsideVision as a "Key Innovator" for two innovations developed within the Horizon Europe ABILITY project:

— a full-page refreshable display for tactile graphics and Braille (with CEA)
— a localised haptic-feedback tablet (with CEA and OFFIS)

Funded by the European Union.

#Accessibility #Braille

Good news: the European Commission (Innovation Radar) recognises InsideVision as a "Key Innovator" for two innovations developed within the Horizon Europe ABILITY project:

— a full-page refreshable display for tactile graphics and Braille (with CEA)
— a localised haptic-feedback tablet (with CEA and OFFIS)

Funded by the European Union.

#Accessibility #Braille

Fiction plot announcement for future @plusbrothers stories as soon as the site will be ready. But we'll announce (both in Italian and English) the various plots on Mastodon.
Detectives are going to pick up killer's hint through messages on the Internet. This is not original, true.
Anonymous, VPN, and stuff. But, they're not anonymous at all.
Not for networking related clues, but the clues is in writing!
Inspired by an experience happened to me.
Using Braille Screen Input, the typing method for blind users to write on iPhone/iPad touch screen. Right hand manages 3 (or 4) dots, according to screen size, iPad has 8 dots Braille as well. And left hand manages the other combination of dots on the other side; every finger corresponds to a dot. But, if you have an injured hand, you lose control of them. A blind person using BRaille Screen Input is recognizable by another one using same method, or by very close folks knowing, even vaguely, the system. So, the villain starts to write "s" in place of "t", "k" in place of "o", "l" in place of "r"...
Means that character has their right hand injured somehow, and only a person very confident with blindness could know it; main detective is VERY connected to a blind person but he's positively biased (double meaning on "positive" very intended). Villain is death threatening main character, everyone thinks of a stranger, a monster, one politician who wants to train the sentient HIV virus for military purpose.
But, in the end, criminal betrayed themselves by writing!
Sentient virus was aware about villain's blindness, but humans don't believe that a blind person could threat and attempt to disrupt a community.
The blind villain wants to capture sentient virus to make a sophisticated and non-invasive guide for themselves...
Human umiliation in front of virus intuition. Who knows if humans are able to save Patient Zero and their very own virus.
#braille #crime #FediFiction #spoiler

Fiction plot announcement for future @plusbrothers stories as soon as the site will be ready. But we'll announce (both in Italian and English) the various plots on Mastodon.
Detectives are going to pick up killer's hint through messages on the Internet. This is not original, true.
Anonymous, VPN, and stuff. But, they're not anonymous at all.
Not for networking related clues, but the clues is in writing!
Inspired by an experience happened to me.
Using Braille Screen Input, the typing method for blind users to write on iPhone/iPad touch screen. Right hand manages 3 (or 4) dots, according to screen size, iPad has 8 dots Braille as well. And left hand manages the other combination of dots on the other side; every finger corresponds to a dot. But, if you have an injured hand, you lose control of them. A blind person using BRaille Screen Input is recognizable by another one using same method, or by very close folks knowing, even vaguely, the system. So, the villain starts to write "s" in place of "t", "k" in place of "o", "l" in place of "r"...
Means that character has their right hand injured somehow, and only a person very confident with blindness could know it; main detective is VERY connected to a blind person but he's positively biased (double meaning on "positive" very intended). Villain is death threatening main character, everyone thinks of a stranger, a monster, one politician who wants to train the sentient HIV virus for military purpose.
But, in the end, criminal betrayed themselves by writing!
Sentient virus was aware about villain's blindness, but humans don't believe that a blind person could threat and attempt to disrupt a community.
The blind villain wants to capture sentient virus to make a sophisticated and non-invasive guide for themselves...
Human umiliation in front of virus intuition. Who knows if humans are able to save Patient Zero and their very own virus.
#braille #crime #FediFiction #spoiler

I just spent a ridiculous amount of money on #Braille coloring books. I regret nothing! That's it, that's the post!

I just spent a ridiculous amount of money on #Braille coloring books. I regret nothing! That's it, that's the post!

Big news for my UK readers! No Sight Required: The Blind User's Guide to AI is headed to the RNIB Library. The ebook is going up on RNIB Bookshare, and a braille edition is in the works, with DAISY audio to follow.
RNIB Library is completely free for blind and partially sighted readers in the UK. That is exactly where this book belongs.
You matter, every day!
#Blind #Accessibility #AI #ScreenReader #NVDA #JAWS #RNIB #Braille #NoSightRequired

Big news for my UK readers! No Sight Required: The Blind User's Guide to AI is headed to the RNIB Library. The ebook is going up on RNIB Bookshare, and a braille edition is in the works, with DAISY audio to follow.
RNIB Library is completely free for blind and partially sighted readers in the UK. That is exactly where this book belongs.
You matter, every day!
#Blind #Accessibility #AI #ScreenReader #NVDA #JAWS #RNIB #Braille #NoSightRequired

My #Monarch is now flying on the Internet with all of the latest updates. Navigation and reading are improving tremendously, thanks to the helpful tips from more seasoned Monarch users. I keep looking for the cursor routing buttons that aren't there. Lol Just wanted to post an update and say thanks again for the encouragement. #Blind #Braille

Your manuals. Three formats. Zero limits. 🚀

insideONE+ and insideSUPRA now have their manuals in:
📄 DOCX
📕 PDF
🌐 HTML → readable anywhere, on any device

Link in bio 🔗 (or right below 👇)

🔹 insideSUPRA: https://insidevision.fr/produits_braille_bloc_notes_insidesupra_EN_01.html#supports
🔹 insideONE+: https://insidevision.fr/produits_braille_tablette_insideone_plus_EN_01.html#supports

#InsideVision #Braille #Accessibility #Innovation #insideONEPlus #insideSUPRA #TechInclusive #VisualImpairment

Your manuals. Three formats. Zero limits. 🚀

insideONE+ and insideSUPRA now have their manuals in:
📄 DOCX
📕 PDF
🌐 HTML → readable anywhere, on any device

Link in bio 🔗 (or right below 👇)

🔹 insideSUPRA: https://insidevision.fr/produits_braille_bloc_notes_insidesupra_EN_01.html#supports
🔹 insideONE+: https://insidevision.fr/produits_braille_tablette_insideone_plus_EN_01.html#supports

#InsideVision #Braille #Accessibility #Innovation #insideONEPlus #insideSUPRA #TechInclusive #VisualImpairment

Mit den Umbaumaßnahmen in #friedrichskoogspitze kam auch ein Stück weit #inklusion in den Ort.
* Braille an den Geländern
* Bodenindikatoren an allen Treppen
* Beleuchtung für die dunkle Jahreszeit
... und bestimmt noch weitere tolle in diese Richtung gehende Dinge an die ich jetzt nicht gedacht habe 🤗

#friedrichskoog #dithmarschen #schleswigholstein #nordsee #nordseeküste #braille #bodenindikatoren #beleuchtung

Well, that was an unexpected surprise indeed. I wish I'd known it was coming. I walked outside to find a small rectangular shaped cardboard box and a larger padded envelope waiting for me. I hadn't bought anything so had no clue what it could be. Turns out it's the #HumanWareE-Reader from the #LibraryForAccessibleMediaOfPennsylvania. So, dear citizens of Pennsylvania if you requested a new E-Reader keep an eye on your mailbox package drop or front step for one. #Braille

Well, that was an unexpected surprise indeed. I wish I'd known it was coming. I walked outside to find a small rectangular shaped cardboard box and a larger padded envelope waiting for me. I hadn't bought anything so had no clue what it could be. Turns out it's the #HumanWareE-Reader from the #LibraryForAccessibleMediaOfPennsylvania. So, dear citizens of Pennsylvania if you requested a new E-Reader keep an eye on your mailbox package drop or front step for one. #Braille

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 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

La #RAE modificará la definición de "#leer" para incluir #Braille
#lectura
El cambio supone un importante gesto de #inclusiónlingüística y social, especialmente cuando el sistema Braille continúa siendo una herramienta esencial para millones de personas en todo el mundo

https://fuentesinformadas.com/la-rae-modificara-la-definicion-de-leer-para-incluir-la-lectura-en-braille

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

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

Visit Orbit Research at booth A12 at the NFB Convention to experience the new Strata 20 Pro, Strata 40, Strata 40 Pro, and Orbit Flow 40: Orbit’s newest single-line piezo braille products for reading, writing, connectivity, and everyday productivity. Touch it. Try it. Feel the difference.

#NFB26 #OrbitResearch #Braille #AssistiveTechnology #Accessibility #RefreshableBraille

Does anyone out here know the exact formatting of #NLS #Braille books? I'm trying to convert one to eBraille using the tool by #APH but everything I've tried just results in this river of two spaces down the left side with initial characters being cut off the beginning of lines. #Monarch