Skip to content

RetroMake / accessibility

Accessibility

How the terminal presentation stays usable for every reader, and how to tell us when it does not.

What you are looking at

RetroMake draws every page on a character grid styled after a Commodore 64 or a DOS bulletin board. Underneath, each page is ordinary HTML: headings are headings, lists are lists, links are links. Screen readers announce the article, not the art. Decorative screens carry a text description; menu art that duplicates a visible list of commands is hidden from assistive technology so nothing is read twice.

Keyboard

Every command visible on a menu can be pressed on the keyboard. Tab moves through links and controls in order; Escape returns to the main menu. The hotkeys never capture typing inside a text field.

Text size and reflow

Font sizes come from the width of your window, so 40 or 80 columns always fit without horizontal scrolling. Browser text zoom is honoured: the grid remeasures itself and shrinks the column width rather than overflowing. Long articles wrap to the column width of the current theme.

Colour and motion

The palettes are the real ones, so contrast is what the original hardware offered; where a theme's default body colour fails the contrast guideline we brighten the body text one step and note it on the systems page. The cursor and ANSI blink attributes stop when your system asks for reduced motion. The optional scanline effect is off by default.

Emulators

Embedded emulators are opt-in: nothing runs or makes sound until you start it. Each has a text transcript or listing beside it.

Tell us

If any page fails you, write to desk@retromake.com with the page address and what happened. Accessibility defects are treated as bugs, not requests.