You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improve Accessibility of Edit Button for Long Content Pages
Issue:
The current placement of the edit button at the bottom of the page causes significant usability problems, especially for pages with long content.
Current Behavior:
When viewing a page with extensive content, users must scroll to the very bottom to access the edit button. This process is time-consuming and frustrating, especially when frequent edits are necessary.
Steps to Reproduce:
Navigate to a page with long content, similar to the example provided
Attempt to locate the edit button
Observe that extensive scrolling is required to reach the button at the bottom of the page
Expected Behavior:
Users should be able to easily access the edit function without the need for extensive scrolling, regardless of the content length.
Impact:
This issue significantly hampers user experience and efficiency, particularly for content creators and editors who frequently need to make changes.
Proposed Solution:
Implement a more accessible placement for the edit button. Some potential solutions could include:
A floating button that remains visible while scrolling
Placing the edit button at the top of the page
Adding an edit button to a persistent header or sidebar
Additional Considerations:
The solution should work well for both desktop and mobile interfaces
Accessibility standards should be maintained in any new implementation
Next Steps:
I would like to discuss the expected outcome and potential solutions . I'm willing to submit a PR once we agree on the best approach. Let's collaborate to find the most effective solution that aligns with our project's design and usability standards.
Please share your thoughts and preferences regarding the proposed solutions or any other ideas you may have. I'm looking forward to contributing to the improvement of our user experience.
Why is this needed?
No response
Other information
No response
The text was updated successfully, but these errors were encountered:
You're right, the buttons at the bottom aren't very convenient in the example described. It might be worth adding a pencil icon on hover (similar to how it works with attachments), and I also like the idea of a floating button that stays visible while scrolling (probably achievable with position: sticky). It's a bit hard to say which approach will work best without testing, but we can start by ensuring the buttons are accessible.
Thanks for being willing to make a PR, we’d be happy to accept it 🙏
Is this a feature for the backend or frontend?
Frontend
What would you like?
Improve Accessibility of Edit Button for Long Content Pages
Issue:
The current placement of the edit button at the bottom of the page causes significant usability problems, especially for pages with long content.
Current Behavior:
When viewing a page with extensive content, users must scroll to the very bottom to access the edit button. This process is time-consuming and frustrating, especially when frequent edits are necessary.
Steps to Reproduce:
Expected Behavior:
Users should be able to easily access the edit function without the need for extensive scrolling, regardless of the content length.
Impact:
This issue significantly hampers user experience and efficiency, particularly for content creators and editors who frequently need to make changes.
Proposed Solution:
Implement a more accessible placement for the edit button. Some potential solutions could include:
Additional Considerations:
Next Steps:
I would like to discuss the expected outcome and potential solutions . I'm willing to submit a PR once we agree on the best approach. Let's collaborate to find the most effective solution that aligns with our project's design and usability standards.
Please share your thoughts and preferences regarding the proposed solutions or any other ideas you may have. I'm looking forward to contributing to the improvement of our user experience.
Why is this needed?
No response
Other information
No response
The text was updated successfully, but these errors were encountered: