Accessibility Statement

Accessibility commitment

Putty.info aims to make educational SSH/PuTTY content usable by people with diverse abilities. We target WCAG 2.2 Level AA as closely as practical for a content-heavy technical site, recognizing that third-party embeds (if any) and user-generated screenshots may need iterative remediation.

Measures we take

• Semantic headings and landmarks for page structure.
• Keyboard access for primary navigation and forms, with visible focus styles.
• Skip links to reach main content.
• Text alternatives for informative images we publish; decorative images marked appropriately.
• Contrast-conscious colour choices for body text and controls.
• Labels and instructions on contact and interactive tools; errors described in text.
• Avoiding conveying meaning by colour alone in diagrams we control.

Code samples and terminal output may scroll horizontally on small screens; we prefer wrapping where readability allows.

Known limitations

Some historical screenshots or third-party ad frames may not meet our internal standards yet. Download verification instructions sometimes reference external official pages whose accessibility we do not control. Interactive troubleshooters aim to avoid time limits; if you encounter a barrier, tell us.

Compatible technologies

We test primarily with current evergreen browsers on Windows and Linux. Assistive technologies vary; our goal is robust HTML rather than a single AT vendor. If a specific browser/AT combination fails, include versions in your report.

Feedback process

Report accessibility barriers via the contact form with category Accessibility issue. Include the URL, description of the barrier, and your assistive technology if relevant. We prioritize barriers that block understanding of security-critical guidance such as host-key verification and safe downloads.

Formal requests

If you need content in an alternative format, contact us with the page URL and format requested. We will respond within a reasonable period given volunteer/editorial capacity and technical constraints.

Field notes and runbook extras

Additional operational depth for Accessibility Statement (path /accessibility/): treat every change to authentication, forwarding, or host-key storage as a reversible change under change control. Record the PuTTY version string from Help → About, the Windows build, and whether Pageant was running. Those three facts explain a surprising fraction of “it works on my laptop” discrepancies.

When documenting the procedure for teammates, include: the saved session name, Host Name and Port from the Session panel, whether Connection type is SSH, the username, whether a PPK path is set under Connection → SSH → Auth, and whether agent forwarding is enabled. Explicitly state that Putty.info is an independent educational site and that binaries must be obtained from the official project download page. Link readers to safe download guidance, host key verification, and the official manual so they can cross-check labels that differ slightly across releases.

If you still need more diagnostics after following the sections above, reproduce the issue with logging enabled under Session → Logging to a local file you control, scrub secrets from the transcript, and compare against server auth logs for the same UTC timestamp. Avoid third-party “PuTTY fix” utilities. Prefer updating to the current stable release from official hosts, re-importing a known-good saved session, and testing from a second network path before declaring the workstation broken.

• Keep private keys passphrase-protected and backed up offline according to your organization's secret-handling policy.
• Prefer named saved sessions over ad-hoc connections for anything beyond a one-off debug.
• Disable unused tunnels and agent forwarding by default; enable them per session only when required.
• Schedule periodic key rotation and remove stale authorized_keys entries during access reviews.
• Teach new operators the difference between connection errors and authentication errors before giving them production bastion access.