Closed 0xabdulkhaliq closed 1 year ago
Hey there @SiddhantPawar03, @rohansx, @crocmons, @s2sharpit ππ»
Please make sure to assign this issue to me to make the work done!
Thank you.
To reduce notifications, issues are locked. Your issue will be unlocked when we add the label gssoc23
. If you're participating in GSSoC'23, please add the gssoc23
label to your issue.
Hello 0xabdulkhalid, thanks for opening a issue, your contribution is valuable to us. The maintainers will review this issue and provide feedback as soon as possible.
Description
Description
Key Points to Address
Keyboard Navigation: The form should be operable using keyboard inputs alone, without relying on mouse interaction. This is essential for individuals who navigate the web using assistive technologies.
Screen Readers Compatibility: The form elements and associated feedback messages need to be appropriately labeled and structured, ensuring compatibility with screen readers. Proper semantic markup will enhance the understanding of the form's purpose and improve the overall user experience.
Contrast and Visual Cues: Evaluate the form's color contrast to ensure readability for users with low vision or color blindness. Additionally, consider providing visual cues for form validation errors, alerts, and success messages.
Focus Indicators: Implement clear focus indicators to indicate the active form element. This is crucial for users who rely on focus indicators to navigate through web pages.
Responsive Design: Confirm that the form is responsive and adapts well to different screen sizes and devices, including mobile phones and tablets.
Validation and Error Handling: Enhance form validation to provide meaningful and descriptive error messages, guiding users on how to correct their input when errors occur.
Alternative Contact Options: In conjunction with the form, consider providing alternative contact methods, such as a dedicated email address or phone number, for users who may encounter difficulties with the form.
Expected Outcome
Screenshots
Checklist