LEGAL // ACCESSIBILITY
Accessibility Statement
Accessibility is an engineering requirement on this site. The interface is built against the Web Content Accessibility Guidelines, and the controls for adjusting it live in the accessibility menu on every page.
Conformance statement
This site targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AAA, with Level AA treated as the hard floor beneath every decision. Where a Level AAA criterion is achievable within a terminal-style dark interface, we implement it. Where it conflicts with a genuine design constraint, we document the gap in the limitations below instead of claiming conformance we cannot demonstrate.
The site was self-assessed against WCAG 2.2 in October 2026 and is fully self-hosted: the conformance of every page you load is determined entirely by the code in this repository, with no third-party scripts, overlays, or widgets that could silently regress it. This is a self-declared conformance claim made by the ToolsLibrary Collective under the W3C conformance reporting model.
ACCESSIBILITY // FEATURE INVENTORY
Implemented accessibility features
Skip Link (WCAG 2.4.1)
A bypass block is the first focusable element on every page. Keyboard and screen-reader users can jump past the navigation straight to the main content.
Keyboard Shortcuts (WCAG 2.1.1)
All functionality is operable from a keyboard. Alt+A opens the accessibility menu, Alt+M moves focus to the main content, and Escape closes the menu and returns focus to its trigger.
High-Contrast Mode (WCAG 1.4.6 AAA)
An optional contrast mode renders pure black backgrounds with white text and yellow highlights. All text then meets the enhanced 7:1 contrast requirement.
Text Spacing Toggle (WCAG 1.4.12)
A one-click control increases line height, letter spacing, and word spacing site-wide so no content or functionality is lost when text is re-spaced.
Dyslexia-Friendly Font Stack
A locally bundled OpenDyslexic font stack can be enabled globally. Its letterforms reduce mirroring and crowding for readers with dyslexia.
Font Scaling to 150% (WCAG 1.4.4)
Text can be scaled to 125% and 150% from the accessibility menu without loss of content or functionality; layouts reflow instead of clipping or overlapping.
Enhanced Focus Indicators (WCAG 2.4.11 / 2.4.13)
Keyboard focus is always visible, and the enhanced mode draws a bold yellow outline with a black halo that exceeds the focus-appearance minimums in WCAG 2.2.
Focus Never Obscured (WCAG 2.4.11)
Scroll padding is reserved above every focused target so the sticky navbar can never cover the element receiving keyboard focus during tabbing or fragment navigation.
44px Minimum Targets (WCAG 2.5.8 AAA)
Every control inside the accessibility menu (radios, switches, and buttons) meets the 44 by 44 CSS pixel target-size practice, well beyond the 24px minimum.
Reduced Motion (WCAG 2.3.3 AAA)
Animations and transitions can be disabled from the menu, and the site independently honors the operating-system prefers-reduced-motion setting.
Reading Guide
An optional horizontal bar follows the pointer down the page so readers with tracking difficulties can keep their place in long lines of text.
Large High-Contrast Cursor
An enlarged yellow pointer with a black outline can be enabled for low-vision users who struggle to locate the default cursor against dark backgrounds.
Live-Region Announcements (WCAG 4.1.3)
Every accessibility settings change is announced through a polite screen-reader live region, so status messages reach assistive technology without moving focus.
Consistent Help Link (WCAG 3.2.6)
The Request Help link appears in the footer in the same position on every page.
No Drag-Only Interactions (WCAG 2.5.7)
Nothing on this site requires dragging. All actions can be completed with single taps, clicks, or key presses. There are no multipoint or path-based gestures.
Accessible Authentication (WCAG 3.3.8 / 3.3.9)
Signing in requires no cognitive function tests: there are no puzzles, memorization tasks, or transcription challenges, and single-use recovery codes offer an object-free backup path.
Underline Links Toggle (WCAG 1.4.1)
Links can be force-underlined site-wide so that color is never the only visual means of identifying a link.
WCAG 3.0 (draft) adoptions
WCAG 3.0 is currently a W3C Working Draft. It is published for review, it is explicitly not yet a W3C Standard, and its requirements may change before it reaches Recommendation status. We track the draft because it moves toward outcome-based scoring, broader personalization, and graded usability research. We have adopted the draft practices that are already implementable today:
Focus Appearance Beyond Minimums
Focus indicators are larger, thicker, and higher-contrast than the WCAG 2.2 minimum. This anticipates the stronger focus-appearance guidance drafted for WCAG 3.0.
Operating-System Preference Respect
The site honors prefers-reduced-motion, prefers-contrast, and forced-colors directly from your operating system, even before you touch any in-app toggle.
Personalization via User Preferences
Contrast, font size, spacing, motion, cursor, and link styling are user-controlled preferences persisted anonymously in a cookie and synced to your account. This matches the personalization model being drafted for WCAG 3.0.
Plain-Language Structure
Pages are organized under descriptive headings, with consistent navigation and short, direct sentences. This follows the plain-language direction of the WCAG 3.0 draft.
Outcome-Based Scoring Commitment
As the WCAG 3.0 outcome-based scoring model stabilizes toward W3C Recommendation, we commit to adopting it for future conformance assessments of this site.
Known limitations
- Full AAA contrast across every gradient headline is not yet universal; a small number of decorative gradient treatments still fall between the AA and AAA contrast thresholds.
- The third-party Project Wiki (wiki.tools-library.com) and the Matrix chat interface are separate self-hosted services outside this application's codebase, and their conformance is not covered by this statement.
- Automated testing supplements but does not replace manual audit; automated tools catch only a subset of WCAG success criteria, and this statement reflects a self-assessment rather than an independent certification.
Feedback and contact
If any part of this site is difficult or impossible for you to use, we want to hear about it. Barriers reported by real users are the fastest route to a fix. Use the Request Help link in the footer of every page, or reach the collective in the Matrix Chat. Both channels are zero-PII by design: we collect no email address, phone number, or name, so reporting a barrier requires no personal data.
We aim to acknowledge accessibility feedback within five business days and to ship a remediation or a documented workaround for confirmed barriers as a priority change.
This statement concerns this application only. See the Privacy Policy for how the anonymous accessibility preferences are stored.