Accessibility statement

For sigelith.org. Last reviewed: 24 September 2026.

1. What we aim for

We want Sigelith to be usable with a keyboard alone, with a screen reader, at high zoom and on a small screen. Our target is WCAG 2.2, level AA. We do not target level AAA: some AAA criteria would require a second, simplified version of technical pages in eleven languages, and the W3C itself advises against AAA as a blanket policy for whole sites.

This statement is voluntary. Sigelith is run by a micro-enterprise, which the German Barrierefreiheitsstärkungsgesetz exempts. We publish it anyway, because a service that asks you to verify things for yourself should be usable by everyone who wants to.

2. Conformance status

sigelith.org conforms to WCAG 2.2, level AA, with one exception named in section 3: the API reference at /docs/, which is built on third-party components.

Every check we run against the delivered pages passes on all 23 public pages. These checks cover the document language and the language of parts, heading structure, alternative text, form labels, link and button names, duplicate identifiers and autocomplete hints. They run as part of our automated test suite, so a regression fails the build rather than reaching you. On top of that, the site was reviewed by hand: at 320 pixels width and at 200% zoom (no content lost, no sideways scrolling), by keyboard alone through sealing a capsule and stamping a file (every control reachable, focus always visible, no trap), and with a screen reader.

Measured colour contrast (WCAG asks for 4.5:1 for body text and 3:1 for controls). The site follows your system setting and has a light and a dark theme; both are measured:

Colours measured on 27 September 2026, when the light and dark themes were introduced. The lowest value of each row is shown: text on a card, not on the page background; the clock digits are measured on the tinted background around the clock.

Also verified in the source: no fixed pixel widths that would force horizontal scrolling, long strings such as hashes and crypto addresses wrap, every clickable element is a real button or link (so the keyboard reaches it), nothing is revealed by hovering alone, the focus indicator is two pixels in an accent of at least 6.3:1, and the sticky header no longer hides the element the keyboard has just moved to.

3. Known limitations

• API reference — outside the conformance claim. /docs/ and its ReDoc variant are built on third-party components. We host them ourselves and removed their external fonts and trackers, but their internal markup is not ours to fix, so we do not claim AA for those two pages. Everything they document is also available as a machine-readable schema at /api/schema/, and we will answer API questions by e-mail.
• Wide tables — a few reference tables scroll sideways on a narrow screen. WCAG permits this for tables; the data does not fit a phone in one column without losing the comparison it exists for.
• The clock keeps moving — the @beat reading updates continuously and cannot be paused. That is the purpose of the page, so it falls under the “essential” exception. Every value the clock shows is also available as text in the page and through the API.
• Our apps — the Android app and the Wear OS watch face have not been assessed against WCAG and are not covered by this statement.

4. Found a barrier? Tell us

If something on this site is unusable for you, please write to kontakt@advena-partners.com. Tell us the page and what happened; if you use assistive technology, naming it helps us reproduce the problem. We aim to reply within 14 days and to say plainly whether and when we can fix it.

If you need information from this site in another form — for example a page read out, or data from a table sent as plain text — ask and we will send it.

5. How this was assessed

Self-assessment, no external audit. The automated part uses a checker written for this site, which reads the finished HTML of every public page and runs with our test suite, so a regression stops a release instead of reaching you. Contrast values were computed from the site's own colour tokens using the WCAG relative-luminance formula. The remaining criteria were reviewed by reading the stylesheets and templates, and then in the browser: narrow viewport, 200% zoom, keyboard-only navigation and a screen-reader pass.

Operator of this website:

← back to Sigelith