Accessibility is a build step, not a review step
Contrast ratios, focus order and motion preferences are cheap to get right while writing and expensive to retrofit.
Sample post. This entry is placeholder content used to build out the journal. It is not a statement by or about Tecnicubes.
Treated as an audit, accessibility becomes a list of defects filed after the work feels finished. Treated as a constraint, it barely costs anything.
Decide contrast when you pick the colour
Measure the ratio at the moment a colour enters the palette, and record what it is allowed to be used for. A brand colour at 4.4:1 is fine for large display type and unusable for body copy — knowing that up front prevents a hundred small arguments later.
Keyboard order follows source order
If the tab order is wrong, the document order is usually wrong too, and that is worth fixing for its own sake. Anything hidden but still present should be inert, not merely transparent.
// Transparent is not hidden — it is still focusable and
// still read aloud. Say so properly.
<article inert={!isActive} aria-hidden={isActive ? undefined : 'true'}>An invisible element that still takes focus is a trap, not a decoration.