Hi Joanie, One issue is that if we were to say indeterminate on a range we don't know if that is the current value or the max value - at least in the case of group position. If we are to define indeterminate we need to state what it applies to.
Rich Rich Schwerdtfeger From: Joanmarie Diggs <[email protected]> To: [email protected] Date: 09/29/2014 11:44 AM Subject: [Accessibility-ia2] STATE_INDETERMINATE as a means to indicate things like unknowable set size? Sent by: [email protected] Hey all. Given a large data set where the set size is not known (e.g. gmail's "1 of about 120"), we need a way to be able to communicate the known set size along with the fact that the total is not (yet) known. One proposal has been to expose this via something like "120+". The problem with that is it means most of the time set size is a number, except for when it's a string one needs to parse. Seems like a less-than-ideal situation to me. In ATK, we happily have STATE_INDETERMINATE which seems like it would fit the bill nicely, making it possible for quantifiable things like set size to remain numbers and giving implementors a means to indicate the size is indeterminate. In chatting with Alex Surkov about this, he seemed to think this was a reasonable approach. The only "problem" was that the ATK docs specifically said this state was for tri-state checkboxes in the mixed state. I just solved that with new docs. This change has just been committed. [1] So we're good. What can we do to make this happen in IA2. After all, Surkov doesn't like it when our two platforms diverge. ;) --joanie [1] https://bugzilla.gnome.org/show_bug.cgi?id=737602 _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
