Public sector.

I design and code sites for public institutions that comply with WCAG 2.2 AA. Accessibility goes in at the design stage, not as a patch at the end - and your own staff manage the content, with no external invoice for every announcement.

Diagnosis

An institution's website that breaks the law and puts residents off.

The three problems that cost a public institution the most - and none of them can simply be waited out.

A law you cannot work around

Polish law obliges public institutions to provide digital accessibility at level AA. A site that fails to meet it is not a matter of taste - it is a breach of the regulations and a real risk of a complaint.

A look from a decade ago

Residents judge an institution by what they see in the first few seconds. A site that looks like 2010 undermines trust before anyone reads a single announcement.

Every change through an outside firm

An employee wants to post a notice or update the opening hours - and waits days for the contractor. Where information has to be current, that is an operational problem, not a detail.

Process

How an institution's site gets built.

A clear course, firm deadlines and documentation at every step - including the documentation the procurement process needs.

Requirements analysis

We establish the scope, the procurement route and the accessibility requirements. You get a concrete offer and a schedule before you sign anything.

Design with accessibility

I design the site screen by screen, and WCAG 2.2 AA enters right here - contrast, structure, focus order. Not as a patch at the end.

Code and panel

I write the site from zero in Next.js and set up Payload CMS with permissions for individual members of staff. No off-the-shelf themes.

Checks and training

Before handover I go through the site point by point: keyboard navigation, screen reader, contrast and content structure. Then I train the team on the panel, and the code goes to the institution whenever it asks for it.

What you get

A site that meets the law and serves the resident.

Accessibility checked before handover, private-sector design quality and independence from an outside supplier.

WCAG 2.2 AA compliance

I build to the latest version of the standard, which contains the whole of WCAG 2.1 AA: keyboard navigation, screen readers, contrast, alternative text and a legible content structure.

A design without the municipal template

A look matched to the character of the institution, approved screen by screen. None of the generic themes that give an official website away from a mile off.

Your staff run the content

Payload CMS lets them add a notice, a news item or a document without a developer. The change history shows who corrected what, and when.

Permissions shaped to your structure

The secretariat edits the news, HR posts the job adverts, the administrator has everything. Everyone sees exactly what belongs to them.

Comparison

A typical municipal site, or a site from me.

The same institution, two completely different experiences for the resident - and two different levels of legal risk.

A typical municipal site

A site from me

Accessibility bolted on at the end, if at all

WCAG 2.2 AA from the design stage, checked before handover

A template recognisable from a mile off

A design shaped to the institution

Every content change is a ticket and an invoice

Your staff run the content themselves

A multi-year service contract

The code belongs to the institution, no lock-in

A heavy site that takes an age to load

Next.js - the site carries only the code it needs

Pricing

A quote shaped to the procurement route.

In a public institution the scope follows the requirements and the procurement procedure, so I price it individually. You get a concrete offer with a scope and a date - ready for the procedure.

Institutional website

Design, code in Next.js, a CMS panel with permissions and a WCAG 2.2 AA check before handover.

On request

Accessibility audit of an existing site

A check against WCAG 2.2 AA and a report listing the concrete fixes to implement.

On request

Maintenance and hosting (SLA)

Server, backups, monitoring and security updates with a guaranteed response time.

fromPLN 300

monthly
Ask for a quote

FAQ

Before you ask.

Accessibility, code ownership, deadlines and editing the content yourself.

Yes - for public institutions I build to WCAG 2.2 AA, the newest version of the standard, which contains the whole of the WCAG 2.1 AA that the law requires. Accessibility goes in at the design stage, not as a patch at the end: semantic code, keyboard navigation, contrast and screen-reader testing. I will say plainly that I have not yet delivered a project for a public institution, so instead of promising the outcome of an official audit, I show you the method and check the site point by point before handover. Worth remembering, too, that accessibility also depends on the content added later, and that side is yours.

Yes. I implement a dedicated admin panel powered by Payload CMS. You assemble pages from ready-made blocks, so adding a page, changing pricing or publishing a post takes no code at all. After launch I walk you through the panel so you know where everything is.

Yes. I build on open technologies (Next.js, Payload CMS) and I do not licence the site to you - the code is your property. Ask for it and I hand it over in full, so you can develop the project with any other developer. Hosting and maintenance, if you order them from me, are a separate service you can cancel at any time.

The timeline depends on architectural complexity. Fast Next.js brochure sites I deliver in 2-3 weeks. Complex B2B platforms, headless stores or WCAG implementations typically take 6 to 10 weeks. You always get a firm schedule before signing the contract.

We work on a contract that sets out the scope, the deadline and the rule that I do not start programming until you have approved the design. Payment comes in two parts: a deposit at the start and the rest once you accept the working site. You do not pay for everything up front, and you never pay for something you have not seen on screen first.

Technically yes, as standard. Next.js renders content on the server, so Google's crawler sees it immediately, without waiting for scripts. I take care of heading structure, structured data, the sitemap and loading speed. One honest caveat: nobody can sell you rankings bundled with a website - the technical side is the foundation, but the result also depends on your content and on what your competitors do.
Taking on new projects

A site that meets the law and makes a good impression.

Write to me and I will prepare an offer matched to your institution's requirements and the applicable procurement route. The first conversation costs nothing.

Ask for a quote