but I think due to the jquery adding of the prev/next buttons,the alt doesn’t show when hovering/standing on the slideshow.
Actually, alt isn’t supposed to show when hovering… that’s an old IE bug. Alt text should only ever be seen on the screen if/when the image doesn’t load.
What does appear on hover though is the title attribute. I’m usually against title most of the time because it’s often redundant and not useful and isn’t available to keyboarders… BUT if the company specifically wants some text to appear on hover then that’s exactly what you want.
<img src=“blah.jpg” width=“” height=“” alt=“you may or may not want alt and title at the same time” title=“text you want to appear on hover”>
Usually you don’t want alt and title to repeat each other. Some screen readers, if so configured (cause you can change the settings but we assume newbs don’t change anything, like with browsers) will read out both. So depending on how important the text is (which you must decide), you might want alt=“” and title=“the text”.
If it’s pretty important text then go ahead and repeat them. There are only 6 or so images in the slideshow anyway.
In the future if you have alt attributes and you notice that IE is showing a tooltip when you don’t want it, you can get around the bug by adding an empty title:
title=“” alt=“your real alt text”
Though I can’t say there wouldn’t be something jQuery does to make that not work quite right… for example the anchors are sitting right on top of the images and so hovering over them might not let a title tooltip from the image underneath to appear…
I mentioned you and Sitepoint in the meta-keywords tags, as my final thanks!
slimme poes! haha
I’m a bit scared of the js files though in putting them all into 1 file:
Can I just copy/paste everything under eachother and then link to that 1 file? Is that all there needs to be done for the js?
Yeah, I seem to recall that when I did that and jQuery was involved, I had to be careful with the part I added…
Ah, in my versions I also had the calling function at the very end, while you have it at the bottom of the page (shouldn’t matter because the ready function is waiting for the page load event anyway).
What you can do is just try it (make backups, or create a clone/fork of what you have so you don’t lose what you’ve got now) and try putting the scripts together and see if they still work. If you get errors, separate the Spry stuff from the jQuery stuff. You’d still have just one spry library and one jquery line.
<li><a class="MenuBarItemSubmenu" href="vloerbekleding.html">Vloerbekleding</a>
<ul>
<li class="submenu"><a href="blah"></a></li>
<li class="submenu"><a href="blah"></a></li>
<li class="submenu"><a href="blah"></a></li>
</ul>
I didn’t see .submenu in your style.css… is it for Spry? Without Spry, normally you don’t need a class on each sub-li. You normally target them with ul li li {styles} or use the class you’ve got on the anchor.
<table id="tabelwords"><tr><td class="words">creativiteit</td><td class="words">kwaliteit</td><td class="words">vakkennis</td><td class="words">veelzijdigheid & diversiteit</td></tr></table>
Similar. The class on each td isn’t necessary… #tablewords td would hit them the same way.
I forgot to mention this, but here’s another role that’s good to add:
<div class=“footer” role=“contentinfo”>
There are mostly two roles you’ll ever see on footers: contentinfo and complementary. Contentinfo is mostly information about who made the page and stuff like full company name, street address, etc… company info usually counts as contentinfo.
Complementary is for stuff that you’d also maybe see in a sidebar. Sometimes people put stuff in footers that’s stuff like, extra links, partner sites, side projects… often these are sitting in a “fat footer”. Like the black area of fabrique.
So you could add a role of contentinfo to the footer.
If you were to add a role of main, it would probably either be the beginning of the slideshow (the table itself), or, likely better, the right td with the actual text in it.
I happened upon raamdecoratie.html randomly clicking and there, it seems two grey areas, and the smaller one has the text? I clicked on another page and it looked fine.
Check your site in the validator:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.maxx-it.be%2FAanbod%2FWebdesign%2FMira%2520Site%2FMira%2Fsweetfruits%2Findex2.html&charset=(detect+automatically)&doctype=Inline&group=0
Most of those errors are explained below:
XHTML sees META and meta as two very different things… it’s case-sensitive. If you’re going to keep all those, lowercase them. If you’re going to use XHTML rather than HTML4/5, then you need to close the meta tags like /> in the <head>.
You have two charset tags: <META NAME=“charset” CONTENT=“ISO-8859-1”> is later… it’s possible that this one is making your letters okay since I’m not sure if it is able to override the other meta tag or not. Remove it and then check your letters.
You still have </br> in the page. This tag does not exist. For XHTML, you’d need <br/>.
akkennis</td><td class="words">veelzijdigheid & diversiteit</td></tr></table>
Ampersands (&) need to be escaped because they can have special meaning. Change them to & ; (without the space).
This also means in URLs. If you have an & in a url, the validator will not only complain about the &, but it will also flag any trailing = as well. The = is not an error, it’s just being triggered by the &. You can safely turn & into &’s in URLs because browsers convert them to the correct character.
The roles will give you errors because the validator with that doctype does not know what they are. These are errors we are willing to accept, because they aren’t real errors.
The last error is complaining about the type.
required attribute “type” not specified
<script> $(function(){
It’s up to you if you want to add the text/javascript to satisfy the validator or not. Under the HTML5 experimental doctype the validator would say nothing (same for roles) because it knows what that means, but XHTML will always flag it as an error… browsers don’t care.
It’s up to you.
Beyond that, triple check your pages by clicking through them, and then, I guess release it.
Your next site will be so much better : )
Don’t forget to checkout fronteers.nl… they have meetings in Belgium (non-members can attend), where they talk about front-end stuff. A meeting is where I first heard of @media queries, ARIA roles, and Phonegap. 
