Check the decision boundaries behind forms, tables, media, and input controls before using them in an application.
Review the lessons
- HTML button type: make every form action explicit
- HTML readonly versus disabled: preserve the right submission contract
- HTML form method=dialog: close a decision panel without a network request
- HTML formnovalidate: save a draft without publishing incomplete data
- HTML file accept: guide the picker, validate the upload on the server
- HTML telephone input: preserve symbols and validate your own format
- HTML textarea wrap: distinguish display wrapping from submitted line breaks
- HTML table caption and summary: explain a dense data grid
- HTML video transcript: retain information beyond timed captions
- HTML aria-invalid: connect a failed field to a repair instruction
- HTML submitter value: identify which button sent the form
- HTML image submit button: supply an action name and handle coordinates carefully
Common Mistakes
Passing a markup quiz does not prove that a route, asset, or authenticated server action exists.