I think I would be very confused about how to operate the "edit" screen if the check-boxes were removed.
Perhaps we can add some javascript that grayes out the text boxes until after the check-boxes are enabled? On Thu, Jul 19, 2012 at 11:24 AM, Nolan Darilek <[email protected]>wrote: > Asked this before but never got an answer, and it seems like an annoying > usability issue. > > When I'm editing a commit, why is there both a checkbox and a text field > for adding a new tag to a commit? Would it not make sense to assume that if > I've typed text in the "add a new tag" box, then I intend to add that tag? > If it is left blank, then I don't? > > There is an accessibility issue in that the form labels aren't matched > with entries, primarily because there are no <label/> elements. So this > screen doesn't render terribly well for screen reader users, and it is > unclear whether I am canceling a tag or adding a new one. There are two > solutions: > > 1. Use <label> elements correctly throughout the UI or > > 2. Just drop the checkbox here. > > While <label> everywhere would rock, I think this checkbox is redundant, > so seems like removing it would be the easiest accessibility fix here. > > Thanks. > ______________________________**_________________ > fossil-users mailing list > [email protected].**org <[email protected]> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
