The accessible corner

Accessibility Statement

Assessed: November 2026 · Reviewed at least quarterly, or whenever someone with a screen reader says “hey”

Our commitment: mybrosyber.com aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA — the same benchmark the U.S. Department of Justice applies under the Americans with Disabilities Act. A joke site that excludes people isn’t a joke site, it’s a closed door with a whoopee cushion on it. We prefer open doors.

What we have done

Semantic HTML with landmarks (header, nav, main, footer); a skip-to-content link on every page; descriptive alternative text on all meaningful images (the beavers are described, not just declared); labels on form fields; visible keyboard focus styles; keyboard-operable navigation including the mobile menu; color contrast of at least 4.5:1 for body text against the dam-night background; reduced-motion support that stops the marquee ticker for visitors who ask their system for calm; ARIA labels where a visual glyph (like the ☰ menu button) needs a spoken name; and page titles and headings that actually describe their content.

Known limitations (an honest list beats a confident lie)

Some satirical content leans on visual gags and emoji that screen readers render literally — the 🦫 will be announced as “beaver,” which we have decided is feature, not bug. Some decorative flourishes may add verbosity without adding meaning. The infinite marquee ticker is animated by design; if reduced-motion is not enabled on your device it will keep swimming — tell us and we will make it swim quieter for everyone. We are genuinely imperfect here, and the gap is being gnawed at.

Report a barrier (this is read by a human)

If anything on this site is hard to perceive, operate, understand, or robustly use — write to inquiries@privatesystemsinc.com with “Accessibility” in the subject. We commit to acknowledging accessibility reports within two (2) business days, which is faster than most real security vendors’ marketing email, and fixing what we can, documented in writing. Feedback directly shapes our next conformance pass.

Methodology

This assessment combines automated checks, manual keyboard and screen-reader passes, and the opinion of one (1) very confident beaver who has read the WCAG specification and therefore cannot be un-invited from conversations about it. Formal third-party audit is on the roadmap, which in dam-years means: eventually, with teeth marks.