Straightforward build, code is relatively clean I think. Put some effort in fixing details and refactoring the JS code as described in the article.
What challenges did you encounter, and how did you overcome them?Sometimes you loose time with the simple things (typos, linking a JS file etc.)
hello, i see there is no hover effect. also reset is enabled while there are no input values present. also i have to manually hit enter key at "number of person" thing to calculate split values. also no heading at mobile screen sizes. other than that UI looks clean to me. i hope u ll find this feedback helpful 😊
woah!! brother there is huge problem here. your site at mobile screen sizes looks extremely wrong. i means images/icons are not portrait correctly. divs are even not center aligned. No use of javascript at all. it was a javascript challenge but you not applied that just used hardcoded values. brother if you need help ask in discord community. but don't walk your journey this way. I hope you ll take this feedback in a positive way 😊.
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?
overall code looks good to me. few things can be improved like : => always try to select element through classes rather than by their tag names. => your codes looks good at width "375px" but when the screen sizes reduces to with "320px" then the design gets shrink somehow because there were no styles added for screen size "320px".
hope this helps you in some way 😊
I feel satisfied with the result, for now I don't think I will make any future changes.
What challenges did you encounter, and how did you overcome them?I had problems adding a Hover effect to the buttons, I used the linear-gradient() property to add a more custom color when hovering over the button, but the transition effect didn't work, until now I couldn't solve it.
try adding this "transition: background-image 0.3s ease, box-shadow 0.3s ease; " to your ".newsletters button".
hope this helps with your hover effect.
just a little feedback
i hope you ll find this feedback helpful 😊
just a little feedback, when i click on the plus sign to see the answer. it just expands means your accordion box just takes the full width of screen. so next time try to use width or max-width wherever needed/possible.
hope you find this feedback helpful 😊
hey there! your project looks nice. one thing i noticed is that when you select any rating by clicking it, it should also works in reverse i.e. if you again click on the same rating, it should deselect it.
hope you find this feedback helpful 😊
This is my first project where I implemented a mobile-first approach, and I would structure the menu’s HTML differently next time
What challenges did you encounter, and how did you overcome them?The minus and plus SVG buttons didn’t work correctly for me, so I had to switch to Font Awesome for another SVG. However, it wasn’t a challenge
What specific areas of your project would you like help with?I would appreciate it if you could take a look at my project and code, and share your feedback.
I guess everything!. I learned how to write media queries with mobile first approach and desktop approach.
What challenges did you encounter, and how did you overcome them?It was super challenging for me to make it responsive! I learned few things hard way- Making images responsive is also a bit tricky and large padding can also break design in smaller resolution.
What specific areas of your project would you like help with?Any feedback on this challenge is greatly appreciated.
i just checked your project. it looks great to me. there are some points which i like to highlight here:
hope you find this feedback helpful 😊
