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

Advice-generator-app

jquery
P
Gabriela C•195
@gcardenasdev
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was my first calling an API and using JQuery for a project. Any advice on Accessibility is also very much appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Danilo Blas•6,300
    @Sdann26
    Posted about 3 years ago

    Hi Gabriela!

    I'll give you some recommendations:

    • For the centering in this case you can better use display flex than using margins because it will not adapt to all type of screen vertically as well as in the result of the design. So we will modify these two elements: To the body give:
    body{
       min-height: 100vh;
       display: flex;
       flex-direction: column;
       justify-content: center;
       align-items: center;
    }
    

    With that it would already be more or less centered and now we modify the main like this: Remove: margin: 5% auto 5rem auto; Add: margin-bottom: 3em;

    With this the design will improve with respect to the centered one.

    • To eliminate the error regarding the button we will add the tag aria-label="Change to Advice ". We change from <button type="button" class="dice-btn">`` to <button type="button" class="dice-btn" label="Change to Advice"`. This error happens because usually the buttons usually have text but when they do not have text when a screen reader passes through them, it detects that the button does not have meaning and then with the aria-label we add that meaning for its reading.

    • Lastly if or if there must be a h1 in your project that is the main title of your current page you could change the <p class="advice-id">ADVICE #171</p> by <h1 class="advice-id">ADVICE #171</h1> and it would be solved.

    I hope my comments will help you to improve.

    Good 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