Welcome
Learn here why
Vision
Together, we make HTML semantically accessible using reusable Web Components to ensure usability and accessibility.
Mission
The
HTML web standard
is specified to be very "open" in order to be as durable and robust as possible. It therefore often happens that HTML compositions are not readily accessible, semantic and valid.
W3C
web standards
(framework-agnostic), is thereby a generic reference implementation of the
WCAG standard
and
BITV
for accessibility, and is implemented as a multi-theme-enabled presentation layer. There is no technical reference and no data transfer functionalities. This makes
Collaboration and cooperation
The focus of
We should collaborate and cooperate on these atomic components in order to bundle our skills and knowledge. Through the synergy effects at the basic components, our own focus can be placed more on subject-specific content.
Let us make
License
Making accessible: The artifacts and source code can be reused freely and without charge by anyone. In this way, the ITZBund makes a contribution in the sense of
“Public Money – Public Code”
.
Warranty and liability disclaimer: No warranty or liability claims are associated with the reuse.
“Copyleft” clause: Copyleft states that any copy of
KoliBri (fork) must be re-released under the same or a compatible open-source license.
Delimitation
To use
Styling
The more relevant components are found and implemented, the more value is added to all web-based projects. However,
Rendering
Web components can be rendered on the client side (CSR), prerendered (SSG), or on the server side (SSR). The rendering depends on the respective technical framework conditions (
,
).
💡 It should be noted that Web Components is a JavaScript-based web standard. Server-side rendering allows the Web Component to be rendered for optimal display speed on the client. If client-side JavaScript is allowed, the full dynamics of the Web Component are also available client-side. However, if you want to avoid using JavaScript on the client side, the Web Component is rendered, but the dynamics are lost. 🧪 Server-side rendering of Web Components is an exciting new functionality where adjustments to the prerenderer will still be necessary and is therefore classified as experimental on our part ( ).
Versioning
Structure of a version:
It usually consists of 3 parts (e.g. 1.0.2)
Major, here the 1
Minor, here the 0
Patch, here the 2
For the release phase of a version, you can use additional labels (e.g. 1.0.3-rc.2)
Label, here the rc.2
The following main principles are applied:
Patch: Includes changes that improve the current functionality and do not change its use.
Minor: Includes changes that extend the functional scope and do not change the existing functional scope in its use.
Major: Includes changes that enable architectural realignment and are allowed to change the use of the existing feature set.
You can find the complete description of the SemVer here:
Quality objectives
The following table lists the prioritized qualities of
Device, operating system, browser and screen reader requirements
Microsoft Internet Explorer is explicitly not supported in order not to weaken the project and the development by legacy. Instead,