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

Article Preview Component Solution

node
P
Steven•180
@stevensuna
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? Built With
  • Semantic HTML5 markup
  • CSS custom properties and BEM methodology
  • Vanilla JavaScript with ES6+ features
  • Mobile-first responsive design
  • Focus on accessibility
  • Progressive enhancement
Key Features
  • Responsive Design: Adapts seamlessly between mobile and desktop views
  • Keyboard Accessibility: Full keyboard navigation support with focus trapping
  • Screen Reader Support: ARIA attributes for enhanced accessibility
  • Smart Animations: Respects user's motion preferences
  • Click Outside: Closes share popup when clicking outside
  • Performance Optimized: Debounced resize handling
What I Learned

The project provided great insights into creating accessible interactive components. Here are some key implementations:

Managing component state:

const state = {
  isShareActive: false,
  isMobileView: window.innerWidth < BREAKPOINTS.TABLET,
  focusableElements: [],
};

Implementing focus trapping for keyboard users:

function setupFocusTrap() {
  const focusableSelectors =
    'button, [href], input, select, textarea, [tabindex]:not([tabindex="-1"])';
  state.focusableElements = Array.from(
    elements.sharePopup.querySelectorAll(focusableSelectors)
  );
}

Respecting user preferences:

if (window.matchMedia("(prefers-reduced-motion: reduce)").matches) {
  document.documentElement.style.setProperty("--transition-default", "0s");
}
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Gabe•320
    @gabei
    Posted 2 months ago

    This looks awesome! I really like your animations and the fluidity with which the different menus popup. The focus trap is also a nice touch. I don't know that I have a lot of constructive criticism to add, so I'll nit pick about the share button being a little finicky to click on PC.

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.

Oops! 😬

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

Log in with GitHub