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

Frontend Quiz app

P
Y39WebDeveloper•600
@Y39WebDeveloper
A solution to the Frontend Quiz app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Yulia•720
    @YuliaLantzberg
    Posted 7 months ago

    Hi. Your project is built well. I liked the naming and how js code was written. It's easy to read, the flow is organized simple, and clear. However, I think, the semantics of HTML can be improved. There is no main tag. You can use it instead of the root div. Also you use section as an entire container and then use divs. I think, it would be more reasonable to use a few sections for start, quiz, answers and score as there are separate different groups (pages). Anyway, main is strongly considered as the best practice. And about sections it's only in the scope of personal opinion. Also, there is a small bug. Your progress bar is empty when you enter the first question in the first cycle of the quiz. And start to expand only from the second question. But when you enter the first question after answering other topics, then the progress bar is full on the first question (like it's on 100%) I'd suggest to use the native progress tag of HTML. It'd be more right semantically but also very easy to manipulate. You just give the number of questions as max and change value as a number of the current question. And it will work perfectly. Hope it is helpful. And again, I really liked the simplicity of js code. :-)

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