wootz-browser
nvda
wootz-browser | nvda | |
---|---|---|
1 | 29 | |
41 | 1,946 | |
- | 2.1% | |
4.7 | 9.8 | |
3 days ago | about 4 hours ago | |
Dart | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wootz-browser
-
Mozilla, like Google, is looking ahead to the end of Apple's WebKit rule
very interesting times. a few months back, i started contributing to a mobile browser app (OPEN-SOURCE) that has an integrated wallet. I think browsers are going to have many more usecases than just browsing the web.
Payments is going to be a key enabler - web2 or web3.
https://github.com/wootzapp/wootz-browser
nvda
-
ESpeak-ng: speech synthesizer with more than one hundred languages and accents
After some brief research it seems the issue you're seeing may be a known bug in at least some versions/release of espeak-ng.
Here's some potentially related links if you'd like to dig deeper:
* "questions about mandarin data packet #1044": https://github.com/espeak-ng/espeak-ng/issues/1044
* "ESpeak NJ-1.51’s Mandarin pronunciation is corrupted #12952": https://github.com/nvaccess/nvda/issues/12952
* "The pronunciation of Mandarin Chinese using ESpeak NJ in NVDA is not normal #1028": https://github.com/espeak-ng/espeak-ng/issues/1028
* "When espeak-ng translates Chinese (cmn), IPA tone symbols are not output correctly #305": https://github.com/rhasspy/piper/issues/305
* "Please default ESpeak NG's voice role to 'Chinese (Mandarin, latin as Pinyin)' for Chinese to fix #12952 #13572": https://github.com/nvaccess/nvda/issues/13572
* "Cmn voice not correctly translated #1370": https://github.com/espeak-ng/espeak-ng/issues/1370
-
Custom Forms with Web Components and "ElementInternals"
NOTE: There is an accessibility bug in Safari and NVDA where labels are not properly associated to Form-Associated Custom Elements for screen readers. They are read fine with VoiceOver in Chromium browsers (Chrome, Edger, Brave, etc.) and Firefox on Mac and MS Narrator and JAWS on Windows. As a workaround, you can continue including your labels within your elements.
-
Does NVDA have a first letter nav feature like VoiceOver has?
If that doesn't meet your need, I would encourage you to file an issue on our issue tracker at: https://github.com/nvaccess/nvda/issues
-
jaws vs nvda on a touch screen device
We don't have a huge number of users relying on touch, and we know NVDA could be improved in this area, so we are always keen for feedback. The best place is to file an issue at: https://github.com/nvaccess/nvda/issues (Happy to have discussion here, but just in case I miss it, and in any case someone will still need to create an issue for any action items eventually).
-
Outlook 365 NVDA table-reading question
If you think this is an issue with NVDA, you can open an issue on Github.
-
How old is libre office work with NVDA?
It's getting better. We originally didn't have any contact with anyone from the LO community to try to get any help from their side. But in recent years we've had support from a couple of LO developers and community members and support for LO is improving. As always though, if you use it and encounter any issues with NVDA, please do report them to us either in a message or email, or create an issue on our GitHub page: https://github.com/nvaccess/nvda/issues If it is a LibreOffice issue (rather than NVDA) then they also have an issue tracker: https://bugs.documentfoundation.org/ And often it is hard to tell, so feel free to report it to us and we can ensure it gets reported with LO as well (or vice-versa).
-
Questions about NVDA and text selection/editing
Even if you can't contribute to the code itself, this level of technical knowledge of the issue would definitely be worth writing up in an issue on https://github.com/nvaccess/nvda/issues
-
Mozilla, like Google, is looking ahead to the end of Apple's WebKit rule
And there's still a lot of work for the third-party tools to do, too.
https://github.com/nvaccess/nvda/issues/5186#issuecomment-20...
https://bugzilla.mozilla.org/show_bug.cgi?id=381888
https://github.com/nvaccess/nvda/pull/9933
I read somewhere that screen readers look for a flashing vertical line, to detect the caret position in systems that don't expose it via the OS's APIs. I can't find a reference for that right now, though.
-
NVDA question?
Coming in late and without much new info I'm afraid. Good question though. I must admit, I'm not sure if we considered this situation. The one thing I can suggest, is if you are interested in the functionality, is creating an issue on our GitHub tracker here: https://github.com/nvaccess/nvda/issues
-
Getting help with NVDA
- If you are confident you've found a bug and would like to report it, we have a GitHub page here: https://github.com/nvaccess/nvda/issues
What are some alternatives?
cloudpilot-emu - A PalmOS emulator for the web
ccd - Edge first cd replacement tool for Windows cmd shell.
sse3-emu - Emulate an SSE3 CPU on a system without SSE3 (WIP)
Draft.js - A React framework for building text editors.
ProseMirror - The ProseMirror WYSIWYM editor
aria-at - Assistive Technology ARIA Experience Assessment
NDA - basic tool to encrypt and decrypt single files.Working, but still under construction.
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
Visual Studio Code - Visual Studio Code
lucia - An audio game engine written in python
liblibinject - Library injection for GNU/Linux