OK, now that it's back up, let's take a look at the examples. There's a "register to vote" page, but that's trivial. Here's a more difficult one - a mockup of a Veterans Administration form.[1] This is clearly for use by a Government employee, not the public.<p>(The first question one asks is, if an appeal is "certified", why does it also have to be "activated" by a human before anything happens? But that's the organization's problem, not web design.)<p>It's a high-contrast layout, to support the visually impaired. Although it does have both white on black and black on white buttons, visually it seems OK.<p>The form has a pull-down for "Confirm type action". This isn't a "Confirm" button, it's a selection option, for selecting the type of bureaucratic action. There are several documents mentioned, "Form 8", "Form 9", etc. These are in bold sans-serif blue text. The "NOD" document is apparently missing, so you couldn't view it, but the text for it is the same as for the documents you can view. At the end of each line is the word "Change", in the same font and color. It's not clear if "Form 8" is clickable, leading to a view of the form. "Change" is presumably clickable, and ought to lead to a popup. It's not clear whether changes commit immediately, or when the final buttons at the bottom ("Reassign" or "Activate Appeal") are clicked.<p>The "POA" heading is misaligned. You can tell they used table-less design - things don't line up right.<p>This form is useful only if the user has paper materials on hand against which they are checking. Functionally, this form is exactly equivalent to something on a green-screen IBM 3270 terminal from 30 years ago, which may be what it is emulating.<p>This is their example of good Government web design.<p>[1] <a href="https://playbook.cio.gov/designstandards/assets-styleguide/img/home/example_VAappeals_full_mock.png" rel="nofollow">https://playbook.cio.gov/designstandards/assets-styleguide/i...</a>