KeevaathTech

KeevaathTech/Colophon

Colophon

How this site is built, and how to check

We sell assessment work, and we publish an essay arguing that a report about a system is worth less than the system itself. It would be inconsistent to then ask you to take our own standards on trust.

What a first visit costs you

Five requests

One document, one stylesheet, two font files, one script. Nothing else loads before you agree to it.

No third party origin

Fonts are served from this domain. No Google Fonts, no content delivery network, no tag manager, no embedded widgets.

One image on the whole site

A photograph on the about page. All sixteen diagrams are drawn in the document itself, so none of them costs a request.

Median page, twelve kilobytes

The home page is the heavy one at a hundred and seven, because it carries the animated sequence.

Check it yourself: open developer tools, choose the network tab, and reload. Count the rows and read the total.

What we do not do

Nothing measures you before you say yes

Analytics and session recording are not present in the markup of any page. They are injected only after consent, which is asked in two separate parts, because recording what you type is a different question from counting page views. Decline and no request is made to either service at all.

No cookies are set on arrival

The only thing stored before you choose is nothing. After you choose, one entry records the choice so you are not asked again.

No accessibility overlay

We sell accessibility audits, and the widgets that promise conformance from one line of script do not deliver it. Installing one here would contradict what we would tell a client.

No dark patterns in the consent panel

Decline is a button of equal weight, not a link hidden under a paragraph. Choosing costs you the same as accepting.

How it is built

Static, on the edge

Every page is a file in its own directory. Nothing is rewritten in flight, so no request is ever redirected on its way to a page.

Typefaces

Newsreader for display, DM Sans for text, JetBrains Mono for labels and data. Six Latin subset faces, self hosted, cached for a year.

No framework

No React, no build step, no hydration. The markup you receive is the markup that renders.

Forms

One edge function. Submissions are emailed and nothing is stored. If sending fails the form says so and gives you an address, instead of showing a confirmation that is not true.

Motion

Only compositor properties are animated, and every looping animation pauses when its section leaves the screen. A reduced motion preference removes all of it.

Structured data

Sixty four blocks across thirty four pages, describing the organization, the services, and the questions each page answers.

Accessibility

The target is WCAG 2.2 Level AA. Every page has one first level heading and no skipped levels, every control has a label, every diagram carries a title and a description, contrast is at or above 4.5 to 1 in both themes, and nothing is set below eleven pixels.

What we will not do is claim conformance. There is no certification body for WCAG, testing here is not complete across assistive technology combinations, and a claim we have not finished earning is worth less than an honest statement of position. The accessibility statement says where we actually are and how to report a barrier.

Where this site falls short

The home page is heavier than we would like

A hundred and seven kilobytes, because the opening sequence is one continuous animation instead of a static image. We think it earns its weight. If you disagree, that is a reasonable position, and it is the trade we made.

Two product marks are reconstructions

The Gulf Careers Academy and MaatraCare logos here were rebuilt from small raster images while the originals are prepared. They are close and they are not exact.

One published article

The Build Log is monthly and it started recently. A record of one piece is not a publishing record, and we would rather say so than imply otherwise.

How to check any of this

  1. Count the requests

    Developer tools, network tab, reload. Five rows on a cold load, and no origin other than this one.

  2. Test the consent gate

    Open a private window, decline, and watch the network tab. Nothing goes to Google or Microsoft. Accept, reload, and both appear.

  3. Operate it by keyboard

    Tab through any page. Focus is visible at every step, the skip link comes first, and every journey completes without a mouse.

  4. Turn off styling

    Disable CSS and read a page. The heading order and the reading order should still make sense, because the markup carries the structure.

  5. Run it through a tool

    Lighthouse, WAVE, axe, whichever you prefer. If you find something we have missed, we would like to know.

Questions we are asked

Why publish this at all?

Because we sell assessments, and a firm that assesses other people's work should be willing to have its own read. It is also the cheapest way to demonstrate a standard: anyone can check every claim here in about two minutes.

Do you build client sites this way?

The principles carry over and the specifics do not always. A client with an existing content platform, a marketing team that needs a page builder, or an analytics obligation will land somewhere different. We tell you what each choice costs and you decide.

What would you change if you rebuilt it today?

The home page weight, by loading the opening sequence after first paint instead of with it. It is on the list and it is not urgent.

Found something wrong?

Tell us. Corrections to this page are the ones we act on fastest, and we will say what changed.

Found something we missed?

Corrections to this page are the ones we act on fastest, and we will say what changed. That offer is the point of publishing it.

Related