Accessibility
Ink aims to be usable by writers with different devices, abilities, input methods, and visual preferences.
Our approach
Ink uses semantic controls, visible keyboard focus, labeled interface elements, keyboard shortcuts, responsive layouts, reduced-motion support, and scalable browser text. Its five theme packs provide coordinated light and dark palettes, and selected writer tools expose programmatic pressed states. Legal pages and core navigation are designed to work without a mouse.
Ink uses WCAG 2.2 Level AA as a design and testing target. This statement is not a formal conformance claim. The primary, secondary, and accent text colours in each current theme pack have been contrast-checked, but automated checks do not replace keyboard, screen-reader, zoom, forced-colour, and human usability testing.
Typewriter mode may play low-volume mechanical key sounds after you activate it. These sounds are decorative: no instruction, status, or content is communicated by audio alone. Browsers that block or do not support web audio can still use the mode’s font, active-block focus, and vertical-centering behavior.
Known limitations
Rich-text editing through browser content-editable controls can behave differently across browsers, screen readers, mobile keyboards, and voice-input tools. Some floating formatting and selection behaviors may require further assistive-technology testing. Theme previews, browser print output, third-party authentication screens, and custom user or extension styles may also differ from the intended presentation.
Feedback
If something prevents you from writing or reading comfortably, contact jtredoux69420@gmail.com. Include the page, browser, assistive technology, and problem encountered if you are comfortable doing so.
Ongoing work
Ink continues to be tested against WCAG 2.2 with keyboard-only navigation, 200% and 400% zoom, reflow, forced colours, reduced motion, current screen readers, accessible authentication, iOS VoiceOver, Android TalkBack, and common desktop browsers.