Our robust community site integrating Steam for enhanced user interactions and data management, powered by Remix with Tailwind CSS for optimistic, responsive UI. Features CI/CD with GitHub Actions and Docker for seamless deployment and maintenance.
We've encountered an issue in our repository regarding the cursor pointer and default styles in our custom cookie consent banner and modal. Due to our implementation of accessibility features using roles, there's confusion with cursor pointer behavior where it's not intended and vice versa.
Steps to Reproduce:
Open the website/application and trigger the cookie consent banner.
Attempt to interact with the elements within the banner and modal.
Observe the cursor behavior inconsistently applying pointer and default styles.
Expected Behavior:
Cursor pointer should only be displayed when interacting with actionable elements (e.g., buttons).
Default cursor style should be maintained for non-actionable elements (e.g., text content).
Actual Behavior:
Cursor pointer is inconsistently applied, causing confusion for users interacting with non-actionable elements.
Additional Context:
This issue stems from our implementation where buttons were created from <div> elements using roles for accessibility purposes. While this setup was necessary for onclick functionality and accessibility compliance, it has inadvertently led to confusion regarding cursor behavior.
Proposed Solution:
Review and refine the implementation to ensure consistent cursor behavior according to user expectations.
Consider alternative approaches to maintain accessibility compliance without sacrificing user experience.
We've encountered an issue in our repository regarding the cursor pointer and default styles in our custom cookie consent banner and modal. Due to our implementation of accessibility features using roles, there's confusion with cursor pointer behavior where it's not intended and vice versa.
Steps to Reproduce:
Expected Behavior:
Actual Behavior:
Additional Context: This issue stems from our implementation where buttons were created from
<div>
elements using roles for accessibility purposes. While this setup was necessary foronclick
functionality and accessibility compliance, it has inadvertently led to confusion regarding cursor behavior.Proposed Solution:
Screenshot: