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
Describe the bug
The decorative image of a man holding a key has no alt attribute. As a decorative image, it should be coded in CSS, not to be read by screen readers. Decorative images aren't important to be verbalized and may confuse navigation.
It's just identified an image and the user doesn't know what the image is or what is for.
Expected behaviour
As a decorative image, it should be in CSS to not be identified by screen readers. The screen reader user doesn’t know what is that image's purpose.
Screenshots
Cambiatus Env you are using
Put the URL of the page you are trying to use
Desktop (please complete the following information):
OS:Windows
Browser Chrome
Version 129.0.6668.101 (Versão oficial) 64 bits
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
For mapping all defects statistics, I just updated the spreadsheet. Also, there is a graphic to help understand some kinds of bugs and how they can impact users. Muda's Report Spreadsheet
Describe the bug
The decorative image of a man holding a key has no alt attribute. As a decorative image, it should be coded in CSS, not to be read by screen readers. Decorative images aren't important to be verbalized and may confuse navigation.
It's just identified an image and the user doesn't know what the image is or what is for.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
As a decorative image, it should be in CSS to not be identified by screen readers. The screen reader user doesn’t know what is that image's purpose.
Screenshots
Cambiatus Env you are using
Put the URL of the page you are trying to use
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: