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

Responsive Officelite coming soon site challenge

accessibility, sass/scss
codezeloss•570
@codezeloss
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone!

I just completed another challenge Alhamdoulillah ❤️.

Please let me know about any issues you may find and how I can improve my solution & my code. I'm always open for your feedback (;.

Have a nice day!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 3 years ago

    Hi there

    Overall this looks good but content is overflowing my mobile screen slightly at the sides. I haven't examined css in this but that is often caused by either explicit widths/min-widths, or lack of paddings/margin

    More important learning points for you at the moment are around html Though:

    • use a main landmark for page content rather than nesting sections as children of the body
    • look up how to make forms accessibile. Lots of very important things to learn there. Your forms are missing loads of essentials at the moment like labels and validation
    • related - you can't build a fake select like that, the keyboard controls etc are totally different and it won't work for all users. Styling native selects is really limited but there are some third party versions you could include.
    • use button elements for form submits, not the legacy input type submit
    • use more appropriate semantic elements: eg in the carda, the list of benefits are lists not paragraphs
    • look up how and when to write good alt text on images and when to leave it Blank
    • use the date time element for dates
    • rethink the html and accessibility in particular on the countdown timer when you implement it. You might want the cards to be aria hidden, but have an understandable date in there for screenreaders that updates every minute or day etc - that would need aria live on it if you went down that route

    Last thing - really important to restore the gitignore in your repo!. Then delete node modules and ds store and repush to remove them from tracking. Then npm install on your local again. They should never be on your remote repo, only local

    Marked as helpful
  • codezeloss•570
    @codezeloss
    Posted over 3 years ago

    Hello Grace ! I hope you're doing well!! Thank you so much for your report & your analysis, it really shows that you have giver time to read my code...! Later I will work on all the points you mentioned inchallah, and of course I will try to pay attention to them in future projects. All the points you mentioned are really useful, through it I concluded that not only the Visual that matter to complete the project, but also writing CLEAN and complete code. Thanks again Grace, have a nice day!

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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