nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.11k stars 637 forks source link

Error messages for setting row/column headers should note that report tables must be enabled too #4384

Open nvaccessAuto opened 10 years ago

nvaccessAuto commented 10 years ago

Reported by ondrosik on 2014-08-12 10:55 NVDA simply doesn't report column and row headers when I uncheck report tables under document formatting settings. I am not sure if this is intentional, but if yes, we should rewrite the error strings for adding column and row headers littlebit. Now it says that it is necessary to enable reporting of table headers but it should also include that it is necessary enable reporting of tables too.

nvaccessAuto commented 10 years ago

Comment 1 by jteh on 2014-08-13 01:43 It is intentional. You're correct that we should fix the error messages. I don't think this is important enough to break the string freeze for 2014.3, but we should definitely fix this after that. Changes: Changed title from "NVDA doesn't report cel and row headers when report tables checkbox is not checked" to "Error messages for setting row/column headers should note that report tables must be enabled too" Milestone changed from None to next

nvaccessAuto commented 10 years ago

Comment 2 by nvdakor on 2014-08-26 23:30 Hi, This can be done by adding a check to make sure report tables setting is enabled. We also need to tell users via user guide that these two settings must be enabled for header announcements to work. For the message itself, would you want the message to include report tables setting as well? For implementation, let's wait until 2014.3 goes live before working on this ticket.

Adriani90 commented 5 years ago

Actually a link between the check boxes would be enough. So if the one is disabled and other check boxes depend on it, then the dependent check boxes should be unavailable for check or uncheck Action. Is this possible?

josephsl commented 5 years ago

Hi,

Yes via a checkbox event handler. Note that this must be done from the master checkbox, not the dependent ones. Once I get a firm grasp of the issue, I'll cook up a pull request that should (finally) resolve this after four years.

Thanks.