Every now and then you come across an example of code that slaps you around the face and demonstrates that you really do have to make sure you use valid code.
Someone from the company in question queried this, they thought the links in question did work. The code went something like this:
If you also take into account that the
<noscript> tag is a block element (like paragraphs, headings etc.), you shouldn’t be able to wrap a link around it in the manner the author must have been expecting.
As it happens, most browsers (including IE6, Opera & Safari) do use the second link. However, Firefox doesn’t, effectively closing the second link within the
<noscript>, so there is no content to the link.
This may be a minor example, but it does show you’ve got to use valid code to be confident how it is dealt with. Major examples would probably cause visual issues in cross-browser checking, and are less likely in the days of a reasonable Firefox market share.
<noscript>. However, as any standards aware developer would have been able to say: use a progressive enhancement method. There are even tools to create accessible pop-ups for you!
2 contributions to “Invalid HTML interfering with accessibility”
I don’t find yrou code examples, partially hidden and with both horizontal and vertical scroll bars, very accessible.
That depends on your setup, I don’t get vertical scroll bars.
The underlying markup is good, and accuracy is important. (It is important that you can cut and paste straight into something else).
I set the
autoso that scroll bars are added if there isn’t space for the content. That stops IE dropping the layout, and stops others from overlapping content, also not very appetising options.
Comments are closed.