Latest solutions
Rating Component - Remix Run TypeScript Tailwind
#react#remix#tailwind-css#typescriptSubmitted almost 3 years agoResponsive Advice Card with Next.js
#fetch#next#react#tailwind-css#accessibilitySubmitted about 3 years agoResponsive flex component with text animation
#next#react#tailwind-css#typescript#accessibilitySubmitted about 3 years agoFylo Data Storage Component - Next.js Mantine.dev
#accessibility#next#tailwind-css#reactSubmitted almost 3 years agoNext.js TailwindCSS TypeScript Responsive Four Card Layout
#accessibility#next#react#tailwind-css#typescriptSubmitted over 3 years ago
Latest comments
- @zofiadobSubmitted over 3 years ago@MikevPeerenPosted over 3 years ago
Hey 👋
Try not to add alt text to meaningless icons like the Facebook icon, a screenreader has no use for that.
Also try to diversify your html elements, for example using headers and using lists for the different data.
Other than that good job 👏
Marked as helpful0 - @AliRadmaneshSubmitted over 3 years ago@MikevPeerenPosted over 3 years ago
Hey 👋
Good job 👏
Try to keep in mind when using alts text if it adds any value to a screenreader for example the background images do not. In that case you can use alt="" as that would be better.
Also as a improvement you could've used a ul list instead of divs for the footer section.
0 - @b-a-merrittSubmitted over 3 years ago@MikevPeerenPosted over 3 years ago
Hey 👋
Looks good to me, the only thing I can think about is that you could perhaps have predefined arrays with key value pairs this way you can just select your element for example for the housselection like:
Sethouse = Array[num]
And perhaps it would be cleaner to have two states one for the name and image.
Also useStates should always be ordered at the top so the function in between is a no go.
I would also have maybe a custom hook for your localstoragd to handle that.
But for the rest good job
Marked as helpful1 - @xxxcrisxxxSubmitted over 3 years ago@MikevPeerenPosted over 3 years ago
Hey 👋
Good job finishing this one 👏
My only comment would be to not skip headings as you are now going from h1 to h3 you should try to use h2 in that case.
0 - @xs30snwSubmitted over 3 years ago
Time Tracking Dashboard w/ Tailwind, Webpack, PostCSS and json-server
#tailwind-css#webpack#sass/scss@MikevPeerenPosted over 3 years agoHey 👋
Try to make use of headers instead of using paragraphs for everything. Also try to add alt text to images that require it, if they don't require it use alt="".
For your question I personally used buttons for the interactions but a list would also be fine imo.
Marked as helpful1 - @TelrodanSubmitted over 3 years ago@MikevPeerenPosted over 3 years ago
Hey 👋
My only comment would be to add more descriptive alt txt for accessibility a d also to remove it for non saying images like the eye icon, for those your can use alt=""
0