Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Officelite coming soon site (html, css, js)

Alain•205
@Alain-sys
A solution to the Officelite coming soon site challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everybody,

I present to you my solution for this challenge.

Any feedback is welcome and very appreciated ! 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello, Alain! 👋

    Congratulations on finishing this challenge! 👏

    Here are some recommendations for improvements.

    • I notice that the alternative text for the logo is "redirect to home page". It's good that you use the alternative text to tell that it is a link. It would be better if it also tells the name of the site. So, include the company name as well in the alternative text.
    • Also, since the logo is wrapped by a link there's no need to tell about what will happen to the users. The screen readers will pronounce it as a link. So, the users will know that it is going to navigate them to another web page.
    • As a result the better alternative text is "officelite - home".
    • The details and summary elements should not be used for custom select elements.
      • First, it won't be able to submit any information.
      • Second, the screen reader will not pronounce it as a combobox. It tells the users that it is like an accordion element.
      • I used Narrator and it pronounced it as "Basic Pack Free, button, collapsed." There's no way that the users know that it contains some options to choose from.
      • I can't interact with the selection using the keyboard and the screen reader isn't pronouncing them correctly.
    • To create an accessible combobox, I recommend taking at the Select-Only Combobox Example by W3C. You can either use third-party component for custom select or just use the native select element.
    • Consider using the right type for the input elements. For example, use type="email" for email input. This will help mobile users to get the right keyboard layout.

    I hope this helps! Happy coding!

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

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