Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

potential-happiness-master

Mudasir Nadeem•430
@mudasirNadeem
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

That's great! For your web accessibility page, you can reflect on things like making sure the page is easy to navigate for people with disabilities, ensuring good color contrast, or using semantic HTML.

To answer the question, you could say:

What you're most proud of: "I'm proud of making the page easy to use with screen readers by applying WAI-ARIA roles correctly and ensuring keyboard navigation works smoothly." What you'd do differently: "Next time, I would spend more time testing with real users who rely on assistive technologies to find any areas that could be improved." Would you like help with specific parts of the accessibility page?

What challenges did you encounter, and how did you overcome them?

To answer the question "What challenges did you encounter, and how did you overcome them?" for your web accessibility page, you could consider the following:

Challenges you encountered: Think about any difficulties you faced while making the page accessible. For example:

Ensuring proper keyboard navigation. Using WAI-ARIA attributes correctly. Managing color contrast for readability. Testing the page with screen readers or other assistive technologies. How you overcame them: Explain the steps you took to solve these challenges. For example:

Researching and applying best practices for WAI-ARIA roles. Using online tools to check color contrast ratios. Testing your page with accessibility tools or getting feedback from others. Would you like help detailing any specific challenge you encountered while working on the accessibility page?

What specific areas of your project would you like help with?

For this question, focus on particular parts of your web accessibility page where you feel unsure or need improvement. Being specific will help others give you useful feedback. Here are some examples you can consider:

Keyboard navigation: "I want to make sure my page is fully accessible via keyboard. Can anyone suggest improvements or tips on how to enhance this?"

Screen reader support: "I’ve used WAI-ARIA roles on custom elements, but I’m not sure if they are correctly applied for screen readers. Could someone review this part of my code?"

Color contrast: "I’ve tried to follow contrast guidelines, but I’m unsure if my color choices are accessible enough. Any feedback or suggestions for improvement?"

Form accessibility: "I’ve added labels and field descriptions to my forms, but I’m not sure if they are fully accessible. Can anyone test or review them?"

Would you like help drafting specific questions for your project?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Mohd Sadaf•1,160
    @MsadafK
    Posted 8 months ago

    project looks good to me 😊

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub