This webpage takes an HTML document as an input, goes through it, and gives you a report to tell you what is wrong with your HTML.
So you can see from the above example that you really want to make sure your HTML is well-formed! In a small example like the one seen above, it is easy to search through the lines and find the errors, but what about a huge, complex HTML document?
The best strategy is to start by running your HTML page through the Markup Validation Service — created and maintained by the W3C, the organization that looks after the specifications that define HTML, CSS, and other web technologies.
A failure might be because the user entered the details incorrectly or the document has been revoked, reported lost or reported stolen.
The identity provider can then carry out further verification to see if the person is who they say they are.
To do this, they have to look at a range of evidence and different methods to reach the required level of confidence, so that someone can't easily pretend to be you using just one or two pieces of evidence.
As part of the process of verifying a user's identity, identity providers will ask users to provide evidence that it's really them.
Writing HTML is fine, but what if something goes wrong, and you can't work out where the error in the code is?
This article will introduce you to some tools that can help you find and fix errors in HTML.
The error messages are usually helpful, but sometimes they are not so helpful; with a bit of practice you can work out how to interpret these to fix your code.
Let's go through the error messages and what they mean.
We've built the document checking service so that identity providers can check digitally - immediately - to make sure the information provided by the user matches a valid record. UK Verify, because it means identity providers can complete all the necessary checks within the time it takes for a user to go through their verification process - about 10 minutes in total, on average.