Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Accessible & Responsive Article Preview Component using SCSS & JS

accessibility, sass/scss, vite
Gabriel Montplaisir•210
@GabrielMontplaisir
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Second project using SASS and SCSS. I decided to try using a @mixin for the headers and the author's name.

I wanted the tooltip to be "super-responsive" and make it scroll horizontally based on the screen size. This worked well when there wasn't enough padding on the right side. However, I wanted to make the arrow "stick" in one spot, and have the rest of the tooltip scroll horizontally once there was enough space (about 900px). I eventually resolved to create multiple media queries and make the tooltip jump from one spot to the next. If anyone could guide me on how I could make it scroll horizontally from smaller screens to overlapping on larger ones, I'm all ears.

Styling the tooltip correctly was also a struggle as the reference images shrink the card when the tooltip is toggled. Instead, I wanted to maintain the same height while centering the text on the button. I eventually found a "happy middle".

I took advantage of the different "roles" and attributes (aria-expanded) applied to the Share section and the buttons for transitions and the JS, instead of creating a .hidden class.

The Javascript was surprisingly the simple part. I added a couple of event listeners to check whether the user clicks on the button, or outside the tooltip. For accessibility reasons, tooltips also need to be allowed to be toggled "off" by pressing the ESC key.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Gabriel Montplaisir'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.