Latest solutions
- Submitted 5 months ago
news-homepage-main
#accessibility#sass/scss#lighthouse- HTML
- CSS
- JS
I need some help on how to make the mobile menu do the transition from the right of the screen instead of just pop-in out.
- Submitted 5 months ago
contact-form-main
#accessibility#sass/scss#lighthouse- HTML
- CSS
- JS
I would like help on how to style that query box with
background-color: $green-200
whenever the radio input is checked.I would appreciate any other help! 👍
- Submitted 5 months ago
faq-accordion-main
#accessibility#lighthouse#sass/scss- HTML
- CSS
- JS
I want some help with the accessibility. I couldn't make the screen reader (NVDA) read the answer when I press "Enter" of the corresponding question.
- Submitted 5 months ago
interactive-rating-component-main
#accessibility#lighthouse#sass/scss- HTML
- CSS
- JS
I would appreciate any feedback. 👍
- Submitted 5 months ago
tip-calculator-app-main
#sass/scss#lighthouse- HTML
- CSS
- JS
I would love getting some feedback about the quality of the JavaScript code and also if the quality of the responsiveness of the page regarding large screens.
- Submitted 5 months ago
time-tracking-dashboard-main
#sass/scss#lighthouse- HTML
- CSS
- JS
I would appreciate any remarks regarding the JavaScript code, or if there is way to leverage CSS in order to make some the tasks done using JS.
Latest comments
- P@FixitoSubmitted 5 months ago@AymaneOnlinePosted 5 months ago
Add
aria-expanded
to buttons that control the menu to indicate the menu’s open/closed state.0 - @Alexandru736Submitted 6 months agoWhat are you most proud of, and what would you do differently next time?
Being able to improve the readability of my code. Next time I would try a CSS framework, maybe.
What challenges did you encounter, and how did you overcome them?Small challenges regarding how to style and how to extract the value of the radio buttons
What specific areas of your project would you like help with?I need feedback on how accessible is my site and how readable is my project.
@AymaneOnlinePosted 5 months agoHere are some feedbacks on accessibility as you asked:
- Add hover effects on the submit button and
cursor: pointer
so to make it more intuitive. - The consent checkbox is not reachable from the keyboard (try pressing tab few times), remove the </input> closing tag after the checkbox.
- There some fields that are not visible on mobile devices, to fix that remove the
display: flex; justify-content: center; align-items: center;
styles from the<body>
. - Try using the Lighthouse Chrome Extention it could help to spot some accessibility flaws to improve (like colour contrast for your case).
0 - Add hover effects on the submit button and
- @Alexandru736Submitted 7 months agoWhat are you most proud of, and what would you do differently next time?
Being able to think more of accessibility
What challenges did you encounter, and how did you overcome them?I didn't know how to split the background between the background color and the background image. I thought about creating two divs that represented both but I thought I would've overcomplicated the solution. In the end, I used the
What specific areas of your project would you like help with?background-image
property along withbackground-size: contain
Feedback on the accessibility standards I applied here. Thank you!
@AymaneOnlinePosted 5 months agoHere is some feedback:
Styles:
- Add
justify-content: space-between;
to the<div class="question">
to create that space between the question and the plus button. - Add
cursor: pointer
to the<button class="btn">
to change the appearance of the cursor whenever you hover the question.
0 - Add
- P@elisilkSubmitted 6 months agoWhat are you most proud of, and what would you do differently next time?
I focused a lot on using semantic HTML and the accessibility features of the built-in form controls to make sure that this component was fully keyboard accessible. I definitely wanted to make sure none of my styling of the radio buttons would interfere with any of those built-in features, and I think it turned out pretty well.
@AymaneOnlinePosted 5 months agoI have nothing to say, I've actually learned from your solution a lot. Good Luck! 👍
0 - @AdrienB23Submitted 5 months agoWhat are you most proud of, and what would you do differently next time?
.
What challenges did you encounter, and how did you overcome them?.
What specific areas of your project would you like help with?.
@AymaneOnlinePosted 5 months agoI did want to see the code, but your repository link is not working.🤔
0 - P@webdevbynightSubmitted 5 months agoWhat are you most proud of, and what would you do differently next time?
I learnt the way of building a grid layout with the keyword
What challenges did you encounter, and how did you overcome them?auto-fit
. I thought it would be complicated to use it, but it is as easy as to use therepeat()
function, where such a keyword is used. Combined with the use of theclamp()
function to define the grid container width, I managed not to multiply media queries.I wondered how I would translate the coloured top banner of each card into code in a efficient way. By testing with a pseudo-element and a grid layout, I realised that grid layout, like flexbox, included the pseudo-elements attached to the grid container in the elements to which the grid effects applied.
What specific areas of your project would you like help with?Do not hesitate over giving feedback about accessibility if there are improvements in the way I use
aria-live
, and about my TypeScript if there are improvements to make the code I wrote more performant.@AymaneOnlinePosted 5 months agoGood job, I like how you didn't forget the
focus effect
of the Daily button when the page is loaded on the first time.0