Accessibility Statement

Effective 2 November 2026

We want everyone to be able to use PostWide. This statement explains where we stand on accessibility, what we have done so far, the gaps we know about, and how to tell us about a barrier.

1. Where we stand

DevMod LLC wants PostWide to be usable by everyone, including people who use assistive technology such as screen readers, keyboard navigation or screen magnification.

PostWide has not been audited against an accessibility standard, such as the Web Content Accessibility Guidelines (WCAG) 2.1 or Israeli Standard 5568, and it does not claim conformance with one.

We work to fix barriers that people report to us. Our automated tests check the pages of the website, and the app screens they visit, for common accessibility problems.

This statement covers the PostWide website at postwide.co and the PostWide app at app.postwide.co.

2. What we have done

  • Pages use semantic HTML, with a main area, labelled navigation and headings, so screen readers can move through them.
  • Links, buttons and form controls are standard HTML elements that work with a keyboard, and the element in focus shows a visible focus ring.
  • App pages that show the app’s navigation, both for agency staff and for the clients they invite, start with a “Skip to content” link.
  • Every page of the website also starts with a “Skip to content” link.
  • Icons that only decorate are hidden from screen readers, and buttons that show only an icon, such as the theme switch, have a text label.
  • When your device asks for reduced motion, the website turns off its animations and smooth scrolling, and the app turns off its loading and dialog animations.
  • Both the website and the app have light and dark themes. The app can also follow your device’s setting.
  • Pages do not block zooming, and their layout adapts to narrow screens, so you can enlarge them with your browser’s zoom.
  • Form fields in the app have labels that assistive technology reads out.
  • Every page declares that it is in English, so screen readers pronounce it correctly.
  • Our automated tests check each app screen they visit with the axe accessibility checker, which flags common accessibility problems, and fail on serious or critical ones.
  • Our test suite also checks every page of the website with axe and fails on any problem it finds. That check runs without a browser, so it leaves out colour contrast.

3. Known limitations

  • The app is under active development. We review it for accessibility feature by feature, so a new or changed feature may have gaps until it has been reviewed.
  • Some steps happen on pages run by other companies: the sign-in and permission pages of the social networks you connect, Google sign-in, and the Paddle checkout. Those providers control how accessible their pages are.
  • The images and videos in your posts are your own content. The composer lets you add alt text to each image, and we send it to the networks that accept it, such as Instagram and X. A post published without alt text has no description on the network.
  • Thumbnails of your media inside the app are not described separately for screen readers.

4. Report a barrier or ask for another way

Our accessibility coordinator is Eilon Udi. Email eilon@devmod.co to report a barrier, ask for content in another format or get help completing a task.

Tell us the page or feature, what you were trying to do and, if you use one, the assistive technology involved.

We aim to acknowledge your message within 2 business days. We will then fix the problem or give you another way to complete the task.

5. Review of this statement

This statement was last reviewed on 2 November 2026. We review it at least once a year and whenever the website or the app changes materially.

Also read our Privacy Policy, Terms of Use and Refund Policy.