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

DHBLee_Tictactoe using React, TailwindCSS, Vite

react, tailwind-css, vite
P
Dong Hee•1,320
@DHBLee
A solution to the Tic Tac Toe 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?

Proud I was able to atleast clean some codes.

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

One challenge would be creating the logic for this game. But the most challenging part was to make it cleaner and more efficient :D

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

Would appreciate feedback in regards to my usage of React: Techniques, different approach. THank yow

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•7,270
    @MarziaJalili
    Posted about 2 months ago

    That’s an A game build, no cap! 👑

    A tiny tweak?

    ✅ If the <button> element doesn’t contain visible text or a discernible label (in this case an icon-only button), then you should provide an aria-label or similar accessible attribute, bro.

    ✅ This is best practice because the screen readers can convey the buttons’ purpose.

    ✅ For example, you could improve this button:

    <button aria-label=“restarts the game”>
      <img src={restartIcon} alt="" />
    </button>
    

    Other than that, the web’s lit!

    🔥🔥🔥

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