The first step for an accessible site is conformance to a standard. A colleague of mine who closely follows this subject told me. It can be XHTML or HTML. Does not matter much as far as we conform to one, he added.
Please contest me if I say something stupid, but in a word, a site created using MOSS 2007 Publishing Feature does not conform to none of the two. You can not configure it to. You have to customize it.
It is based on ASP.NET 2.0 which I believe supports XHTML more than HTML.One of the places that you clearly see it is that it inserts lines like below, which violates HTML scheme.
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="..." />
And you can not configure it to stop doing so.
OK. Let us go for XHTML then. But, thank you MS! It violates it too...
You can see it quite easily, just by inserting an image using its Rich HTML Editor. It generates a line like this.
You can see it quite easily, just by inserting an image using its Rich HTML Editor. It generates a line like this.
<img border=0 ... >
Actually, I have the impression that MOSS Publishing feature is designed(?) to create HTML sites. Its OOTB masterpage files have got HTML doctype declaration.I really do not understand why it comes out like this...
Anyway, after having tried both, I saw going for XHTML should be a realistic solution, and started customizing it.
In a couple of posts after this, I would like to talk about the series of tricks that I employed.
No comments:
Post a Comment