W3C Validation & Image Alt Tags

[fifteen]

Dante does not seem to have ALT tags attached to images on it’s shortcodes. One example I have found is the Team shortcode, which has this:

     $items .= '';

(in /dante/swift-framework/page-builder/builder/shortcodes/team.php)

As you can see, alt is not included here at all. This causes W3C HTML Validation to fail, and is potentially bad for SEO.

I find this strange as dante/swift-framework/page-builder/builder/shortcodes/clients.php has $image_alt on the image tags here. So does dante/swift-framework/page-builder/builder/shortcodes/gallery.php

Can the use of alt tags be implemented throughout the theme for consistency?

Next: CSS W3C validation: https://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fdante.swiftideas.com%2F&profile=css3&usermedium=all&warning=1&vextwarning=&lang=en

Dante does not validate. Please note that I’m ignoring non-dante stylesheets and focussing on dante/style.css

A lot of the CSS errors are “Parse Error = 100)” because you have spaces in between the equals sign and the number. =100). For example:

	filter: alpha(opacity= 100);

should be

	filter: alpha(opacity=100);

I have been fixing these as I go along, however I believe the theme should ship with total validation.

Could you please advise if you plan to make the theme validate with w3c? I realise some people disagree on whether or not w3c validation matters, however I would personally like it to validate. 🙂

Attachments:

You must be logged in to view attached files.

[David Martin – Support]

@fifteen Thanks for the feedback, I’ll pass this back to the team and see if we can improve this for a future update.

– Can you confirm what Dante theme version you are using?

Thanks.

[fifteen]

3.2.3

[fifteen]

This reply has been marked as private.

[David Martin – Support]

Hi,

I cannot provide a time frame, but will ensure this is reviewed for discussion.

Thanks.

[camind]

Would also like to get an update on this 🙂 Would be great If the Dante Theme can be validated. Would save us headaches in the future and would run more smoothly.

Hope this will be fixed soon.

Thanks

[Swift Ideas – Ed]

Hi @camind

It was validated back at release, but obviously a few things have cropped up since then. It’s on the list for the next update.

Thanks,

– Ed

[camind]

Ed,

That is great to hear. 🙂

Keep up the amazing work.

Thanks for the update

[David Martin – Support]

Great, thanks Ed.