Accessibility

• Semantic HTML structure, and full keyboard navigation through the main flows.
• Alt text on images that carry meaning.
• Color contrast that targets WCAG 2.2 Level AA ratios.
• Full bilingual support — Arabic with RTL, English with LTR — held to the same standard of care.

This commitment covers the public string.education site and the String teacher and student application alike. It does not currently cover content files uploaded by a third party — a PDF a teacher uploads themselves, for instance — because String does not control how that file was produced.

Some interactive content — charts and diagrams inside lessons, for instance — has not yet been fully tested with screen readers, and some downloadable PDFs are not yet fully tagged for accessibility. A full color-contrast review of the Arabic, RTL interface specifically has not yet been completed. This is a starting list that will update as the work progresses, not a final list or a completed audit result.

We aim to test core flows with a screen reader (such as NVDA or VoiceOver) and with keyboard-only navigation, as ongoing work — not a step we complete once and close. Every new feature is built with this goal in mind from the start, not retrofitted onto it afterward.

We have not yet run an independent, external accessibility audit. When we do, the result will be stated here plainly — whether it is favorable or not.

If you hit a barrier using String because of a disability, tell us through the channels below, with the page and the problem described. We review every report and respond within a reasonable timeframe.