GNOME Bugzilla – Bug 369292
gcalctool doesn't speak the new result when the "=" button is activated..
Last modified: 2006-11-03 21:18:38 UTC
Please describe the problem: This is an a11y bug for calculator. Steps to reproduce: 1. Invoke orca and calculator. 2. Click buttons to make a calculation. 3. Press Tab to the result. Actual results: The focus can not be put on the calculation result, this makes result is not accessible. Expected results: The result should be accessible. Does this happen every time? Yes. Other information: This bug can be found with gcalctool 5.8.24 and orca 2.17.1.
The way that the Orca gcalctool script is designed is that when the display area is updated, it's new value is spoken and brailled. The gcalctool display area is deliberately made read-only so that the user cannot randomly change the contents. I do not consider this a bug and I'm closing as such.
The other point I should make is that in arithmetic operator precedence mode, the Return key is a toggle between the result and what you user last typed in. If the user forgot what was being displayed, then they can hit Return twice, and it will be re-spoken and re-brailled.
Yes, the result will be updated and displayed in brlmonitor, but it failed to be reported in speech while operating the num-pad. If tabbing to the number button, the number and operator can be heard when he is typing, but the result is not accessible. This seems to be a conflict I think. I could find this with both orca 1.0.0 and 2.17.1.
That's a totally different bug Tim. Reopening and adjusting the summary (and severity) accordingly.
Transferring to the Orca team for further evaluation.
Created attachment 75963 [details] [review] Patch to fix the original problem. Will politely mentioned that the problem was this: If you tab (or arrow) around to the "=" button and then use the spacebar to activate it, then you do not hear the result spoken. This isn't a numeric keypad problem after all. The attached patch fixes that original problem.
Patch checked into Orca CVS HEAD. Closing as FIXED. Tim, if you were refering to a different problem, please file a new bug. Thanks.