Looking at the document structure of the start page, it has only one header - todays date... Other pages are missing headings, jumping straight from h1 to h3 without passing h2. On one page I found an h2, but in a way you'd think you wouldn't have to see anymore:
<h2>Röd lykta <span style="FONT-SIZE: 8pt; FONT-FAMILY: Verdana"><br /></span></h2>
Using my M600i to surf a lot these days I would also have liked to see a "Skip to content"-link for faster browsing as well as alternative text for the flash-thingy. All I get now is a line stating "flash failed".
WAI-wise the site fails to avoid deprecated features (11.2), associating labels with their controls (12.4) and separating links properly (10.5).
Interestingly, the site introduces a few completely new HTML elements I would like to share with you, you never know when they might come in handy:
<Lunchkonserter i Operakaféet>
<Längd ca 1 timme>
<Scen Operakaféet>
<LUNCHKONSERTER>
And for everyone out there that has switched to XHTML, just adjust these tags as follows:
<Lunchkonserter i Operakaféet />
<Längd ca 1 timme />
<Scen Operakaféet />
<LUNCHKONSERTER />
There's also a lot of divitis and classitis going on. Then we have the style sheets, but that's for some other day or someone else to go through.
The tools can certainly get better, in this case EPiServer. I would also expect more from a "market leader" on accessibility. The end customer should be able to trust these to deliver better quality.
Comparing a few searches with regular Google gives, as expected, quite different results. Let's see what happens when (and if) this Google Labs products is incorporated into the regular Google search.
Let's also hope Google will give their own code an overhaul. Entering the search term "google" in Google Accessible Search returns a Wikipedia article on the company as first result...
]]>“Transcendent CSS makes full use of the most up-to-date CSS techniques and in doing so does not require that we limit our creativity to the limited capabilities of legacy browsers.”
And yes, like everybody else I've put a few photos up on flickr. But heed Eric Meyers call — thou shalt not depict your dinner and mark it atmedia — 'cause we really don't need the extra amount of pictures to wade through (c. 3.500 when writing this).
]]>
The capital letter W starts off 1px to the left of where it should if the following conditions are true:
The following font-size values set on body (or your container of choice) also gets the job done without the down-sizing:
IE6/Win choppes part of the letter off. In lists the problem occurs when margin is set to zero.
If font-size is set to less than 83% or more than 90% the problem disappears. The same is true if you change font-family (Arial displays the same behaviour though). and no, I haven't tried every other font.
So. Are we dealing with a windows-problem here or is it native to the Arial font or any sans-serif? Well, since the problem also occurs in MS Word when you set Arial to size 8, we can at least be sure that it is not a CSS bug. IE7 beta 2 does not have the problem though. My bet is still with Windows. Any other ideas?
]]>Well. Why not, I say. We have hidden CSS from Netscape 4.x since way back and maybe Dan's doing the right thing since IE/Mac is no more.
Another one bites the dust.
question of the day is how many new bugs IE7 will introduce..
pessimist, who, me?
]]>"to better understand and execute on Web standards as defined by standards bodies such as the World Wide Web Consortium (W3C)"]]>