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

Tic tac toe game with focus on a11y

accessibility, vite, web-components
P
Srijan Manandhar•450
@srijanss
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 learned new aria roles and attributes to make the game accessible, like grid, gridcell etc.
  • I learned how to use aria-live attribute to make the player turn live for screen readers.
  • I learned how to use CSS :not() pseudo-class to style the cells that are not occupied by a mark.
  • I learned how to use CSS :hover and :focus pseudo-classes to style the cells when hovered or focused.
  • I learned how to use CSS :before pseudo-element to add an icon to the cells when hovered or focused.
  • I learned how to use CSS variables to set the icon size and position.
  • I learned how to use aria-label attribute to provide a label for the grid cells.
  • I learned how to use aria-describedby attribute to associate the instructions with the grid cells.
  • I learned how to change cell state using data attributes.
  • I learned how to use Javascript's map method to render the cells.
  • I separated the game logic and data store from the UI components to make the code more modular and maintainable.
  • I learned how to use Javascript's every method to check if the game is a tie.
  • I learned how to use Javascript's filter method to filter the cells that match the active mark.
  • I learned how to use Math functions to generate a random number.
What challenges did you encounter, and how did you overcome them?
  • It was challenging to make the game status, turns, modal data live for screen reader users. Use of aria-live for turns and aria-describedby for modals and menu which points to visually hidden element in the div helped
What specific areas of your project would you like help with?
  • I have used header, main and footer inside web-components. Is it a best practice to do it this way ? Does this satisfy the accessibility requirement?
  • Any feedbacks regarding a11y are welcome
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marc Francis•730
    @marcfranciss
    Posted 9 months ago

    Impressive solution to this challenge! 💯

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.

Oops! 😬

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

Log in with GitHub