Design comparison
Solution retrospective
Hello i have some questions on the way i can improve.
- I had an hard time to link different column for the backend i could have send an array but i couldn't figure out how. (So the replies doesn't work)
(The backend is kinda long to work cause heroku is pretty long to work)
Community feedback
- @pikapikamartPosted almost 3 years ago
Hi, really nice work on this one. The desktop state looks really great, site is responsive and the mobile state looks great as well. One bug I saw though:
- When you go to mobile state and close the hamburger dropdown and if you go to the desktop state again, the sidebar is now missing.
I don't know about your backend though, I tried seeing the repo but can't find your
api
directory in the nextjspages
folder. Since you are using nextjs, I mean we use different approach but you can use the nextjs api so that you will have a more compact app since the server will be in the same directory with the client-side that can do pretty much do the same thing with using express since next is using express. You could use module to use like a connect-middleware if you're a fan of it ( i'm a fan :> ). But still, hey, it works!Don't know if I could review the whole site since I am really having trouble looking at websites that is almost white, can't really stand it. But here are some suggestions, mainly frontend:
- It would be nice to use the next
.getServerSideProps
orgetInitialProps
either way, it will be much beneficial so that the content will be great for seo since on this one, you are fetching it on the client-side, thus it contradicts next benefits. - I think the
frontendmentor feedback board
is just a single phrase on this and not separated text-element. Because the text "feedback board" is a great text to be heading tag since it gives information on what the section would contain. - Don't use
span
to serve as a container for those sets ofbutton
. Usediv
instead oful
since those are "list" of things. - Also, instead of using
button
, usea
tag for eachall, ui, ux, etx
since they are all living in thenav
tag. But if you insist on usingbutton
, then maybe adding something like anaria-pressed
attribute on each of thebutton
. You will set it totrue
if the user toggles this, this way, screen-reader will give extra information if thebutton
was formerly toggled or selected. header
could be replaced asdiv
on theroadmap
since usingheader
inside another landmark just treats it as a normal tag. You couldheader
for cases likearticle
like that, since they sometimes need a heading.- I think the
roadmap
link on this should go into another page where user can view their progress or something like that. I also would add something like asr-only
span
inside thea
tag so that it will describe more and not justview
text. - Each item in the roadmap could just be a
p
tag and not heading tag since it the first text will be directly read when traversing usinglist
on the screen-reader. - The
nav
inside themain
tag that wraps the blue container is not needed since there aren't any navigational links in there. Adiv
would be better. - For the bulb-icon, you should set a
alt=""
andaria-hidden="true"
on theimg
tag since that is only a decorative image. - The sort-by should be an interactive element on this one.
- I think those
enhancement, feature, etc
below on each of the feedback is just a tag and not an actual link or an interactive element. They just servers as guide for user on where is that suggestions has been added. - Those upvotes should be using
button
and not aspan
. Remember that when creating interactive components, interactive elements must be used andspan
is not interactive. You need to usebutton
with eitheraria-label
orsr-only
element inside it that gives information on what thebutton
will do. - Same for the upvote arrow-icon, hide it using the method above I mentioned about decorative images.
- The heading tag for each of the feedback will be much better to make as the trigger to view the feedback. Right now, clicking the feedback container will redirect me to a feedback, but then again,
div
is not interactive element. You could nest the feedback's title inside of ana
tag:
<h3> <a href=""></a> </h3>
- Reply-icon is decorative as well, better hiding it .
CREATING A FEEDBACK PAGE:
- The arrow-icon on the
go back
link is decorative as well, better hide it. - Since this is an another page, wrap the whole content inside of an
main
tag since that is the main-content of the page and landmark elements helps screen-reader users to navigate the site properly. nav
is not needed inside theform
since it doesn't really contain navigational links.- Again,
span
is not best used as a container forblock
elements,div
would be a much better choice. label
should not be containingblock
elements likeh2
since it is inline. Also you could just directly uselabel
for theh2
text so that it will be more valid and proper markup.- When using
label
make sure that theinput
that you are pointing to is usingid
attribute. Right now, those are missing which makes thelabel
useless since theid
is not present on theinput
. - It would be nice to add more validation on each of the
input
and not just relying on therequired
attribute to make sure the user adds something. Because for example, I could just remove the attribute and submit the form and can can unwanted data in your db. - For the category, again,
span
is not great as a container especially not great for using as toggle in a dropdown. You can just useselect
tag so that it will be more accessible or maybe a create a customlistbox
if you would like. - The dropdown-icon on the category is decorative, hide it.
- Same goes for the feedback detail, using a custom validation would be really nice.
- The
form
is not working? Would be really nice if this was fixed or just made to work:> - The cancel-button should be using
type="button"
. Remember that when abutton
is placed inside aform
element, it defaults totype="submit"
. So imagine if you have a close-button inside theform
without specifyingtype="button"
clicking the close-button will submit theform
. Be aware of this kind of scenarios. - Use
button
for theadd feedback
withtype="submit"
instead ofinput
.
For now, these only since my eyes can't really handle too much screen-whiteness. My eyesss.
Again, great job for this one.
1@SeyBooPosted almost 3 years ago@pikapikamart ahah don't worries i'm feeling the same pain right now.
First of all thanks you for giving me this incredible feedback i will because of you i will improve so much thanks again. (And yeah i couldn't add the repo of the backend so there is a link if you want : https://github.com/SeyBoo/product-feedback-server ).
I wasn't knowing for the server side on Next.js i heard about it but that's it i didn't do so much research on it i should cause it seem pretty nice :) thx you.
all, ui, ux, etx
for those i forgot to add anchor tag and prevent the default action so that's my bad.For the rest thanks i have a tendency to put
header
everywhere cause i'm like yeah it's the head of this div so ... But yeah it's just section i wasn't sure !And thanks for putting me the light on the screen reader part of html i never spent some time on it so know i could thx to you i have learn news tag like
aria-hidden="true"
ect and when to use them so that's a huge improvement to my code.I will upload all of this change during the weekend thanks you a lot ! :)
1
Please log in to post a comment
Log in with GitHubJoin our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord