Control work
This control work covers Chapter II. The theory questions are about the web page, site and domain, HTML tags, CSS, pictures and alt text, forms and validation, animation and frame rate, sound, and links. The practical task is to build one page: a heading, a picture (with alt), a form, a link and a menu; save the file as UTF-8 and check it by opening it in a browser. The calculations include picture size (width·height·3 bytes, 24-bit colour), animation frames (rate·seconds), sound size (rate·bit depth·channels·seconds : 8) and speed (distance : time). To prepare: write a list of tags and attributes, recall each tag with a one-line example, test your code with the F12 console, and repeat the safety rules (do not send a password openly through a form, do not use pictures without permission, do not click a suspicious link).
A newspaper proofreader reads an article before printing and finds mistakes, because the author often does not see errors in their own writing. Checking with another person’s eyes gives a reliable result. Programmers also have their work tested by someone else.
Proofreaders, accountants and software testers recheck work through someone else’s eyes.
Do one calculation twice independently (the second time without looking at the first answer) and compare. If they differ, find the reason.
| Calculation | Result |
|---|---|
| 800·600·3, picture, bytes | 1440000 |
| 12·5, frames | 60 |
| 8000·16·5/8, sound, bytes | 80000 |
“Bug hunters”: a teacher or classmate prepares a page with 5 mistakes (no alt, an unclosed tag, a wrong relative address, a fixed width, an @keyframes name that does not match); another group finds and fixes them.