Policy

Accessibility

Last updated November 8, 2026

I want these sites to work for everyone, including people using a keyboard, a screen reader, or reduced-motion settings. The goal is to meet WCAG 2.2 level AA.

What's in place

• Reduced motion. If your device is set to reduce motion, the front page and picoCTF Solves skip the 3D animations, intro sequences and page transitions, and show plain layouts with the same content.
• Screen readers. The 3D graphics are decorative and hidden from assistive technology; all of the information is also in regular page text. On picoCTF Solves, moving to a new category moves focus to its heading so it is announced.
• Contrast and text. Text is sized in relative units and keeps readable contrast against the dark background. On picoCTF write-ups, a Dots / Solid switch puts a solid background behind the text for easier reading.
• Zoom and small screens. Every page reflows for phone-sized screens without sideways scrolling, and picoCTF Solves enlarges its tap targets on touch screens.

Keyboard

Everything can be used without a mouse. A "Skip to content" link is the first thing you reach with Tab, and every link and button shows a visible focus outline.

• Page Down / Space and Page Up / Shift + Space move to the next or previous section on the front page and picoCTF Solves. Home and End jump to the top or bottom.
• Left / Right arrows move between picoCTF categories, between write-ups in the same difficulty, and between difficulty tabs when one is focused.
• Ctrl + K (or ⌘ + K on a Mac, or /) opens search on picoCTF Solves. Use the arrow keys to choose a result and Enter to open it.
• Escape closes search and menus, and backs out of a picoCTF category or write-up.

Known limitations

• The 3D animations on the front page and picoCTF Solves can be heavy on older phones and computers. Turning on your system's reduced-motion setting gives you the lightweight version.
• Some picoCTF challenges don't have a write-up yet. Those pages show placeholder text, clearly labelled as a placeholder, until the write-up is published.

Report a problem

If something is hard to use, email ZACrawfordx@gmail.com with the page and what went wrong. I will reply and work on a fix.