Checklist the per-video bar — engine/sim
98.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review longform-W28-Sat good|bad)⚠ 1 flag(s) — not yet ship-ready: copy_generic · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelpending1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
render pending — silent master not yet on disk
expected output: 0/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 6 scenes · 152.6s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  matches intent shared field signature-3d | open | 0–25.9s | spatial-parallax | icon·liquid-chrome | ♪ bed_in | A site that is live should work for every person who lands on it, including the ones using a screen reader or a keyboard instead of a mouse. That is accessibility, and it is not a favor, it is just building the thing right. Today I show you how we made the The Big T-M hub usable by everyone, with plain moves you can copy onto your own site this afternoon. on-screen: The hub works for everyone |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · node-graph · spatial-parallax · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape tetraground redtreatment liquid-chromemotion spatial-parallaxpower summoninstrument summon→The hub works for everyone | |||||||
| 2 |  matches intent NumberedList template | teach | 25.9–53.599999999999994s | kinetic-build | icon·white-knockout | ♪ node_lock | First move. A blind visitor uses software that reads the page out loud, but it cannot read a picture. So every image on the hub has alt text, a short written description in the code. We had the model draft alt text for each image from what it actually shows, then we corrected the ones that were off. An image with no description is just a blank spot to a screen reader. We leave no blanks. on-screen: Describe every image in code |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Describe every image in codecurate items, nodes | |||||||
| 3 |  matches intent ChecklistCard template | teach | 53.6–77.4s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Second move. If your text is too light against its background, plenty of people cannot read it. There is a real rule for this, a contrast ratio. We ran the hub's colors through a contrast checker and bumped up anything that failed until it passed. This also helps anyone reading on a sunny phone screen. Building for the edge case quietly fixes it for everybody. on-screen: Make sure the text can be read |
expected on screen: red ground · a ChecklistCard panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape tetraground redtreatment liquid-chromemotion kinetic-buildpower morphinstrument morph+laser→Make sure the text can be readcurate items, nodes | |||||||
| 4 |  matches intent CodeWindow template | teach | 77.4–103.30000000000001s | kinetic-build | icon·white-knockout | ♪ node_lock | Third move. Many people never touch a mouse. So we tested the hub using only the tab key, moving through every link, button, and form field in order. Where the focus jumped around or got stuck, we fixed the page so it flows top to bottom. If you cannot use your own site with just a keyboard, some of your visitors cannot use it at all. We made sure you can. on-screen: Drive the whole site by keyboard |
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Drive the whole site by keyboardcurate codeLines, nodes, windowTitle | |||||||
| 5 |  matches intent ListCard template | proof | 103.3–127.4s | receipts-count | icon·liquid-chrome | ♪ node_lock | The proof. We did not just claim the hub is accessible. We turned on a screen reader and listened to it read the live page, tabbed through it with no mouse, and ran the contrast check until it passed. The site you can visit went through that, not a checklist we ticked from memory. Accessibility you have not tested is just a word in a meeting. on-screen: We tested it the hard way |
expected on screen: red ground · a ListCard panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id ListCardvisual receiptsshape tetraground redtreatment liquid-chromemotion receipts-countpower receiptsinstrument spotlight→We tested it the hard waycurate items, statsLabels | |||||||
| 6 |  matches intent shared field signature-3d | resolve | 127.4–152.6s | coalescence | icon·liquid-chrome | ♪ bed_out | That is how The Big T-M built the hub for everyone. The takeaway. Write alt text for every image, check your color contrast against the real rule, and prove your whole site works with only a keyboard. None of it is hard, it is just usually skipped. Your next step. Unplug your mouse and try to use your own site. Then see ours at office dot temerarii dot xyz. on-screen: Run the keyboard test today |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment liquid-chromemotion coalescencepower coalescenceinstrument coalescence→Run the keyboard test today | |||||||
Format stack 1 aspects · same scenes[], re-cropped
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 2 destinations
YouTubeBlog
Social captions supplemental published copy · per channel (comp_id level)
youtubeMake Your Site Usable for Everyone: Alt Text, Contrast, and a Keyboard-Only Test
A live site should work for every person who lands on it, including the ones using a screen reader or a keyboard instead of a mouse. That is accessibility, not a favor, just building the thing right. This walkthrough covers plain moves you can copy onto your own site this afternoon.
The moves:
- Describe every image in code. A blind visitor's software reads the page aloud but cannot read a picture, so every image gets alt text, a short written description. Draft it from what the image actually shows, then correct it. An image with no description is a blank spot to a screen reader.
- Make sure the text can be read. Light text on a light background shuts people out. There is a real rule, a contrast ratio. Run your colors through a contrast checker and bump up anything that fails. This also helps anyone reading on a sunny phone.
- Drive the whole site by keyboard. Test using only the tab key through every link, button, and form field in order. Where focus jumps around or gets stuck, fix the page so it flows top to bottom.
The proof: we turned on a screen reader and listened to it read the live page, tabbed through with no mouse, and ran the contrast check until it passed. Accessibility you have not tested is just a word in a meeting.
Your next step: unplug your mouse and try to use your own site. Then see ours at office.temerarii.xyz.
Keywords: web accessibility, alt text, color contrast ratio, keyboard navigation, screen reader testing, inclusive design.