Accessibility
Fund the development ♥
We need your support to maintain, update, support and develop Tiptap. If you’re waiting for progress here, become a sponsor and fund our work.
Introduction
We strive to make Tiptap accessible to everyone, but to be honest, there’s not much work done now. From our current understanding, that’s what needs to be done:
Interface
An interface needs to have well-defined contrasts, big enough click areas, semantic markup, must be keyboard accessible and well documented. Currently, we don’t even provide an interface, so for now that’s totally up to you.
But no worries, we’ll provide an interface soon and take accessibility into account early on.
Output
The editor needs to produce semantic markup, must be keyboard accessible and well documented. The Tiptap content is well structured so that’s a good foundation already. That said, we can add support and encourage the usage of additional attributes, for example the Alt-attribute for images.
Writing assistance (optional)
An optional writing assitance could help people writing content semanticly correct, for example pointing out an incorrect usage of heading levels. With that kind of assistance provided by the core developers, we could help to improve the content of a lot of applications.
Resources
| Document | Section | Heading |
|---|---|---|
| WCAG 3.0 | 7.1 | Text Alternatives |
| WCAG 2.1 | 1.1.1 | Non-text Content |
| WCAG 2.1 | 2.1 | Keyboard Accessible |
| WCAG 2.1 | 2.1.1 | Keyboard |
| WCAG 2.1 | 4.1.1 | Parsing |
| WCAG 2.1 | 4.1.2 | Name, Role, Value |
| WCAG 2.1 | 2.1.2 | No Keyboard Trap |
TODO: Update resources to point to WCAG 3.0 https://www.w3.org/TR/wcag-3.0/
Anything we should add here? Please let us know, so we can take it into account.