|
If you were logged in you would be able to see more operations.
|
|
|
|
In the prepackaged demo on the "About us" page I added a new image in a file field and another new image in a big text. I turned on all WAI integrity checks and adequate rule.
Both images do not have any "ALT" value so will cause some WAI errors.
In the case of the image introduced in the big text the error is correctly diagnose. This is not the case for the image in the file field.
There is no reason that one is causing an error and not the other.
Finally How do I enter an alt value for an image field?
[This integrity check was not present in Jahia 5 SP4 so I delayed it for the 6.0 SP1+ - Up to you the urgency of WAI checks]
|
|
Description
|
In the prepackaged demo on the "About us" page I added a new image in a file field and another new image in a big text. I turned on all WAI integrity checks and adequate rule.
Both images do not have any "ALT" value so will cause some WAI errors.
In the case of the image introduced in the big text the error is correctly diagnose. This is not the case for the image in the file field.
There is no reason that one is causing an error and not the other.
Finally How do I enter an alt value for an image field?
[This integrity check was not present in Jahia 5 SP4 so I delayed it for the 6.0 SP1+ - Up to you the urgency of WAI checks] |
Show » |
Sort Order:
|
Bug
Resolved - To be tested
Minor
No WAI check on images on file fields
The same applies to all other additional attributes (height/width, title etc.), we have no influence on.
From internal point of view, there is no semantic behind the File field. It is the content designer who decides, if this is an image, a link to a document or something else.
If we introduce here WAI checks, this can lead to confusions. What do you think?