Accessibility Statement
This page explains how SocialCRM approaches accessibility across its public site and product surfaces today.
On this page
Working standard
Scope
This statement covers the public marketing site at socialcrm.com, public developer content, and authenticated product surfaces delivered from the same application. It does not cover third-party websites, third-party software, or content outside SocialCRM's control.
How we approach accessibility
We try to keep new and updated work usable with standard browser and assistive technology workflows, including keyboard navigation, screen magnification, zoom, and screen readers.
In practice, that means we pay attention to:
- Semantic page structure and heading order
- Visible focus states for interactive controls
- Readable contrast and responsive layouts
- Clear labels, link text, and form feedback
- Alternative text for meaningful marketing imagery
Known limitations
Some areas of the product are more demanding than static marketing pages. At the time of this update, the most likely friction points are:
- Dense dashboard views and data-heavy interfaces
- Charts, tables, or monitoring views that may need clearer text alternatives
- Third-party services, embeds, or external destinations we link to
- Machine-generated or imported content that may need manual review
If you hit a blocker, the fastest way to get it fixed is to send us the page URL and a short description of what happened.
Feedback and support
We welcome reports about accessibility barriers, missing labels, keyboard traps, low-contrast content, or any workflow that is harder than it should be.
Accessibility contacts
- Accessibility
- accessibility@socialcrm.com
- General support
- support@socialcrm.com
- Contact form
- Use the public contact form
- What to send
- Page URL, issue summary, browser or device details, and the steps that led to the problem.
If you need information from one of our pages in another format, email us and we will try to help using the contact details above.
Changes to this statement
We update this statement when the published accessibility posture changes in a meaningful way, or when the underlying pages and workflows change enough to make the summary stale.