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

Article Preview Component with Toggletip

Gregor de Cillia•190
@GregorDeCillia
A solution to the Article preview component 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?

The js part came together pretty easily. Getting the styling for the tooltip right was a bit messy which is why I would think about that part earlier the next time around.

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

I had to do some experimentation with absolute positioning for the tooltip. Adjusting the crop-direction required some MDN reading. For the layout shift between mobile and desktop (img left vs top), I initially used grid but switched to flex later.

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

Tooltips are notorious for being hard with accessibility and there are different suggestions floating around depending on usecases. If you could give me your suggestion on how to make it work for this design, that would be great.

  • I remembered this article from an earlier project (back when I knew much less about web) and gave it another read: https://inclusive-components.design/tooltips-toggletips/.
  • Another idea I had was to make the tooltip an .sr-only element for screenreaders and a toggleable element for other users.
  • There is also the aria-expanded attribute which is often used with expandable nav elements which also seems to fit.

The amount of options feels very overwhelming to me which is why the current accessibility of the tooltip is at a very bad state. display: none removes the tooltip from the accessibility DOM until a screenreader user triggers a click event on a non-focusable element :(.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Gregor de Cillia'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 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.