Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.
Stepped process doesn't result in HTML 4.01 transitional compliant
Options
LegacyForum
Posts: 1,664 ✭✭
How come when I follow the stepped process advocated by ParaSoft, after
remediating anything called out, I still don't end up with a page that is
compliant with the DOCTYPE specified at the top of my page?
From an accessibility testing perspective, I need my pages to validate
against the DTD specified, and yet there is no way in WebKing 5.5 to
validate against a specified DTD, only option for validating a full
xhmtl page against xhtml DTD...
We're not using XHTML, we're using HTML 4.01 transitional and when
I follow the stepped process, Step 1a Check Industry Web Stds, then
step 2, HTML Industry Standards, there's nothing afterwards to
validate full HTML page against DTD specified in DOCTYPE declaration
(HTML 4.01 Transitional)... only steps 3a, 3b, or 3c for basically
validating XHTML to XHTML DTD...
We're not coding XHTML and the JSF (JavaServer Faces) components
that we're suing don't emit XHTML, they emit HTML 4.01 Transitional HTML.
When I do an online DTD validation using the w3c online validator
(at http://validator.w3.org/) it still shows many violations that were NOT
flagged by WebKing.
Please advise...
Debi Kipping
0
Comments
-
Hello Debi Kipping,
Thank you for your question. I would like to redirect you to the IBM WebKing Knowledge Community where IBM employees are encouraged to post their questions or problems they may have with WebKing.
Another option is to send an email directly to WebKing Tool/Endicott/IBM directly, though the above method is preferred.
Please let me know if you have questions about this.0