We would like to give you the opportunity to read about the development of KoliBri and have collected all the groundbreaking events for you on this page.
In public administration, we are legally obligated to make all digital offerings accessible to everyone. Furthermore, we want to implement our digital products as efficiently and flexibly as possible, and this requires sound and consolidated standards.
In deciding to create our own component library from scratch, we were largely guided by the goals of the ITZBund and the federal government's IT strategy. In addition, the maturity of the Web component standard, combined with the final replacement of Internet Explorer, played a major role at the time.
Existing UI libraries were very design-driven and framework-specific. Semantic accessibility was not a focus when components were designed. In addition, most of the libraries in question, as popular as they are, are outside of our scope to quickly implement requirements within the scope of our legislation.
For us, it was important in making the decision to be as independent and sovereign as possible. With the breakthrough of the Web Component Standard, we can implement a single-source strategy and build all components from the ground up with the guidelines of the W3C, WCAG and BITV, and continuously improve them.
The free design of the components comes only at the end and participates from the self-contained accessible base components. By having the UI/UX designers deal with the restrictive components, you always have the accessibility and technical side in mind.
With KoliBri as a standard, we also create a place where everyone can interact, regardless of developer, designer or tester. The knowledge, experience and feedback of all contributes to the improvement of the standard.
In mid-2020, we created a prototype using a TSX-based framework to realize the vision. Thanks to the prototype and a detailed project description, the desired goals, we were able to initiate an internal project to create standardized, flexible and accessible components.
At the beginning of 2021, we started with an internal project and initially implemented the most important components and coordinated the test procedure. After conducting an initial full BITV test, we found the first reference projects in the ITZBund during the course of the year that used KoliBri and gave us feedback. With the help of the feedback, we were able to specifically expand the scope of the components and the functionalities. At the end of 2021, we were able to successfully complete our project with more than 40 components instead of the originally planned approx. 20 and have moved into the maturity phase.
We now knew that the technology was powerful and concentrated on supplying the projects in the best possible way. Surprisingly, the number of components has hardly changed. Rather, we massively expanded the functionality of the existing components and improved their flexibility. Also, the idea of the possibilities of reusing semantically accessible base components led us to a modular and decoupled architecture. Finally, we also moved away from token-based theming because it does not offer completely free stylability. Using the component styling approach, we have developed the theme designer and will further simplify and improve the creation and maintenance of themes.
Open source approval
KoliBri was approved for open source development by the ITZBund to be accessible to all and to be continuously improved and extended from the feedback of the community.
KoliBri offers optimal reusability for this because it is …
- small - small-scale components,
- fast - automated DevOps pipelines,
- nimble - framework-agnostic and
- colorful - decoupled theming.
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 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.
Today we can serve almost all web-based realization projects with the KoliBri components. We want to further strengthen this field and expand the community.
For the future, we are taking on even more exciting challenges to further expand the reuse benefits of KoliBri.
We want the KoliBri components to be pre-rendered server-side, so that they can be used in any CMS system SEO optimized.
We want to develop the Theme Designer into a real tool that lets the user reuse existing patterns immediately during styling and helps prevent accessibility mistakes in their own design.