Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
26
Comments
425

darryncodes

@darryncodesWiltshire, UK6,350 points

Working hard to change career.

I’m currently learning...

JavaScript, React 🔜 Node.js & Next.js

Latest solutions

  • Age calculator app - React & Styled components

    #accessibility#react#styled-components

    darryncodes•6,350
    Submitted about 1 year ago

    It'd be interesting to know if there is a more elegant way to handle the form validation on submission - there are a lot of if conditions to handle all the possible scenarios.


    0 comments
  • FAQ accordion - HTML, CSS, & Vanilla JavaScript

    #accessibility

    darryncodes•6,350
    Submitted about 1 year ago

    Any accessibility specific feedback would be very welcome.


    1 comment
  • Social links profile - Vanilla HTML, CSS & @keyframes

    #accessibility#bem

    darryncodes•6,350
    Submitted over 1 year ago

    0 comments
  • E-commerce product page - Tailwind CSS, React, Framer Motion & Vite

    #accessibility#framer-motion#react#tailwind-css#vite

    darryncodes•6,350
    Submitted about 2 years ago

    1 comment
  • URL shortening API landing page - React, React Router, Bootstrap, SCSS

    #accessibility#bootstrap#react#react-router#firebase

    darryncodes•6,350
    Submitted about 2 years ago

    0 comments
  • Fylo dark theme landing page - HTML, Tailwind CSS & JavaScript

    #accessibility#tailwind-css

    darryncodes•6,350
    Submitted over 2 years ago

    1 comment
View more solutions

Latest comments

  • Javier Alberto Vásquez Suárez•700
    @JaviVaSu
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I am proud that I can make the designs more easily.

    What challenges did you encounter, and how did you overcome them?

    Aligning the content was what was most difficult for me

    What specific areas of your project would you like help with?

    In the management of the FlexBox and Grid

    Responsive Social Links Profile.

    1
    darryncodes•6,350
    @darryncodes
    Posted about 1 year ago

    Hi Javier,

    Glad to hear the designs are getting easier - keep going!

    A few bits of feedback to help match the design a little more:

    • add min-height: 100vh; to your <body> and remove the margin top/bottom on the .portafolio class to centre the design nicely in the veiwport
    • add background-color: hsl(0, 0%, 12%); to .portafolio, you'll need some padding and border-radius too
    • add background-color: hsl(0, 0%, 20%); to your buttons
    • use cursor: pointer; on the buttons to help indicate visually you can interact with them

    A couple of pointers regarding semantic html:

    • consider using a <main> for this element .portafolio
    • try nesting your a's in a ul list
    • it's not valid HTML to wrap button's with a tags. You probably just need the links and not the button on this design

    I hope this helps. Happy coding 🤙

  • Zoulanders•380
    @AlexDDevv
    Submitted over 2 years ago

    Chall using Flex, Javascript and responsive

    1
    darryncodes•6,350
    @darryncodes
    Posted over 2 years ago

    Hi Zoulander,

    I think your question would be better resolved using semantic html and css instead of JavaScript.

    • instead of a using a list consider <input type="radio"> this has many more built in accessibility benefits and makes styling the input with :focus easier achieving the 'active' state
    • you can also tab into the input and use your arrow keys to see the focus state
    • styling radio inputs are a little trickier but something really worthwhile

    Extended content:

    • MDN - <input type="radio">
    • MDN - :focus
    • you should look into using <form>, <fieldset>, <label> and <input>'s too
    • when using the <form> you'll need to consider the submit event instead of onClick

    I hope that helps, any questions let me know.

    Happy coding!

    Marked as helpful
  • Ibrahim Tangco•150
    @ibrahimtangco
    Submitted over 2 years ago

    3-column-preview-card

    1
    darryncodes•6,350
    @darryncodes
    Posted over 2 years ago

    Hi Ibrahim,

    Overall a really decent solution and responsive - well done!

    A few bits of feedback for your consideration:

    • add {cursor: pointer;} to your buttons
    • swap <div class="grid container"> to a <main>. Semantic html is really important for accessibility and it should clear your report.
    • look into max-width to control the width of your content in a responsive way, rather than using width with percentage values. This would help your design not to stretch across the viewport at larger screens too
    • I noticed at different viewports your buttons are not aligned. Also if the content in the <p> were different lengths in the design you'd come up against the same challenge. I created this codepen that uses flex:1 and justify-content: space-between as potential solutions

    I hope that all makes sense, any questions let me know.

    Happy coding!

  • Aksinya🔮•10
    @Alice-in-Matrix
    Submitted over 2 years ago

    qr-code-component with hover effects

    1
    darryncodes•6,350
    @darryncodes
    Posted over 2 years ago

    Hi Aksinya,

    Really nice work on this one, good solution.

    I think your approach to CSS is completely fine on this size project. When your projects grow you could consider BEM to make building modular styles easier coupled with SASS to create multiple css files (partials) that relate to each component and compile to one style sheet.

    Also you should embed some best practices resolving your accessibility report. Your .container <div> could be a <main> tag and your .card-title <p> could be a <h1>. Semantic html is really important.

    I hope that helps!

    Marked as helpful
  • Erkin•50
    @ErkinN
    Submitted almost 3 years ago

    HTML,CSS

    4
    darryncodes•6,350
    @darryncodes
    Posted almost 3 years ago

    Hi Erkin,

    I really like your solution, it looks great!

    Your accessibility report is highlighting a few tweaks you could make:

    • swap .container <div> with a <main>
    • swap .attribution <div> with a <footer>
    • consider swapping your <h2> with a <h1>

    Using semantic html is a really fundamental part of building an accessible page. Also Heading hierarchy is important!

    • also try adding min-height: 100vh; to your <body> to help nice centre the design in the viewport

    I hope that helps!

    Marked as helpful
  • Mohsin Bashir•130
    @mobasher10
    Submitted almost 3 years ago

    Interactive rating component

    1
    darryncodes•6,350
    @darryncodes
    Posted almost 3 years ago

    Hi Mohsin,

    Really nice work on this challenge, well done.

    And great perseverance to complete the solution with radio buttons too!

    Some considerations for you:

    • check out a <fieldset> for your .rating-container. It is a semantic element to choose compared to a div and has some interesting attributes you might use in the future
    • you should consider adding cursor: pointer; to your interactive elements to give that additional feedback to the user on desktop
    • also it'd be great to see some focus states added to those interactive elements for those who navigate the component using a keyboard
    • your accessibility report is suggesting you need to use a landmark element like a <main>, here is some more information for you
    • lastly you could consider making the card and thank you result the same dimensions, so when it changes you don't notice a difference between the layouts as much

    Overall you smashed it, with a few tweaks you could level it up even further!

    All the best!

View more comments
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Mentor of the Week - 2nd Place

This badge is awarded to the 2nd placed community member on the weekly Wall of Fame.

Fun fact

Keypunches were used in early computing to punch precise holes in stiff paper card. The punched cards were then used for data input, output, and storage. No code linters or auto-complete suggestions to help out back then! 😅

Mentor of the Week - 3rd Place

This badge is awarded to the 3rd placed community member on the weekly Wall of Fame.

Fun fact

The Hansen Writing Ball shown in the badge was the first commercially produced typewriter. It was put into production in 1870 with its unique ergonomic design. It was overtaken in the market in 1873 by the Sholes and Glidden typewriter which was the first keyboard to utilise the QWERTY layout we now use today.

Mentor of the Month - 3rd Place

This badge is awarded to the 3rd placed community member on the monthly Wall of Fame.

Fun fact

An abacus is an ancient calculating tool. These days we would typically use a calculator or computer but the abacus is where it all started!

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub