@Steven-AngSubmitted 22 days ago
Mudasir Nadeem
@mudasirNadeemAll comments
- @mudasirNadeemPosted 17 days ago
Great job, Steven-Ang! Your use of semantic HTML and overall responsiveness is impressive. To improve, consider adding visible focus states for better keyboard navigation and ensure all form inputs have proper labels for accessibility. Keep up the great work!
0 - @zhansayatazhibayevaSubmitted 19 days ago@mudasirNadeemPosted 17 days ago
i think you did not understand his requerment please check my page https://mudasirnadeem.github.io/time-tracking-dashboard-main/ load data from json file click the weekly Daily and Monthly text I appropriate you bacause you ui is very best
0 - @astnioSubmitted 23 days agoWhat are you most proud of, and what would you do differently next time?
I mostly learned how to style forms further, along with validation via JavaScript. I had done a smaller version of this before, but this was a bit more complicated as this had several elements to manage.
What challenges did you encounter, and how did you overcome them?I find that I struggle to remember how to style form elements often. With how common this seems to be I feel as though I should take some notes to refer to, as I find myself going back and having to research how to style certain elements repeatedly.
@mudasirNadeemPosted 19 days agoYour use of semantic HTML is strong, and adding aria-live to form validation would enhance accessibility. The layout works well on small screens, but more spacing could improve larger screen designs. Refactoring repetitive styles into reusable classes would help maintainability.
0 - @BaiacuPlaysSubmitted 2 months ago
- @xStephxSubmitted 27 days ago
- @MrReduSubmitted 27 days ago
- @xStephxSubmitted about 1 month ago
- @mudasirNadeemSubmitted 27 days agoWhat are you most proud of, and what would you do differently next time?
I’m proud of completing the project successfully and implementing a responsive design that works well across devices. Additionally, I improved accessibility by adding clear navigation and text contrasts.
What would you do differently next time? Next time, I would focus more on optimizing my code for performance and ensuring better cross-browser compatibility. I’d also spend more time testing for edge cases and user feedback before launch.
What challenges did you encounter, and how did you overcome them?One challenge I faced was ensuring the layout was responsive on all devices. To overcome this, I researched media queries and used a mobile-first approach, which made the design adaptable to different screen sizes. I also encountered issues with some JavaScript functionality, which I solved by debugging the code step by step and seeking help from online communities.
What specific areas of your project would you like help with?I would appreciate feedback on the following areas:
Code Optimization: Are there parts of my code that could be more efficient or simplified? Accessibility: Does the project meet accessibility standards, especially for users with disabilities? Cross-Browser Compatibility: Are there any issues with how my project works across different browsers or devices? Being specific in these areas will help me improve and refine my project further.
@mudasirNadeemPosted 27 days agoSemantic HTML: Great job using semantic HTML elements! This enhances accessibility and SEO. Ensure all sections use appropriate tags to convey meaning effectively.
Accessibility: The solution is generally accessible, but consider these improvements:
Add alt attributes to images for better screen reader support. Ensure all interactive elements, like buttons and links, have visible focus states to improve navigation for keyboard users. Responsive Layout: The layout looks good on various screen sizes. It’s essential to test on smaller devices to ensure there are no issues with overflow or alignment.
Code Structure: The code is well-organized and easy to read. Consider breaking larger functions into smaller, reusable components for better maintainability.
Design Consistency: The solution closely follows the original design, with only minor deviations that don’t impact usability.
Overall, this is a solid solution with just a few areas for improvement. Keep up the great work!
0 - @mudasirNadeemSubmitted 27 days agoWhat are you most proud of, and what would you do differently next time?
I’m proud of completing the project successfully and implementing a responsive design that works well across devices. Additionally, I improved accessibility by adding clear navigation and text contrasts.
What would you do differently next time? Next time, I would focus more on optimizing my code for performance and ensuring better cross-browser compatibility. I’d also spend more time testing for edge cases and user feedback before launch.
What challenges did you encounter, and how did you overcome them?One challenge I faced was ensuring the layout was responsive on all devices. To overcome this, I researched media queries and used a mobile-first approach, which made the design adaptable to different screen sizes. I also encountered issues with some JavaScript functionality, which I solved by debugging the code step by step and seeking help from online communities.
What specific areas of your project would you like help with?I would appreciate feedback on the following areas:
Code Optimization: Are there parts of my code that could be more efficient or simplified? Accessibility: Does the project meet accessibility standards, especially for users with disabilities? Cross-Browser Compatibility: Are there any issues with how my project works across different browsers or devices? Being specific in these areas will help me improve and refine my project further.
@mudasirNadeemPosted 27 days agoSemantic HTML: The solution effectively uses semantic HTML elements, which helps with accessibility and SEO. Consider using more specific tags (like <article>, <aside>, or <nav>) where appropriate to enhance clarity.
Accessibility: Overall, the solution is accessible, but here are some improvements:
Ensure all images have alt attributes for screen readers. Check that interactive elements (like buttons and links) have clear focus states. Responsive Layout: The layout adapts well across different screen sizes. It would be helpful to test on various devices, especially mobile, to ensure there are no overflow issues or misalignments.
Code Structure: The code is well-structured and readable, making it easy to follow. Consider breaking larger functions into smaller, reusable components to improve maintainability.
Design Consistency: The solution closely aligns with the original design. If there are any differences, they are minor and do not detract from the overall user experience.
Overall, this is a strong solution with minor areas for improvement. Great job, and keep up the excellent work!
0 - @Steven-AngSubmitted 28 days ago@mudasirNadeemPosted 27 days ago
Semantic HTML: Good use of semantic elements! Ensure all areas use appropriate tags instead of just <div>.
Accessibility: The page is accessible, but check focus states for interactive elements and ensure color contrast meets WCAG standards.
Responsive Layout: Looks good on various screen sizes, but test on smaller devices for any overflow issues.
Code Structure: The code is readable and organized. Consider simplifying or breaking up longer sections into reusable components.
Design Consistency: The solution closely follows the design with minor deviations that don’t affect usability.
0 - @MaobugichiSubmitted about 1 month ago@mudasirNadeemPosted 28 days ago
Hi Maobugichi, great effort! Here are some areas for improvement:
Semantic HTML: Incorporating elements like <header>, <main>, and <section> will improve structure and accessibility.
Accessibility: Add aria-label attributes for interactive elements and improve focus states for keyboard users.
Responsiveness: The layout doesn’t adapt well to smaller screens. Consider using a mobile-first approach with Flexbox or Grid for better scaling.
Code Structure: Simplify your JavaScript by reducing repetitive tasks and make your CSS more modular for readability.
Design Alignment: The design differs from the original layout. Try aligning it more closely with the provided guidelines.
0 - @MaobugichiSubmitted about 1 month agoWhat are you most proud of, and what would you do differently next time?
Finally got the hang of using fetch.
What challenges did you encounter, and how did you overcome them?not much
@mudasirNadeemPosted about 1 month agoGreat job! The semantic HTML is well-structured, and the responsiveness works across different screen sizes. To improve, consider adding more aria-labels for accessibility and refining code structure for better readability and maintainability.
0
