Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Dictionary Web App

react, react-testing-library, storybook, styled-components
Juan Bonilla•610
@juanpb96
A solution to the Dictionary web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everybody! This challenge was great for me to try new things. I wanted to see how Storybook works, this tool is fantastic for checking UI components separately and identifying accessibility issues easily. If you have any suggestions for improving this project, I would appreciate it!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sam Hemingway•180
    @SamHemingway
    Posted about 2 years ago

    Great implementation Juan!

    I really like the use of determining state from the URL (something I've been wanting to learn for a while now, any good tutorials you can recommend?).

    I really appreciate that you put in the work to add things like aria-label for unsighted users.

    I tested out your font selection drop down menu for keyboard accessibility, and at first glance it works great — kudos for the work you must have put in to trap keyboard focus, and that the selected font option is focused by default.

    The only weird behaviour is the fact that the page moves as we use the up/down arrow keys to select an option - perhaps there's a way to disable that default behaviour of those keys when the dropdown is active?

    Generally speaking, for things like the dropdown, I tend to turn to unstyled libraries like Radix UI as they're always bulletproof for annoying little things like this :)

    Last UX point: the only way to submit the form is by pressing enter, which might not be immediately obvious for anyone using it for the first time. A lot of users might expect a submit/search button that sends the form - I discovered this when I asked my partner to test my solution, and watched as she got confused after entering text on what to do next!

    Keep up the great work buddy!

    Marked as helpful

Join 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

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

Oops! 😬

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

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

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

Log in with GitHub