A small fix!
I wanted to, after signing the petition, you pass a mini survey that I created on this forum, but it turned out that it is not displayed.
So that it will not.
in spite of this, I will continue to keep track of the company, in support of this petition.
at the end of July, I will report the results.
if someone is interested, you can write the results in this topic.
do this after the petition has reached 1000 subscribers.
and she will go to google for consideration.
Thank you for your attention and support.

Apple's Braille support is now 100% spot-on from what I can tell. I've had no issues as of late. So I'm surprised that this is still an issue on the Android system...ten years after accessibility became mainstream.

It's one of the primary reasons I'm still on iOS: I love Braille, and a turn-off even in NVDA for me was its lack of solid Braille support.

Re: post 3, @Ethin I've heard this from multiple other people as well that Google has downsized their access team. And no, NVDA's Braille support is cute at best, at least with the displays I've used. Your premise of using Java to contributed is also flawed since not everyone is a developer, so you can't expect everyone to jump in and start coding. I've seen this type of attitude from many people as of late and it's simply not how the world works. In fact, FS used to use the same argument: if something is broken, you can script it, so that alleviates us from responsibility. Heck, even GW Micro used that argument when they came out with their app development stuff.

It's easy for you to write such things but you fail to see it from the average user's perspective.

Lol, just listen to the interviews Victor Tsaran did a few times. He specifically says that other Android teams have their own priorities. So, accessibility, very apparently, isn't one of them? The platform, aside from braille for a second, won't allow TalkBack to implement multi-finger gestures, after a good ten years of work? Nah, the Android developers just don't care, and the accessibility people don't seem to have the power to change that. Also, if you're such a big bad coder, Ethin, why not fix braille yourself, and add in multi-finger gesture support into the accessibility API while you're at it? After all, its not that hard, right? After all, anyone can do it, right? I'm so tired of being told to "just fix it yourself." "Oh Linux is great, and if you have a app you want make it yourself! Open source rules because everyone can make anything!" and "you want some thing we deem unimportant in a screen reader? Make it yourself!" Back to Android, I'm sure Google would gladly accept your commit, and maybe even thank you privately for improving accessibility, doing what they've not been able to do for 10+ years! Like, you must be some kind of genius or something if our engineers couldn't even figure it out. All this makes me proud to be an iPhone owner, that I've given my dollars to a company that at least tries to care about accessibility, and gets it mostly right.

Again, can someone explain what exactly the problem is with NVDA or android and Braille? is your display just not supported and that makes such a big chaos around your personal and emotional life?

When it comes to Braille from Google, your best off using ChromeVox with a Chromebook, if ya want Braille.
Also, have a look over at This AppleVis Blog Entry (particularly startting with "comment 39" onwards,) as the discussion between IOS and Android, is quite inspiring!

You cannot even do the most basic thing, which is turn the speech off and use braille. If you want to go into detail, brailleback needs to be set as your default keyboard each time you want to use it to input on your display, and when you disconnect it then you have to change keyboards again. Hopefully this at least should be possible to resolve in Android Q. Scrolling also used to be very buggy back when I tried it. It all sounds great on paper, Google has 2 channels to report accessibility bugs, but the reality is most things you report there will be read by somebody who never used TalkBack longer than 15 minutes and will have no idea how to reproduce something. All this comes from a 5 year Android user. With Oreo, when Victor stepped in it really seemed like Android will massively improve. Here we are, just a year ahead and we're back to how it was in pre Oreo days. We get a TalkBack beta with no info on what bugs were fixed, Youtube is constantly breaking accessibility with every update, web browsing is a lot of fun with focus jumping all around, and in general issues that any blind full time Android user would notice in a few days. No, you can't contribute. A flawed argument with no evidence to back it up. How do I contribute to TalkBack when the last open sourced version is out of date and when Google is not accepting pull requests? That source is there just for reading, not so people can actually contribute. Simple translation pull requests were not merged, a pull request by a member of LineageOS team was not merged, so I can only thank Google for making it useless to contact custom rom developers and ask them to fix accessibility shortcut on their setup. Brailleback even as far as I know is not open sourced at all, however I could be wrong on that since I didn't check. If it is, great, but it probably works on the same principle as TalkBack, they will update the sources once per year and that's it. There's a reason Samsung created voice assistant from TalkBack's source and didn't contribute, it took Samsung one Android version to make multy finger gestures work. It took Samsung one Android version to inspire Google to later add accessibility shortcut, dark screen to TalkBack and god knows how many other features. This is not bad at all, however it should not stop there. Android is accessible, that's for sure, but it's a major payn for some tasks including web browsing, and add to this that almost any list having over 100 items is painfully slow to brows with TalkBack and you got the root of the problem. Google needs optimisation, nothing else.

The only screen reader that lets you "Mute" the speech while using braille on "Pure" Android, sadly is Samsung's own "Voice Assistant."

Now, if we are talking Braille Display Support using the VoiceView screen reader from Amazon, way nicer experience I hear!
(Links above take you to their respective "Fire Tablet Accessibility" help page.

Just because those of us that know how to code can fix code we don't like doesn't mean everyone should be told to fix broken software themselves. As I pointed out earlier, FS adopted this mentality at one point and so did GWMicro, and I didn't like it then, either. It absolves the companies--who hire people to fix problems--of the responsibility of fixing them, because well, the community, if it weren't so damn lazy, would just fix it itself. See my roofer analogy above.

Plus, we go right back to the argument that not everyone is a coder, so you can't just expect every person and their mom to jump in and start coding on such a complex project as Android. It's simply not realistic. Most of these people don't even know what a linked list is. Just like hardware is out of the league of many of us, so is software to many others. If DYI was so easy, nowadays everyone and their dad would be a plumber. But...surprise! We still have hardware stores around to do hardware maintenance.

So, again, it's easy for people like you to just come here and write "well...just fix it yourself," but this idea is simply not realistic because now you're assuming everyone has the domain-specific knowledge you do. So you can't use that catch-all as a solution to every open-source problem you come across.

And this is definitely a younger mentality we've got going on here because it's idealistic and based on a premise that simply doesn't hold in reality. I used to think the same way when I was your age, until I realized that people go to school for different reasons--and still more don't go to post-secondary at all.

Also, reading backwards, I don't think anyone said Android is shit. We all have raised accessibility concerns and the lack of a true access effort in Android, which, even I, (not being an Android user) have heard many Android users themselves complain about.