Skip to content
GullySales

Disability support NGOs · Website

Build a site that the people you serve can read, hear and use.

A website for a disability support NGO is the first place a family, an employer or a funder judges the centre, and it must be usable by people with disabilities. GullySales builds and tests pages for screen readers, keyboard use and low-end phones.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of ngos at work in India

What website means

A website is the page a customer lands on after searching, clicking an advert or scanning a code, and it decides whether they call or leave. GullySales builds and maintains sites that load quickly, explain the offer plainly and make the enquiry form or phone number easy to find.

Last updated 18 Oct 2026.

For disability support NGOs

Where it usually goes wrong, and what we would do.

  • “An inaccessible site contradicts the mission”

    A centre that supports people with disabilities, but whose site a screen reader cannot read or whose video has no captions, tells visitors something unfortunate about itself before they arrive.

  • “The first screen must answer a worried parent”

    A family wants to see what the centre does, where it is, how to reach someone and what happens first. A long story about the founder, placed ahead of this, loses the visitor.

  • “Language and reading level matter”

    Some visitors read in a local language or find long sentences tiring. Short sentences, plain words and a language switch at the top serve more families than a polished English page.

  • “Donation and contact pages carry legal weight”

    A page that takes donations or lists registrations must be accurate. Rules differ by state and by the type of body, so the wording must be checked with your own adviser before it goes live.

What we do

What we deliver for disability support NGOs.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. An accessibility-first design

    Page structure, contrast, text size and focus order built for screen readers and keyboard use from the start.

    Result: People who use assistive technology can move through each page.

  2. A tested build

    Checks with a screen reader, keyboard-only use and a basic phone before launch.

    Result: Problems are found by testing, not by a visitor.

  3. Programme and contact pages

    One page per programme and a contact page with phone, WhatsApp, address and timings.

    Result: A family finds the next step on the first screen.

  4. A language switch

    Key pages in the languages your families speak, with a visible switch.

    Result: Visitors read in the language they know best.

  5. A feedback route for access problems

    A visible way for anyone to report a page they could not use, with a named person to respond.

    Result: Barriers reported by visitors reach someone who can fix them.

How the result is measured

  • Page load time
  • Bounce rate
  • Enquiries from the website

Recorded as a baseline before work starts, so every later report has an honest comparison.

Searches your buyers type

What a visitor searches and the page on the website that answers each.

what does [centre name] do
The home page, saying in plain words who the centre serves, where it is and how to ring. A large phone number sits on the first screen.
[centre name] admission process
An admission page with steps, papers and what happens at a first visit. Says when the centre cannot take a person and where else to ask.
how to reach [centre name] by bus
A getting-here page with entrance, step-free route and landmarks in the local language. Answers the grandparent who brings the child.
employ a person with disability [city]
An employer page with the placement steps, the adjustments commonly made and a named officer. Kept apart from the family pages.
[centre name] donate
A donation page that explains what a gift supports, with accurate legal and payment details as the centre holds them. Contains no figures it cannot prove.

Who it is for

This is written for these disability support NGOs.

  • Early intervention and therapy centres for children
  • Special schools and learning support centres
  • Vocational training and sheltered workshops
  • Inclusive employment and placement organisations
  • Assistive device and prosthetic fitting charities
  • Organisations for the blind, deaf and hard of hearing
  • Autism, cerebral palsy and intellectual disability associations
  • Rehabilitation and community-based support programmes

Not for

It is not the right fit if.

  • The centre cannot yet keep the site updated, so timings, camps and contacts would drift away from the truth
  • No one can test the pages with a screen reader or a keyboard, and the site would exclude people the centre serves

Before you decide

Agree the work. Know how to judge it.

Website for disability support NGOs: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the pages that support a buying decision and the actions visitors must complete. Keep examples of failed forms, unclear product information, and questions your team answers repeatedly.

Make the scope clear

Agree the page list, content ownership, integrations, and who controls the domain and hosting. Include redirects and existing search traffic in a redesign brief, before changing addresses.

Check the work in use

Complete a real enquiry journey on a phone and a laptop. Check that the confirmation appears, the enquiry reaches the right person, and tracking records the action once.

Know when to change course

If visitors can enquire but the team does not follow up, start with the sales handover. A larger website will not resolve that delay.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

How it works

How the website work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Build scope agreement

    Your requirements brief comes first, followed by a conversation. We agree the build scope, fee, and term in writing before work starts.

  2. 2

    Access and content confirmation

    We check available content, domain access, and hosting arrangements. You confirm missing material and whether preserving an existing site’s search standing requires a redesign scope.

  3. 3

    Sitemap and design approval

    You approve the page list, platform, and content responsibilities. Phone and desktop designs then go to you for approval before development.

  4. 4

    Test-site content approval

    The approved designs become working pages with real content. You review business details on the test site and approve the content before launch checks.

  5. 5

    Launch approval

    You approve the finished pages and launch checklist before the site goes live. Where an old site exists, its addresses are mapped to destinations you approve as part of this decision.

  6. 6

    Live checks and access handover

    After launch, we test the live enquiry routes and tracking, complete agreed corrections, and hand over documented account access and source files for your acceptance. Further improvements are distinguished from build corrections and scoped separately.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Can a site be fully accessible?
No site is perfect, and standards develop. We build and test against common practice, and we give people a phone and WhatsApp route as well. We also listen to what users report and fix what they find.
What must the site say about registration and donations?
Only what is true and has been checked by your own adviser. Rules differ by state and by the kind of organisation. We do not state any registration or tax status on your behalf, so the centre supplies and confirms that wording.
Should the site have a large-text and a high-contrast option?
Build the pages so they read well at larger sizes and with strong contrast by default, and respect the visitor's own device settings. A switch on the page helps some visitors. Test with a screen reader and a keyboard, and ask a user who relies on them.
What should the donation page say about legal status?
State only the facts the centre can document and has checked with its own adviser, in the form the rules require. Do not imply any status the centre has not confirmed. Rules differ by organisation and state, so ask your own auditor or lawyer to read the page before it goes live.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.
What if we are not happy with the work?
Tell us and the plan changes. Everything is reported against the baseline, so a number that is not moving is visible to both sides. The term is in your written scope, and the refund and cancellation policy sets out the rest.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.