Accessibility statement
We build to WCAG 2.2, level AA. This page lists what we check, the gaps we know about, and how to tell us when something does not work for you.
The standard. We build editwise.io, the review links your clients open, and the client portal to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA.
What we do
- Text has a contrast ratio of at least 4.5 to 1. Buttons, form fields and focus outlines have at least 3 to 1.
- Every page works with a keyboard alone, with a visible focus outline, a skip link and no keyboard traps.
- Pages reflow at 320 pixels wide and at 400 percent zoom without sideways scrolling. Wide tables scroll inside their own box.
- Form fields have visible labels. Error messages say what went wrong and how to fix it.
- Headings follow in order, so a screen reader can move through a page heading by heading.
- Pictures of the product carry text alternatives.
Known gaps
- Product pictures on this site are pictures. The screenshots of EditWise on editwise.io are images of the app, not the app itself. Each one has a text alternative, but a screen reader user gets a description of the screen, not a working screen.
- Touch targets in the client portal. Some checkboxes, radio buttons and icon buttons in the client portal are built to a 24-pixel desktop minimum. That is smaller than the 44 by 44 pixels we want on touch screens, so we are raising them to 44 pixels.
Tell us what does not work
If something on editwise.io, in a review link or in the client portal does not work for you, email us at contact@editwise.io Tell us the page and what you were trying to do. We reply within a few business days in most cases. If we cannot fix it quickly, we will send you what you need in another form.
Review
We review this statement when we introduce significant changes, and after every audit.