Accessibility
This site is a read-only archive of a 20-year-old volunteer forum. We built the archive itself with accessibility in mind, but the underlying content — two decades of member posts — predates any accessibility review and wasn't written with it in mind. This page describes both what we control and what we don't.
What this archive does
- Semantic HTML throughout: real heading structure, landmark regions, and a "skip to content" link on every page for keyboard and screen-reader users.
- Every interactive control (search, theme toggle, pagination, the log-collapse toggle) is a
real
<button>/<input>/<a>element, reachable and operable by keyboard alone, not a click-only custom widget. - Text and background color combinations are checked against WCAG AA's 4.5:1 contrast minimum, in both the light and dark themes — including the alternating post-background shading on topic pages, which is deliberately a distinct value per theme rather than one color reused everywhere, since a shade that reads clearly on a light background can all but disappear on a dark one.
- Dark/light mode follows your system preference by default, with a manual toggle that persists your choice.
- Enhancements like the reading-progress bar and the collapsed-log toggle are progressive: the full content is always present in the page and readable/searchable with JavaScript disabled — JavaScript only changes how it's displayed, never whether it's there.
What we can't fix
Post content itself — text, pasted scan logs, and images — is preserved as members originally wrote it. That means some real limitations we can't retroactively correct without altering the historical record: images posted without meaningful alt text, screenshots of text that isn't itself readable by a screen reader, and formatting quirks from a 20-year-old forum editor. We've prioritized preserving the content accurately over rewriting it.
Report a problem
If you hit an accessibility barrier in the archive's own interface (not in old post content) — navigation, search, contrast, keyboard traps, or anything else — email us at privacy@malwareremoval.com and we'll take a look.