We are running a website and have 3rd party tracking pixels, but we're receiving alt
attribute errors when doing a webaim/WCAG 2.0 scan on our site.
I'm not sure if in this situation the tracking pixels actually need to still have a blank alt
attribute or would some screen readers still read the src
?
If no alt attribute is present, the screen reader will read the file name for the image instead, which can be a major distraction to those using screen-reading technology.
Also referred to as an alt description or an alt attribute, alt text is critical for those with disabilities because it describes the function and appearance of a photo or graphic they cannot see. PDF documents often contain images that convey critical information to the reader.
Deciding what to include and what not to include in an image's alt description is a grey area in web accessibility. Alt attributes (or alternative attributes) are textual descriptions of images added to the HTML code that a screen reader will read to a user as they navigate through a webpage.
Alt Tags for Accessibility The web should be easy for everyone to navigate. Those with visual impairments and other disabilities who use screen readers when browsing the web rely on alt tags so that images may be described to them, and to help provide more context and information about the content of a webpage.
alt=""
is the most appropriate approach in this case - this tells the screenreader that the image is purely decorative and should be ignored. Since tracking pixels do not visually convey information, they are essentially decorative from this point of view.
If no ALT is present, some screenreaders will fallback to reading the image name (without extension) instead, which you generally don't want.
Some screenreaders (JAWS) may ignore 1x1 or similarly sized small images - but still best to put alt=""
as that's the best practice.
Some references:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With