Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt Responsive Units for Improved Flexibility and Accessibility #383

Open
pcodesdev opened this issue Aug 18, 2024 · 3 comments
Open

Adopt Responsive Units for Improved Flexibility and Accessibility #383

pcodesdev opened this issue Aug 18, 2024 · 3 comments

Comments

@pcodesdev
Copy link

I've been exploring your project and have greatly appreciated the effort put into developing the portfolio. I'm reaching out with a suggestion aimed at enhancing the project's responsiveness and accessibility.

Currently, the project utilizes fixed px units for sizing elements. While this approach works well for static designs, it can pose challenges when scaling the interface across different devices and screen sizes. Users on larger screens might find elements too small, whereas those on smaller devices might struggle to interact with elements that are too large or too close together.

To address this, I suggest considering the adoption of responsive units, such as percentages (%), viewport widths (vw, vh), or em/rem units, which are based on the root font size. These units automatically adjust to the user's device settings, offering a more fluid and adaptable layout.

For instance, margins, paddings, and font sizes could be defined using em or rem units, which scale based on the user's preferred settings. Similarly, widths and heights could be set using percentages or vw/vh units to ensure they scale with the viewport size.

Adopting responsive units not only enhances the user experience across devices but also improves accessibility for users who rely on zooming features or have specific display preferences. It's a small change that can make a significant difference in the usability and reach of your project.

I'd be happy to discuss this further or provide examples of how to implement these changes. Thank you for considering my suggestion.

Best regards,
Pcodesdev

@ashutosh1919
Copy link
Owner

@pcodesdev Thanks for the suggestions. Do you want to raise PR to solve this?

@pcodesdev
Copy link
Author

@ashutosh1919 Thank you for your response I will be raising a PR over the weekend to start working on this suggestions.

@pcodesdev
Copy link
Author

@ashutosh1919 would you kindly let me know if the pull request that I made last week on Saturday works. I am willing to continue editing the remaining css files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants