Accessibility
Accessibility Statement
This accessibility statement applies to the Wordsmith.ai web application, desktop application, and plugins (e.g., Slack, Microsoft Word).
We believe everyone deserves equal access to legal tools. That’s why we’re working to build inclusive products that work for people of all abilities, and anyone interacting with our services across different devices and contexts.
Accessibility is an ongoing journey, and while we’re not perfect yet, we’re committed to continuous improvement.
Legal Basis
This statement supports compliance with the European Accessibility Act (Directive (EU) 2019/882), which becomes enforceable from 28 June 2025. It also aligns with the principles of the WCAG 2.1 Level AA accessibility standard.
These standards help ensure that digital products are perceivable, operable, understandable, and robust for all users — including people relying on keyboard navigation, screen readers, or reduced motion preferences.
Accessibility Status
We are currently partially conformant with WCAG 2.1 AA. This means that while much of our product is accessible, some areas do not yet fully meet the required standards.
Known Accessibility Limitations
Based on internal audits and automated testing (e.g., Axe), we’ve identified the following common issues affecting some components:
Low color contrast in text and UI elements; missing or non-descriptive alternative text for images
Incomplete keyboard access to interactive elements; lack of pause/stop controls for autoplay or motion content
Missing or skipped heading levels; lack of semantic landmarks; improper list structures
Inconsistent or incorrect ARIA roles and attributes; missing accessible names for links, buttons;
Assistive technology support may be limited in complex interactive elements.
We are exploring ways to address these limitations through accessibility improvements over time.
What We're Doing to Improve
We’ve started embedding accessibility into our development process. Current actions include:
Running regular accessibility audits (manual + automated)
Using static analysis tooling like eslint-plugin-jsx-a11y and automation testing tool Axe
Trainings team members for inclusive accessibility best practices
Where full fixes are not immediately feasible, we assess the risk, document it, and prioritize improvements based on user impact.
Feedback & Contact
We’re always looking to improve. If you face an accessibility barrier or need content in a different format, please reach out:
Email: accessibility@wordsmith.ai
Response time: We aim to reply within 5 business days
Your feedback helps us prioritize and build better.
Statement Details
Prepared: 14 May 2025.
Audit method: Internal audit using Axe and manual keyboard navigation checks; screen reader testing has not yet been conducted.
Next review: Before 28 June 2026.
This statement will be updated as accessibility work progresses.
Accessibility Statement
This accessibility statement applies to the Wordsmith.ai web application, desktop application, and plugins (e.g., Slack, Microsoft Word).
We believe everyone deserves equal access to legal tools. That’s why we’re working to build inclusive products that work for people of all abilities, and anyone interacting with our services across different devices and contexts.
Accessibility is an ongoing journey, and while we’re not perfect yet, we’re committed to continuous improvement.
Legal Basis
This statement supports compliance with the European Accessibility Act (Directive (EU) 2019/882), which becomes enforceable from 28 June 2025. It also aligns with the principles of the WCAG 2.1 Level AA accessibility standard.
These standards help ensure that digital products are perceivable, operable, understandable, and robust for all users — including people relying on keyboard navigation, screen readers, or reduced motion preferences.
Accessibility Status
We are currently partially conformant with WCAG 2.1 AA. This means that while much of our product is accessible, some areas do not yet fully meet the required standards.
Known Accessibility Limitations
Based on internal audits and automated testing (e.g., Axe), we’ve identified the following common issues affecting some components:
Low color contrast in text and UI elements; missing or non-descriptive alternative text for images
Incomplete keyboard access to interactive elements; lack of pause/stop controls for autoplay or motion content
Missing or skipped heading levels; lack of semantic landmarks; improper list structures
Inconsistent or incorrect ARIA roles and attributes; missing accessible names for links, buttons;
Assistive technology support may be limited in complex interactive elements.
We are exploring ways to address these limitations through accessibility improvements over time.
What We're Doing to Improve
We’ve started embedding accessibility into our development process. Current actions include:
Running regular accessibility audits (manual + automated)
Using static analysis tooling like eslint-plugin-jsx-a11y and automation testing tool Axe
Trainings team members for inclusive accessibility best practices
Where full fixes are not immediately feasible, we assess the risk, document it, and prioritize improvements based on user impact.
Feedback & Contact
We’re always looking to improve. If you face an accessibility barrier or need content in a different format, please reach out:
Email: accessibility@wordsmith.ai
Response time: We aim to reply within 5 business days
Your feedback helps us prioritize and build better.
Statement Details
Prepared: 14 May 2025.
Audit method: Internal audit using Axe and manual keyboard navigation checks; screen reader testing has not yet been conducted.
Next review: Before 28 June 2026.
This statement will be updated as accessibility work progresses.
Accessibility Statement
This accessibility statement applies to the Wordsmith.ai web application, desktop application, and plugins (e.g., Slack, Microsoft Word).
We believe everyone deserves equal access to legal tools. That’s why we’re working to build inclusive products that work for people of all abilities, and anyone interacting with our services across different devices and contexts.
Accessibility is an ongoing journey, and while we’re not perfect yet, we’re committed to continuous improvement.
Legal Basis
This statement supports compliance with the European Accessibility Act (Directive (EU) 2019/882), which becomes enforceable from 28 June 2025. It also aligns with the principles of the WCAG 2.1 Level AA accessibility standard.
These standards help ensure that digital products are perceivable, operable, understandable, and robust for all users — including people relying on keyboard navigation, screen readers, or reduced motion preferences.
Accessibility Status
We are currently partially conformant with WCAG 2.1 AA. This means that while much of our product is accessible, some areas do not yet fully meet the required standards.
Known Accessibility Limitations
Based on internal audits and automated testing (e.g., Axe), we’ve identified the following common issues affecting some components:
Low color contrast in text and UI elements; missing or non-descriptive alternative text for images
Incomplete keyboard access to interactive elements; lack of pause/stop controls for autoplay or motion content
Missing or skipped heading levels; lack of semantic landmarks; improper list structures
Inconsistent or incorrect ARIA roles and attributes; missing accessible names for links, buttons;
Assistive technology support may be limited in complex interactive elements.
We are exploring ways to address these limitations through accessibility improvements over time.
What We're Doing to Improve
We’ve started embedding accessibility into our development process. Current actions include:
Running regular accessibility audits (manual + automated)
Using static analysis tooling like eslint-plugin-jsx-a11y and automation testing tool Axe
Trainings team members for inclusive accessibility best practices
Where full fixes are not immediately feasible, we assess the risk, document it, and prioritize improvements based on user impact.
Feedback & Contact
We’re always looking to improve. If you face an accessibility barrier or need content in a different format, please reach out:
Email: accessibility@wordsmith.ai
Response time: We aim to reply within 5 business days
Your feedback helps us prioritize and build better.
Statement Details
Prepared: 14 May 2025.
Audit method: Internal audit using Axe and manual keyboard navigation checks; screen reader testing has not yet been conducted.
Next review: Before 28 June 2026.
This statement will be updated as accessibility work progresses.
© 2025 Wordsmith. All rights reserved.
© 2025 Wordsmith. All rights reserved.
© 2025 Wordsmith. All rights reserved.