Accessibility statement

ChirpWater LLC is responsible for this statement, for the accessibility of the Clean Page application at cleanpage.app, and for fixing any barrier reported to it.

Conformance

Clean Page conforms to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Because WCAG 2.2 is backward compatible, the application also meets WCAG 2.1 Level AA and WCAG 2.0 Level AA on the same evidence. Those are the standards referenced by Section 508 of the Rehabilitation Act and by the 2024 rule under Title II of the Americans with Disabilities Act.

This is a self-assessment by ChirpWater LLC following the W3C's evaluation methodology (WCAG-EM). It is not a third-party certification. The evaluation was completed September 19, 2026 against the build that ships to cleanpage.app.

"Not applicable" criteria govern content the application does not contain, such as audio, video, sign-in, or multi-page navigation. Under WCAG's conformance rules they are satisfied.

The full conformance report, and an Accessibility Conformance Report in the VPAT® format, are available on request from the contact below.

How it was evaluated

• The axe-core rule engine, with its WCAG 2.0, 2.1, and 2.2 rule sets, was run across nineteen states of the interface: the writing surface, the toolbar, every dialog, light and dark colors, both text sizes, narrow widths, high zoom, Windows high contrast mode, reduced-motion preference, print, and the WCAG text-spacing override. It reported no violation in any state. IBM Equal Access was run as a second engine and also reported no violation.
• Color contrast, target size, keyboard behavior, focus handling, and status announcements were measured directly, including inside dialogs where automated engines do not compute.
• Each of the 55 success criteria was assessed individually against the normative text, with evidence recorded for every result.

How it works with assistive technology

• The writing area is a standard text field. To the operating system and to assistive technology it is an ordinary editable field. Screen readers, dictation, magnification, switch access, and on-screen keyboards work with it as they do with any text field.
• Every control is a native element. Buttons are buttons, choices are radio buttons, and dialogs are dialogs. Each has an accessible name.
• Everything works from the keyboard. The toolbar is reached with one key, its buttons are walked with the arrow keys, and Escape returns to writing. Dialogs keep focus until they close. There are no keyboard traps and no timed actions.
• Familiar shortcuts. The navigation shortcuts follow the pattern used by Google Docs on Chromebooks.
• High contrast by default. Writing appears as near-black on white, or near-white on dark, above the WCAG minimum in both modes. Windows high contrast mode is supported.
• Readable choices. Settings offer two typefaces, Serif and Sans-serif; two text sizes, Regular and Large; and Light or Dark on-screen colors. Browser zoom and the browser's own font-size preference are honored, and the page repaginates rather than clipping.
• Room for touch. On touch devices every button meets the 44-pixel target size.
• Quiet status. "Changes saved" and the page count are announced only when they change, so a screen reader stays quiet while you type.
• Nothing moves or flashes. There are no animations, no auto-updating content, and no motion-based input.
• Printing is plain. The printed page is black text on white paper in either color mode, with nothing added.

Keyboard reference

• Alt+F moves from the writing area to the toolbar. Alt+E moves to Undo. Alt+T opens Settings. Ctrl+Alt+Shift+M also leaves the writing area.
• In the toolbar, Left and Right arrows move between buttons, Home and End jump to either end, and Escape returns to writing. Shift+Tab from the writing area also reaches the toolbar.
• Tab inside the writing area types a tab character.
• Ctrl+S saves, Ctrl+O opens, Ctrl+P prints, Ctrl+Z undoes, and Ctrl+Shift+Z or Ctrl+Y redoes.
• On macOS, use Control+Option in place of Alt, and Cmd in place of Ctrl.

Known limitations

• The accessibility tree was inspected, but no screen reader was listened to.
• The evaluation ran in Chromium. Firefox and Safari were not evaluated.
• Touch and tablet mode on convertible Chromebooks were not exercised.
• The bundled typefaces cover Latin scripts. Text in other scripts, such as Chinese, Japanese, or Korean, uses the fonts on your device.
• Printed output and the operating system's file and print dialogs are outside the scope of WCAG and were not evaluated.

Report a barrier

If something in Clean Page does not work for you or for someone you support, we want to know. Email Jeffrey Green, owner, ChirpWater LLC, at jeff@chirpwater.com with the action you were taking, what happened, and the browser, device, and assistive technology in use. Please leave names and personal writing out of the message. Requests for the conformance report or an Accessibility Conformance Report go to the same address.

Responsible party