Accessibility Statement

Standard we are working toward

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. This statement describes that target and where we currently stand. It is not a certification and it does not claim compliance with any law or regulation.

Current status: partially conformant

Okood is partially conformant with WCAG 2.2 level AA. This means that most of the site meets the target, but some parts do not yet. We tested the public pages with automated tools and reviewed the main flows by hand. We have not yet completed testing with every combination of browser, device and screen reader, so there may be problems we have not found.

What we have done

• Screen readers: buttons, links, form fields and menus have clear names, and updates such as loading states and confirmations are announced.
• Keyboard access: the main actions can be reached and used with the keyboard alone, including uploads and the menus in the signed-in areas.
• Visible focus: the keyboard focus indicator is easy to see on interactive elements.
• Skip link and landmarks: pages offer a "skip to main content" link and are organised into clear regions (header, navigation, main content, footer) with a logical heading structure.
• Color contrast: in this release we updated button colors, small text on dark backgrounds and secondary grey text to reach the contrast ratios WCAG requires. We will keep checking as the design changes.
• Signing a contract: besides drawing a signature, you can sign by typing your name, after you give explicit consent to sign that way.
• Dialogs: pop-up windows move focus inside when they open, keep it there, can be closed with the Escape key where it is safe to do so, and return focus to where you were.
• Arabic and right-to-left: pages, and the text within them, are marked with the correct language and direction, so screen readers pronounce each language properly and layouts read correctly in Arabic.
• Accessible emails: the emails we send are built with clear headings and descriptive subject lines so they can be read with assistive technology.

Known limitations

We want to be open about what is not yet fixed.

1. Contracts and records as PDF. The PDF contracts and project records you can download are not yet tagged for screen readers, so their structure may not be read correctly. For contracts and active projects, the same information is available in the page itself. Any PDF, including the record we email after a project is deleted, can be provided in an accessible form on request at support@okood.app (see "Help and feedback" below).
2. Signed-in screens. Some screens after sign-in have been tested with automated checks and by keyboard, but not yet with every screen reader. Some details are still being verified with real assistive technology, for example how the product tour is announced and menus in some browsers.
3. Small click targets. Some links and buttons, such as footer links and the monthly/yearly toggle on the pricing page, are smaller than recommended and can be hard to press precisely.
4. Emails. Some secondary text in our emails has low contrast, and the sign-in email sent by our authentication service has a layout that is not yet fully marked up for assistive technology.
5. Arabic coverage. Some pages, such as the privacy policy and terms of service, are currently available in English only. Some labels in the signed-in app are still announced in English, and some confirmation prompts use the browser’s built-in dialog in English only.

Help and feedback

If you have trouble using Okood, or you need information in another way, please contact us:

• Email: support@okood.app
• Expected response time: within 5 business days
• Alternative formats: on request we will provide contract and record information in another accessible format (for example plain text or an accessible document) or help you complete a task.

Please tell us the page you were on, what you were trying to do, and the device, browser and assistive technology you use, if you can.