This blog post is purposely broken. For example, here is a blatant spellling mistake. And here is anotherr.

That’s not all! How about we add a broken link to a different website? While we’re at it, let’s add another broken link to this website?

Next we’re going to embed some JavaScript which creates an error. You’ll need to read the source code to see that.

The readability of this page is generally very good, so let’s add some hard to read text, like this:

The real estate described below, together with all privileges, hereditaments, easements and appurtenances, all rents, leases, issues and profits, all claims, awards and payments made as a result of the exercise of the right of eminent domain, and all existing and future improvements and fixtures (all called the “Property”) to secure the Obligations described in paragraph 5 on the reverse side, including but not limited to repayment of the sum stated above plus certain future advances made by the person so named.

This image is lacking alternative text:

This image has poor quality alternative text:

And this image is completely broken:

This page is responsive, so it should work fine on mobile, but to stop that we’re going to embed a video with a fixed width below. This will break our mobile layout:

Now we need some contact details. Here are a few simple examples:

• Email: example@fakewinebarrel.com
• UK phone number: 01332 123 456
• International phone number: +44 1332 654 321
• Address: 101 Acme Street, Panic Lane, London EC1N 8LE

What follows is a semantically incorrect list of links. (These should be in a bulleted list):

Google
Facebook
Apple
Amazon

This is a blinking tag. Oh my goodness. What a fucking joke. This is not cool shit, you fucker.

This is a Heading 3 without a Heading 2 before it

The following table is not particularly well coded for accessibility:

Here’s a really bad web form with missing labels and such:

That’s enough contrived examples for now. Silktide should have fun testing this page.