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

article-preview

Denis•1,060
@Mod8124
A solution to the Article preview component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I need to improve in accessibility landmark too many errors..

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul•8,560
    @Samadeen
    Posted about 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Here are my suggestions..

    • You should nest all your div and heading in a main tag**.
    • You can wrapper your attribution section in a footer tag to avoid accessibility issues.

    This should fix most of your accessibility issues

    . Regardless you did amazing... hope you find this useful... Happy coding!!!

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

    Denis, buenas!

    Lo errores que tienes de Landmark se pueden solucionar rápidamente colocando todo lo que hay dentro del body además dentro de una etiqueta main, ya que siempre debes poner la información principal de tu proyecto dentro de esta etiqueta. Puedes dejar el div con la clase attribution fuera del main y ponerlo con la etiqueta footer ya depende de ti.

    Eso si intenta no usar las etiquetas h1, h2, h3... h6 sin ningún sentido semantico. Se utilizan para agregar titulos y subtitulos. Si o si necesitas una etiqueta h1 por página o te saldrá error, y luego las demás deben ir colocalas de manera incremental, es como cuando hacer un informe y este tiene un solo titulo y luego subtitulos por apartados y así sucesivamente, masomenos esa es la idea como deberías manejarlo.

    Por ahora solo he revisado la accesibilidad ya luego le doy una revisada al diseño y funcionalidad pero con eso debería salirte 0 errores luego de corregirlo.

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