fix: barrier-free

Author: deleonio

dev/i18n/en/docusaurus-plugin-content-blog/2023-01-04.mdx

@@ -5,7 +5,7 @@ tags: ['website', 'seo', 'spec']
 ---
 
 As an open source project, it is important for KoliBri to have a community around
-to build up the topic of barrier-free basic components. So for this too
+to build up the topic of accessible basic components. So for this too
 optimal accessibility is given, all technical
 Specifications must be available in at least **English**. As in the
 Science allows for feedback and participation from all potential

dev/i18n/en/docusaurus-plugin-content-docs/current/01-manifest.mdx

@@ -23,7 +23,7 @@ tags:
 	</p>
 	<h2>§ 3 Portability</h2>
 	<p>
-		The focus is on small components (e.g. buttons) that can be easily reused. The special thing about this is that an HTML button or input is not barrier-free
+		The focus is on small components (e.g. buttons) that can be easily reused. The special thing about this is that an HTML button or input is not accessible
 		without further ado. However, a KoliBri button or input takes into account the numerous use cases and the semantic construction of the components that must
 		be considered.
 	</p>
@@ -40,7 +40,7 @@ tags:
 	</p>
 	<h2>§ 6 Security</h2>
 	<p>
-		All components serve solely to achieve a consistent and barrier-free representation of web-based user interfaces in the sense of a corporate design or
-		design system. We provide a universally applicable and subject-neutral library without any data transfer functionalities and storage.
+		All components serve solely to achieve a consistent and accessible representation of web-based user interfaces in the sense of a corporate design or design
+		system. We provide a universally applicable and subject-neutral library without any data transfer functionalities and storage.
 	</p>
 </div>

dev/i18n/en/docusaurus-plugin-content-docs/current/03-faq.mdx

@@ -17,11 +17,11 @@ import { KolLink } from '@public-ui/react';
 ## General
 
 - **What is so special about KoliBri?**<br/>
-  KoliBri offers granular, easily reusable HTML compositions that are semantically barrier-free and decoupled from the design. Using the basic styling, which is limited exclusively to the layout, the components can be easily adapted to your own corporate design.
+  KoliBri offers granular, easily reusable HTML compositions that are semantically accessible and decoupled from the design. Using the basic styling, which is limited exclusively to the layout, the components can be easily adapted to your own corporate design.
 - **How ​​do you save with KoliBri?**<br/>
   Websites/applications are implemented with different HTML elements and variants of elements. Each of these HTML structures must be semantically accessible and marked. KoliBri focuses on exactly such HTML structures and their variants and summarizes them in clearly defined components. The development teams that later reuse KoliBri can now use these components and adjust parameters to display different variants without having to think about the correctness of the HTML structure within the component. You are relieved and can focus more on the implementation of the actual technicality.<br/>
 - **How ​​can you not explain KoliBri technically?**<br/>
-  KoliBri is for accessibility like a Thermomix® is for cooking. It makes cooking easier because you can simply choose a suitable dish (component) without having to know how to cook it exactly. The Thermomix® (KoliBri) guides you through the cooking process (parameters for different variants) and ensures that the right dish (barrier-free user interface) comes out at the end.
+  KoliBri is for accessibility like a Thermomix® is for cooking. It makes cooking easier because you can simply choose a suitable dish (component) without having to know how to cook it exactly. The Thermomix® (KoliBri) guides you through the cooking process (parameters for different variants) and ensures that the right dish (accessible user interface) comes out at the end.
 - **How ​​dependent will I be if I use KoliBri?**<br/>
   If you compare KoliBri with a LEGO® set, you can simply mix the building blocks it contains with other building blocks to depict the overall application. You enter into a partial dependency (logical) in order to receive advantages in ensuring accessibility in return.
 - **How ​​can I influence a component if necessary?**<br/>
@@ -49,8 +49,8 @@ import { KolLink } from '@public-ui/react';
 
 ## Technical
 
-- **Why can KoliBri components really be barrier-free?**<br/>
-  The KoliBri components are designed in terms of software architecture in such a way that they can only be instrumented via properties and not via their own HTML that can be entered. This means that the components can only be controlled via the API (properties). This is a quality feature because the components cannot be manipulated from the outside. The components are very restrictive and can therefore always be barrier-free.<br/>
+- **Why can KoliBri components really be accessible?**<br/>
+  The KoliBri components are designed in terms of software architecture in such a way that they can only be instrumented via properties and not via their own HTML that can be entered. This means that the components can only be controlled via the API (properties). This is a quality feature because the components cannot be manipulated from the outside. The components are very restrictive and can therefore always be accessible.<br/>
   In order to be able to break out of this restriction, there is the <KolLink _href="/docs/concepts/expert-slot" _label="Expert-Slot" />, which makes it possible to embed your own HTML in the component. Accessibility via the expert slot is in the hands of the expert (developer) and should only be used in exceptional cases.
 - **Why are component properties sometimes named differently from HTML naming?**<br/>
   In order to keep KoliBri easy to learn, the HTML naming is usually used. But even the HTML standard is not uniform in its naming across several elements (components). And that is why we have chosen uniform names for similar properties in KoliBri. See concept <KolLink _href="/docs/concepts/properties" _label="Properties" /> for more information.

dev/i18n/en/docusaurus-plugin-content-docs/current/40-project/01-history.md

@@ -47,7 +47,7 @@ We now knew that the technology was powerful and concentrated on supplying the p
 
 We want to build a broad community around the topic "small flexible accessible web components", KoliBri for short. KoliBri as an accessible webcomponent library is free to use and should be developed collaboratively.
 
-Why this is worthwhile can be derived from the guidelines of KoliBri. The focus is on small frequently occurring components and their HTML construction. These HTML constructions must be solved namely as a rule by all development teams, which must provide barrier-free web-based user interfaces. If one looks attentively with the "accessibility glasses" in the Web, one notices that for example the Button with the Tooltip, all nearly the same implemented.
+Why this is worthwhile can be derived from the guidelines of KoliBri. The focus is on small frequently occurring components and their HTML construction. These HTML constructions must be solved namely as a rule by all development teams, which must provide accessible web-based user interfaces. If one looks attentively with the "accessibility glasses" in the Web, one notices that for example the Button with the Tooltip, all nearly the same implemented.
 And this is exactly what KoliBri addresses with the small-part components. We turn the openly specified HTML (not readily accessible) into semantic accessible HTML components by means of web components, which can be reused flexibly and customizable for your own design systems and web projects.
 
 ## Prospect `2023`