Forum Moderators: open
Start with the easy stuff:
What is tricky -- and will mark your validator as more or less usable and user friendly than existing ones -- is how you handle error recovery: ie what you do to get back on track when the HTML is missing a close tag, close quote etc.
With good error recovery you are more than halfway to being able to make a stab at validating wild HTML -- the stuff that isn't constrained by a known DTD.
The other thing that will mark your solution as better or worse is the quality and preciseness of your error messages.
Hi all,
I'm wanting to invent something that I can put on the front and back of my bicycle frame to help it move. Can anyone offer any advice?;-)
I havent got time for jokers; Im gathering information, this isnt a give me the code so I can get rich this is new project our company (a very large disability company may I add) is taking on. This will be getting developed no matter what smart arses say like you.
victor thanks for the info - this aint going to be easy by all means :)
I personally use "CSE HTML Validator", a product with which I am extremely happy, and it has extensive accessibility checks. It has a free trial version, and I would not be surprised if they gave disability companies a discount (it isn't too expensive, anyway).
BTW, I have *no* connections with the company that writes the software; I just use it.
We are wanting to develop it ourselves to have it operate / check docs exactly how we want; we then use that information to generate a printed report in compliance with DDA / W3C guidelines. This will be getting a huge marketing budget etc so will be big, I wont be developing the software - im just the webmaster wannabe :)
We have a team of microsoft certified developers who are more than up for the task so we are just trying to get as much info / advice before this gets on the way..