Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

FAQ accordion (HTML | CSS | Vue JS Composition API + Vite )

vue, vite
Cheosphere•1,040
@Cheosphere
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


...made with a lot of love 🤘🏻🙂

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jax Teller•670
    @piushbhandari
    Posted over 1 year ago

    had a quick look at your markup:

    • i would change .faqs-header to a button instead of a div for semantic/accessibility reasons. additionally you can look into adding attributes aria-hidden for accordion content and aria-expanded for accordion buttons so screen readers will announce these.
    • h3 to h2 since you have h3 right after h1
    • because the accordion buttons are not actual <button> elements, your component is not accessible for keyboard users. hope this helps
    Marked as helpful
  • Shubham Kandpal•50
    @Shubham-kpl
    Posted over 1 year ago

    Loved it man!! Just wow! Keep it up

  • rimar-basaa•30
    @rimar-basaa
    Posted about 1 year ago

    Hola @Cheosphere, excelentes soluciones felicitaciones..

  • Zuhriddin Sharipov•70
    @ZUHRIDDIN-SHARIPOV
    Posted about 1 year ago

    Wow, that's great.

  • Zain•160
    @zainy2401
    Posted over 1 year ago

    Such a good solution, I'm jealous! I love how you've used Vue.js to build this and I'm hoping I can learn to do this soon with a JS library like this or maybe React!

  • Theunis•210
    @theYuun
    Posted over 1 year ago

    Awesome! I didn't even think to reduce input count by removing the enter/space key to expand/collapse the answer. Also cool that the Tab key does not cross onto the page at all, but I left that in in case accessibility controllers use the key to navigate.

  • LoopyOratory•120
    @LoopyOratory
    Posted over 1 year ago

    just wow

  • Wagner Morais•250
    @wagnnermorais
    Posted over 1 year ago

    i'd add a transition when a question get open, besides that, nice job.

  • Yousef•90
    @ousey-ousey
    Posted over 1 year ago

    cool man ! you may add feature on click again on "-" it disappear

  • P
    Dean•480
    @Deanogit
    Posted over 1 year ago

    Dude! This is amazing! 🥹

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

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

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

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

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

Oops! 😬

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

Log in with GitHub