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

Excluding Tracker Pixels from Screen Reader Accessibility #569

Open
jeromehardaway opened this issue Mar 17, 2024 · 0 comments
Open

Excluding Tracker Pixels from Screen Reader Accessibility #569

jeromehardaway opened this issue Mar 17, 2024 · 0 comments

Comments

@jeromehardaway
Copy link
Contributor

Description:
In our application, we utilize small or hidden tracker pixel images for analytics and marketing purposes. While these images play a crucial role in gathering valuable data, they should not be accessible to users, especially those using screen readers, as they offer no informational or functional value to the user experience. To adhere to accessibility standards and ensure a seamless experience for all users, including those relying on assistive technologies, we need to ensure these tracker images are properly marked to be ignored by screen readers.

Action Required:

  • Conduct an inventory of all tracker pixel images used within the application. These are typically small (often 1x1 pixels) images embedded in various parts of the application for tracking user interactions, analytics, or marketing purposes.
  • For each tracker pixel image identified, add a role attribute with the value of either "none" or "presentation". This will explicitly instruct screen readers and other assistive technologies to ignore these images, as they do not contribute to the content or functionality accessible to the user.
  • Ensure that this practice is maintained for all future additions of tracker pixel images to the application, keeping the application's accessibility in continuous compliance.

Expected Outcome:
Implementing these changes will enhance the accessibility of our application by preventing screen readers from announcing unnecessary and non-informative elements, thereby improving the navigation experience for users utilizing assistive technologies. This adjustment aligns with our commitment to inclusivity and ensures our application meets web accessibility standards.

This task is pivotal in ensuring that our application remains focused on providing content that is relevant and accessible to all users, including those with disabilities. By excluding non-essential elements from the accessibility tree, we uphold our dedication to creating an inclusive digital environment.

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

No branches or pull requests

2 participants