Accessibility
What this site does to stay usable with a keyboard, a screen reader, a magnifier or no JavaScript at all — and, just as importantly, what we have not tested.
We would rather tell you exactly what is built and what is unproven than claim a conformance level nobody here has measured. Everything below is either something you can check yourself on this page, or something a mechanical check enforces before a release can ship.
What is built in
- Skip to content. The first thing a keyboard reaches on every page is a link that jumps past the navigation.
- A visible focus ring. Links, buttons and every form field show a clear outline when reached by keyboard.
- It works without JavaScript. Navigation, tutorial listings and learning paths all ship a plain HTML fallback, so the site is readable with scripting switched off or unavailable.
- Text scales with your browser. Font sizes are set in relative units, so raising the browser or system text size enlarges the page instead of clipping it.
- Real landmarks and headings. Every page uses a single
mainregion, a realnavcontaining plain text links, and headings that descend in order without skipping a level. - A breadcrumb trail on every page below the top level, both on screen and in the machine-readable data.
- No motion traps. Nothing auto-plays, nothing moves on a timer, and there is no carousel to outrun.
What a machine checks before every release
These are not intentions. They are automated checks, and a release that fails one of them does not ship:
- No heading level is ever skipped on any page.
- Every visible form control has a label a screen reader can announce.
- Every internal link resolves to a page that exists.
- Every page carries a title, a description and a language attribute.
The checks are also tested against deliberately broken pages, so we know they still catch what they claim to catch rather than passing in silence.
What we have not tested
This is the part most accessibility statements leave out.
- No formal conformance audit. We do not claim a WCAG conformance level, because no independent audit has been carried out. Individual criteria are enforced, as listed above; the whole standard has not been assessed.
- No screen-reader testing. The markup is structured for assistive technology, but it has not been walked through with a real screen reader on real hardware.
- Colour contrast is not systematically verified. The palette was designed for legibility, not measured against a ratio on every component.
- Code samples are wide. Tutorials contain terminal output and code that may scroll sideways on a narrow screen or at a high zoom level.
Found a barrier? Tell us
If any part of this site is difficult or impossible for you to use, we want to hear about it — including which page, and what you were using to read it. A specific report is worth more to us than any audit.
contact@finkatana.com