@blueocto
I never hear section 508 being used, should be used more often IMO.
@Aarlev
Yeah design wise very nice.
I would also agree with Br3n as more work, if you have it, gives you better boasting rights to any future employers about your credibility, and your ability to variate your designs to their mental ideas before they contact you.
I would look at your links though because even though it passes accessibility guidelines, as Blueocto rightly says, I would still argue that it is not as accessible as it could be ~
<a href="sorenaarlev.com/wp-content/themes/sorenaarlev/img/10_yy_large.jpg" rel="lightbox" title="10 Years Younger"><img src="sorenaarlev.com/wp-content/themes/sorenaarlev/img/10_yy.jpg" alt="10 Years Younger" /></a>
Now to a blind user that is going to be read out as ~
[link 10]10 years younger 10 years younger
Now as all your links use the title attribute and all your images/links are labelled correctly within either the A tag or the ALT attribute, then for a blind user they will just have every link read out 2ice to them, which is a bit irritating TBH. SEO wise the title attribute is not indexed so I would remove them, as it will reduce your code bloat and improve accessibility.
Personally, and TBH I'm being bold as I love CSS Zen Garden and I see you have a design in their, I personally would move the logo up the page.
This is from a usability point of view as I think it would use the space more efficiently by moving your main content area, the guts of the page and thus the area your site visitors want, up.
On your contact page apply the meta noindex, follow to the top of the page, in the head tag.
<meta name="robots" content="noindex, follow" />
This will remove the page from the search engines index and apply any equity you have more efficiently through out the main pages, which will help them to rank better, be it your home page and you blog.
Also a input tag that has it's type set to hidden wont be shown to the site visitor, so the surrounding div can be removed.
<div style="display: none;"> as it is overkill and not needed.
Are now we get to form accessibility, the vain of my life for the past 2 weeks.
What you want to do when you are coding forms is rather than relieing on how screen reader interpret the form is to tell them how to do it instead.
So for example you have this ~
<p class="contact">Your Name (required)<br />
<span class="wpcf7-form-control-wrap your-name"><input type="text" name="your-name" value="" class="wpcf7-validates-as-required" size="40" /></span> </p>
I would change that to ~
<p class="contact">
<label for="name">Your Name (required)</label><br />
<span class="wpcf7-form-control-wrap your-name"><input type="text" name="your-name" value="" class="wpcf7-validates-as-required" id="name" size="40" /></span> </p>
Now what we have just done is overridden the control of any screen readers.
When a screen reader hits a form they pretty much have to guess what input goes to what text.
Some read out the name attribute, some guess by using near by text. However all of them, to my knowledge, use what is in the label tag as a description text of that element if it is present.
So for each input tag that you have got that needs user content place a label tag around clear descriptive text near by it, place a unique id on the corresponding input value and then place the id name in the for attribute of the label tag. And bobs your uncle one clearly labelled and highly accessible form.
It also has the effect of when you click the words you have labelled it focuses the mouse on the corresponding input field.
You should also not link to the page you are on, by de-linking it and preferably bolding it, different background colour, what ever just make it stand out, it confirms to the user where they are within the site, which helps with site orientation.
You tag line says designer ~
What?
Interior designer?
Web designer?
Car designer?
Print designer?
Fashion designer?
To much ambiguity, your tag line is a highly important part of the page, it helps to clarify what the site is all about, so therefore needs to be spot on.
Also, sorry, very little niggle shouldn't the links to the previews read large
r preview?
Hope that has helped in some way.
Jaz
Key:
Purple ~ XHTML
Reddish-brown ~ Screen read output