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

Responsive Article preview component

Raink31•340
@Raink31
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone !

I used a .action class to toggle the share button. The text and images moves a bit when the class is added or not. How could I fix that ?

Thanks !

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    BUTTONS 🖲️:

    • This solution had generated accessibility error reports due to lack discernible text for <button> element

    • The <button> must have discernible text that clearly describes the destination, purpose, function, or action for screen reader users.

    • Screen reader users are not able to discern the purpose of elements with role="link", role="button", or role="menuitem" that do not have an accessible name.

    • The <button> name rule has five markup patterns that pass test criteria:
    
    <button id="al" aria-label="Name"></button>
    
    <button id="alb" aria-labelledby="labeldiv"></button>
    
    <div id="labeldiv">Button label</div>
    
    <button id="combo" aria-label="Aria Name">Name</button>
    
    <button id="buttonTitle" title="Title"></button>
    
    
    • Ensure that each <button> element and elements with role="button" have one of the following characteristics:

      • Inner text that is discernible to screen reader users.
      • Non-empty aria-label attribute.
      • aria-labelledby pointing to element with text which is discernible to screen reader users.
      • role="presentation" or role="none" (ARIA 1.1) and is not in tab order (tabindex="-1")

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    Marked as helpful
  • P
    visualdennis•8,375
    @visualdenniss
    Posted over 2 years ago

    "The text and images moves a bit when the class is added or not. How could I fix that ?"

    It is because these two settings you have set up:

    media screen and (min-width: 1103px) .profile img { width: 15%; border-radius: 2000px; }

    This gets overwritten by the one below:

    screen and (min-width: 1103px) .active .photo-and-infos img { width: 10%; }

    So images becomes 10% instead of 15% because you have set it so. You should find a way to separate classes of that profile image from the icons etc. so that nothing changes about the profile img when the active class is added.

    Hope you find this feedback helpful!

    Marked as helpful
  • C H A R A N 🎯•2,670
    @0xabdul
    Posted over 2 years ago

    Hello Developer well you Successfully finished the Article preview component

    • A Few Feedback for improve your code
    • In Html 📃 :
    • BUTTONS🖲️
    • In Fact using the button tag we use in right way
    • there are Four ways to use button tag in right way
    • Ex :
    1. <button id="text">Name</button>
    2. <button id="al" aria-label="Name"></button>
    3. <button id="alb" aria-labelledby="labeldiv"></button>
    4. <button id="combo" aria-label="Aria Name">Name</button>
    
    • I hope you find the solution and it's useful comment for you your Article preview component project is Awesome Finnally Happy Coding
    Marked as helpful

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