Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upRadio buttons in Java applications always announce position information as 1 of 1 regardless of the number of radio buttons #3754
Comments
This comment has been minimized.
This comment has been minimized.
|
Comment 1 by Michael Curran <mick@... on 2014-01-08 08:44
|
This comment has been minimized.
This comment has been minimized.
|
Comment 2 by Michael Curran <mick@... on 2014-01-22 06:23
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 3 by Michael Curran <mick@... on 2014-02-07 05:31
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 4 by mdcurran on 2014-02-07 05:36 |
This comment has been minimized.
This comment has been minimized.
|
Comment 5 by mdcurran on 2014-02-12 02:44 |
This comment has been minimized.
This comment has been minimized.
|
Comment 6 by Michael Curran <mick@... on 2014-02-12 02:47
|
This comment has been minimized.
This comment has been minimized.
|
Comment 7 by Michael Curran <mick@... on 2014-02-12 02:48
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 8 by mdcurran on 2014-02-12 02:54 |
This comment has been minimized.
This comment has been minimized.
|
Comment 9 by mdcurran on 2014-02-12 03:01 |
This comment has been minimized.
This comment has been minimized.
|
Comment 10 by Michael Curran <mick@... on 2014-02-27 04:50
Changes:
|
This comment has been minimized.
This comment has been minimized.
|
Comment 11 by mdcurran on 2014-02-27 04:57 |
nvaccessAuto commentedJan 8, 2014
Reported by mdcurran on 2014-01-08 03:59
Currently, NVDA assumes that all radio buttons are direct children of the same parent, and that the only children of the parent are in deed radio buttons. Therefore, NVDA uses the child index and the parent's child count as the 'ordinal' or position information for each radio button.
Clearly this is not at all useful if the radio buttons are within separate panels etc.
We could either 1. no longer expose position info for adio buttons (especially if its 1 of 1), or 2. Come up with a complex huristic that searches for and counts radio buttons around the current radio button, and calculates suitable position information. However, it is debatable as to how high up the parent structure the search should go. Surely there are examples where there are two groups of radio buttons within the same frame?
Therefore, for best performance and suitability for as many situations as possible, we should simply stop exposing this position information for Java radio buttons.