Everything you would have to ask us for.

The kind of work

Small portals and internal systems. Tidying data and moving it out of one thing into another. Forms that feed a record rather than an inbox. Case management for a team that is currently doing it in a shared spreadsheet. Making two systems that do not talk to each other exchange what they need to. Reporting that is produced rather than assembled.

We read education notices on the same two feeds as everything else. A college or a university buying one of the things above is the same job, and we would be glad to quote for it.

Fixed scope, fixed price

We write down what we are going to build, what it will cost and when it will be done, and you have that in writing before anything starts. If the scope changes, we quote the change before we do it. We would rather turn a job down than start one where nobody has agreed what finished means.

You talk to the person doing the work

There is no account manager between you and the code. The person who scopes the job is the person who writes it and the person who fixes it afterwards.

Your data, and who owns the code

Your data is yours, and getting all of it back out in an open format is a function in the software rather than a favour you have to ask for. Who owns the copyright in the code is a separate question and a contractual one: we will put the answer in writing before you sign, and we are content for it to be you.

What happens if we are not here

A fair question to ask a one-person company, and one we would rather you asked at the start. Everything we build runs on ordinary, widely used parts — a PostgreSQL database, a standard web framework, a mainstream host — and the source code and the database can be handed to you or to another supplier at any point. Nothing we build needs us specifically in order to keep running.

On a build, we are normally your processor: the data belongs to your organisation and we handle it on your instructions and nobody else’s. That gets written into the contract before any of it reaches us.

• Where your data is held is agreed in writing before any of it reaches us, and we will keep it in the United Kingdom or the European Economic Area unless you have asked for something else. It is a term of the contract, not a property of our servers — so ask us to write it down, and we will.
• We take the smallest amount of real data we can work with. For testing we would rather have made-up data than a copy of yours, and we will ask for that first.
• Access is by named account, and we can show you who has one.
• If something goes wrong we tell you promptly and in plain words, including when we do not yet know the full extent of it.
• At the end, you get everything back in an open format and we delete our copies.

What this website itself does with the details you type into it is set out in our privacy notice.

We aim to meet the Web Content Accessibility Guidelines version 2.2 at level AA. We believe this site does, with the exceptions listed at the bottom.

What we checked, and how

• Colour. Every text colour on the site measured against what is actually painted behind it. The lowest is 5.1 to 1, where AA asks for 4.5 to 1 for normal text. The edge of every field and button was measured too: the lowest is 3.6 to 1, where AA asks for 3.
• Keyboard. The site used with the keyboard alone, with no mouse. Everything that can be operated can be reached in order, nothing traps the focus, and the thing you are on is always visibly outlined.
• Forms. Every field has a label joined to it in the markup rather than placed near it, and an error is announced when it appears rather than only shown.
• Structure. Headings run in order without skipping a level, so moving through a page by heading works.
• Size. Text enlarged to twice its size, on screens 1280, 390 and 320 pixels wide, with nothing lost and no sideways scrolling in any of the nine combinations. That check found a real fault and it is fixed: at twice the size on a phone the header, one button and an email address were each being pushed off the side of the screen, where the page then quietly clipped them. Every button and every field is at least 24 pixels in its smaller direction; a link inside a sentence follows the line it sits in, which is what the guideline allows, and the links in the footer are 33 pixels apart, which is more than the 24 it asks for.
• Motion. There is one animation on the site — the drawing on the front page arriving — and it does not play at all for anyone whose device asks for less motion.
• Every publish. The site cannot be published with an unlabelled control, an id used twice, a label pointing at nothing, a heading that skips, or a link that goes nowhere. That is a check that runs before the site goes out, not a thing we remember to do.

Known gaps

• This site has not been tested by disabled people, and it has not had an independent audit. Our checks are our own.
• The pages behind a subscription — managing your billing, setting a password, the installation guide — are older than the rest of the site and have not been through the same check.

If something does not work for you

Email help@doparagroup.com or call 07931 904678. Tell us the page and what happened, and we will fix it and tell you when it is done. If you are not satisfied with our answer you can contact the Equality Advisory and Support Service.