Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

SPA hangman game using React and SCSS

accessibility, bem, react, vite
Daniil•610
@DaniilGurski
A solution to the Hangman game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm satisfied that I've applied my knowledge in concepts like react portals, router dom, context and reducers, even if only a little.

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

I think back to when I first started adding styles to the menu page. At first I couldn't get the right shadow effect on the container and the button. I tried to use pseudo elements and other things, but as it turned out all this matter is solved by border width, which I simply forgot about.

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

I tried to make the game understandable when using screen readers, but I'm still not quite sure about some things. For example, when I click on the wrong button, the number of attempts is not counted, although I seem to have set the right aria attributes on the progress tag. Also, How else can I clearly let the user know in which position of the word he guessed the letter ? It was also quite difficult to fit some of the mystery words on the screen. It often looks strange on mobile devices, so I'd be interested to hear how you dealt with it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tsotne Meladze•1,120
    @tsotneforester
    Posted 4 months ago

    Greate Try, everything works like a charm! 🌟

    • start page is bit tricky in figma, you have placed start card into the center, but here is catch: The Hangman Game logo is also part of it so upper edge of logo and bottom edge of card should be equidistant from screen edges.
    • here is css for stroke text, or you can export as .svgs for how to play, pick a category and etc
    h1 {
    line-height: 120%;
      text-align: center;
      background: linear-gradient(180deg, #67b6ff 16.42%, #ffffff 100%);
      -webkit-background-clip: text;
      background-clip: text;
      -webkit-text-fill-color: transparent;
      display: block;
      position: relative;
    
      &:before,
      &:after {
        content: 'Pause';
        position: absolute;
        top: 0;
        left: 0;
        width: 100%;
        line-height: 120%;
        text-align: center;
        background: linear-gradient(180deg, #67b6ff 16.42%, #ffffff 100%);
        -webkit-background-clip: text;
        background-clip: text;
        -webkit-text-fill-color: transparent;
      }
    
      &:before {
        z-index: 1;
        -webkit-text-stroke: 10px #2c3342;
      }
    
      &:after {
        z-index: 2;
      }
    }
    

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
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

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