Accessibility on this site
This site publishes plain-language guides about Windows security software, and a guide that only some readers can use isn't finished. This page lays out what we do to keep pages readable, navigable, and usable across devices and assistive technology, and how to tell us when something falls short.
What we build into every page
Pages here are written as structured text: headings in order, descriptive link text instead of 'click here', and tables that are used only for actual tabular data like system requirements. That structure matters as much for a screen reader as it does for someone skimming on a phone.
- Semantic headings (H1 for the page title, H2/H3 for sections) so navigation by heading works correctly
- Sufficient color contrast between text and background
- Text that reflows and remains readable when zoomed to 200% in a browser
- Links with wording that describes the destination, such as the Windows hub page rather than a bare URL
Keyboard and screen reader use
Every interactive element on this site — navigation links, the search box if one is present, and in-page anchors like the FAQ sections — should be reachable and operable using a keyboard alone, without a mouse or touch input. We test with common screen readers periodically and fix issues as they're found.
Known limitations
We don't control third-party embeds such as ad networks or analytics scripts, and those can occasionally introduce accessibility issues outside our code. We try to minimize reliance on such elements and will keep working on pages where a barrier is reported.
Reporting a problem
If a page is hard to navigate, a contrast issue makes text unreadable, or an image is missing helpful alt text, let us know through the contact page with the URL and a short description of what happened. We read every message and prioritize fixes that affect the most readers.
Frequently asked questions
Does this accessibility statement apply to Malwarebytes the company?
No. This is an independent publication, not affiliated with Malwarebytes. This statement covers only malware-bytes.net.
What should I include when reporting an accessibility issue?
The exact page URL, the browser or assistive technology you were using, and what you expected versus what happened. That's usually enough for us to reproduce it.
Do you follow a specific accessibility standard?
We aim for practices consistent with widely used web accessibility guidelines, focusing on keyboard access, contrast, and semantic markup rather than claiming formal certification.
Malware-Bytes.net is an independent information resource about malware protection for Windows. We are not Malwarebytes, and this site is not the official Malwarebytes website or support channel. Malwarebytes is a trademark of Malwarebytes Inc.