@menelion @fubsepude There definately are things that can be improved and are slowly improving for example a few years ago there was an issue browsing huge lists of items that's no longer such an issue any more. The webbrowser browse navigation is improving all the time. The accessibility labels and keyboard navigation in the settings app of @gnome is much improved. Gnome calendar is keyboard accessible. The default files app has incremental search that not only searches at the begining of file names but everywhere, we have configurable keyboard shortcuts for launching our apps and scripts, Access to reading PDF files has improved, I'm not using this but I know there are sound schemes for notifying desktop events. And so on and so on. Windows software is improving too.
As for the braille I don't have a braille display but our screen reader #orca is powered by the same translation engine your screen readers #nvda and #jaws are powered on windows, that's #liblouis.
Orca has flat review, sticky focus / sticky browse mode, application specific settings, settings profiles, progress bar beeps, auto restart when it freezes or crashes, ability to display flat review content in a window, object navigation, reconfigurable keyboard shortcuts, ability to present clipboard content, reporting system information such as ram / / cpu usage, It's now getting speech screen and braille screen output usefull for #a11y testing, browse mode features outside web content to combat bad authoring to an extend, Automatic language switching for web and document content, And perhaps other usefull features I'm not thinking of right now.
It's rich ecosystem, our screen reader is very powerfull too.
The best advice I can give you for all environments is know your tools, screen reader in particular and you should be fine.

The older version uses #liblouis's data files, but assumes liblouis is already installed. It also assumes that liblouis is installed in one particular place, so isn't very portable - it will fail at the whim of a platform's package manager or depending on whether you installed liblouis via the package manager or from source. The new version bundles the data files with the code and can always find them, so it works no matter whether you're on #Linux, a Mac, #IllumOS, or anything in between. 2/3

It's this <https://github.com/larsbjorndal/App-Brl2Brl/pull/1>. The purpose is to bundle #liblouis's data with the code instead of assuming that the user has installed it separately, and also installing it at a known location instead of wherever the platform-specific package management tool decides to put it. I'm planning on creating Alien::liblouis and some XS jibber-jabber later to do the job properly, but this is a decent improvement for now that will make it more portable.

@menelion @deafblind So with #liblouis installed and available on the path, I can call it like this:
echo "Merry Christmas" | lou_translate unicode.dis,en-us-g2.ctb
And it will output
⠠⠍⠻⠗⠽⠀⠠⠡⠗⠊⠌⠍⠁⠎

For most braille codes liblouis is a great source so we can be sure it's going to be right. Just change your table when calling.