-
-
Notifications
You must be signed in to change notification settings - Fork 70
Use more accessible ui elements for family_requests form #136
Comments
Taking a step back from this and chatting with @armahillo I think we should go the other direction on this and make the fancy slider toggles into checkboxes. There are some accessibility concerns with these toggles. (or we can pick a different ui element to use here that makes more sense.) |
I have just set up my environment to give this issue a try, and am having issues submitting a family diaper request. I created a guardian with a child, but am getting the following internal server error:
It looks like maybe I don't have |
@VickiShaw94, do you also have |
@benreyn I realized I hadn't seeded the database, but after fixing the Here are the request params:
And local variables:
|
Hey @VickiShaw94 sorry for the delay! Have you set your environment variables? |
@seanmarcia sorry I've been busy lately :D how can I get write access to submit a pull request? |
On the family_requests/new form we use a fancy toggle instead of a vanilla checkbox for theinclude?
column of the table. It would be awesome to use the same toggles for the checkboxes for active and archive on the children form as we do there. Currently we have plain html checkboxes.These fancy on off mobile style toggles on the Family requests form cannot be accessed by keyboard. Also for a user who is colorblind, it might be unclear which way is "toggled on" vs "toggled off"
I think reverting these to vanilla checkboxes and changing the title of the column to "Include in request?" would do the trick. Also, currently it looks like when these toggles are clicked they send a request in the background to update the childs
active
column. I think this could be confusing if someone were to start the creation of a family request and abandon it before submitting, (updating the children to inactive with little feedback to the user) I think these updates are fine to do but we should probably wait until the form is submitted and the request created to finalize it.The text was updated successfully, but these errors were encountered: