@pikapikamart
Posted
Hey, awesome work on this one. Layout in desktop looks great, it is responsive and the mobile state looks great as well. Though I suggest lowering down the breakpoint since right now, at 114px it already shows the mobile/table layout which is too big for those and desktop layout could use more those screen-time.
It is great having to see lots of others giving feedbacks, just going to add some suggestions as well:
- Right now, the error works but is only limited for sighted users right now. To make the form more accessible:
- the error-message for each
input
should have anid
attribute. - When
input
is wrong add anaria-invalid="true"
to inform a user when they navigate on theinput
that it is invalid. - When
input
is wrong add anaria-describedBy
attribute on it, the value of this attribute will be theid
of each error-message. This way, they will know what kind of error they had made based on the text-content of each error-messages. - Making it more accessible, have an
aria-live
element. This element will announce if the form submitted has successfully submitted or if it has any errors. This way, user will be informed right away about errors.
- the error-message for each
A pseudocode of steps 1-3 looks like:
if ( input is wrong )
input.setAttribute("aria-invalid", "true");
input.setAttribute("aria-describedBy", id of the error-message);
else
input.removeAttribute("aria-invalid");
input.removeAttribute("aria-describedBy");
To implement the aria-live
have a look at this simple accessible form that I created. This implemented the other attributes I mentioned as well, see the structuring and the manipulation of the attributes.
If you have any queries, just drop it here okay. Aside from those, great work again on this one.
Marked as helpful