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

Social Media Dashboard with Theme Switcher

accessibility, sass/scss
P
Øystein Håberg•13,260
@Islandstone89
A solution to the Social media dashboard with theme switcher 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?
  • Using Subgrid for the Overview cards
  • Creating gradient border with border-radius
  • Styling theme toggle using pseudo-elements and absolute positioning
  • Design System using Custom Properties
  • Using the :has selector to check if body has toggle checked - if it is checked, the theme colors are changed by updating Custom Properties like --body-bg and text-color, set on the body

Next time I will write where the colors are used at the beginning - with over 20 colors in this project, it's easy to get confused!

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

I had to research how to create the border with linear-gradient, and how to make the border-radius apply.

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

I'm wondering if I managed to create an accessible theme toggle. I added role="switch", as I think it should be used for toggles. I also added aria-checked with a default value of false, to tell screen readers the state of the toggle. I used JavaScript to toggle the states on click - if it's false it changes to true, otherwise it changes back to false.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Øystein Håberg'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.