Orlando Enrique Fiol
At 07:24 PM 1/4/2021, Brian Vogel wrote:
I'd say because your specific needs are not broadly shared, which isI totally get that, which astonishes me even more. Screen readerss entire purpose is reporting screen contents; as such, users should be able to configure the order in which those contents are spoken and change that order on the fly, saving different configurations as needed. I'm surprised that at this stage of NVDA's development, we have to explicitly request this "feature". It would be like requesting a newly-launched car model to contain brakes or a check engine light.
Have you ever looked at the GitHub issues (specifically open ones) forI admittedly have not, since I mainly use JAWS and Window-eyes. I only invoke NVDA when those two can't deliver the goods.
One of the great things about NVDA is that there exists aWhich dismays me even more. A screen reader created largely by and for blind users should have configurable verbosity order baked into its first alfa version.