docs: update content

docs/src/docPages/examples/basic.md

@@ -1,3 +1,5 @@
-# Basic text editor
+# Default text editor
+
+Did we mention that you have full control over the rendering of the editor? Here is barebones example without any styling, but packed with a whole set of common extensions.
 
 <demo name="Examples/Basic" />

docs/src/docPages/examples/book.md

@@ -1,5 +1,7 @@
 # Write a book
 
-This demo has 150 paragraphs and more than 13,000 words, check the performance yourself. The most heavy processing is to check the active state of the buttons for the selection. If you’d like to optimize for that use case, try to limit those checks in your toolbar. But honestly, we think it’s great already, isn’t it?
+This demo has 150 paragraphs and more than 13,000 words, check the performance yourself.
+
+Most of the processing is needed to check the active state of the buttons for the selection. If you’d like to optimize for really long texts, try to limit these checks in your toolbar. But honestly, we think it’s great already, isn’t it?
 
 <demo name="Examples/Book" highlight="" />

docs/src/docPages/experiments.md

@@ -5,4 +5,4 @@ Congratulations! You’ve found our secret playground with a list of experiments
 * [Annotation](/experiments/annotation)
 * [Comments](/experiments/comments)
 * [CharacterLimit](/experiments/character-limit)
-* [Colors](/experiments/colors)
+* [Color](/experiments/color)

docs/src/docPages/experiments/color.md

@@ -0,0 +1,5 @@
+# Color
+
+⚠️ Experiment
+
+<demo name="Experiments/Color" highlight="" />

docs/src/docPages/experiments/colors.md

@@ -1,5 +0,0 @@
-# Colors
-
-⚠️ Experiment
-
-<demo name="Experiments/Colors" highlight="" />

docs/src/docPages/guide/accessibility.md

@@ -10,7 +10,9 @@ We need your support to maintain, update, support and develop tiptap 2. If you
 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 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.
+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.
 
 ### Editor
 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.
@@ -28,3 +30,5 @@ An optional writing assitance could help people writing content semanticly corre
 | WCAG 2.1 | 2.1.1   | [Keyboard](https://www.w3.org/WAI/WCAG21/Understanding/keyboard)                       |
 | WCAG 2.1 | 4.1.1   | [Parsing](https://www.w3.org/WAI/WCAG21/Understanding/parsing)                         |
 | WCAG 2.1 | 4.1.2   | [Name, Role, Value](https://www.w3.org/WAI/WCAG21/Understanding/name-role-value)       |
+
+Anything we should add here? Please let us know, so we can take it into account.