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

Tic Tae Toe Game using Astro, Sass with Vanilla JS

accessibility, astro, sass/scss
P
Kamran Kiani•2,780
@kaamiik
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?

I am most proud of creating a responsive design that works well across different screen sizes, as well as ensuring that the hover and focus states are properly implemented. I also made an effort to improve accessibility by following best practices in HTML and CSS. However, next time, I would like to implement the bonus features, such as saving the game state upon refresh and improving the CPU's logic to not only block my winning moves but also make strategic decisions to win. I plan to build a future version of this project using React to achieve these goals.

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

The main challenge I faced was managing the JavaScript logic, especially defining and updating different states of the game. I had to ensure that the game flow worked correctly depending on whether the user was playing against the CPU or in multiplayer mode. It was also essential to handle resetting the game, moving to the next round, and updating the game statistics. Additionally, incorporating features for screen readers required careful attention. To overcome these challenges, I did a lot of research and received significant help from ChatGPT. Although I tried to solve most problems on my own, I reached out for guidance when I got stuck.

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

I would appreciate feedback on accessibility and JavaScript code improvements. Specifically, I want to know if there are any areas where I could enhance the accessibility of my project, especially regarding screen reader support. I would also love to get feedback on my JavaScript logic, particularly around managing the game state and handling user interactions efficiently. Additionally, if you notice any other areas for improvement in my project, I would be grateful for your feedback!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Kamran Kiani's solution.

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 1st-party linked stylesheets, and styles within <style> tags.

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.