Score Foundation.Website Revamp

About the organization

Score Foundation↗ (opens in a new tab) is a nonprofit established in 2002 in New Delhi. Its mission is to bridge the information and opportunity gap between blind or visually impaired people and the wider society. Its work includes peer-led counselling, information dissemination, community engagement, advocacy, capacity building and skills-related support.

The flagship Project Eyeway↗ (opens in a new tab) operates a national helpdesk (8800004334) staffed by trained counsellors with lived experience of visual impairment. Its published areas of guidance include education, employment, government schemes, assistive technology, independent living and daily challenges. The Foundation's work also spans media programming, outreach, partnerships and public policy engagement.

George Abraham↗ (opens in a new tab) is listed on the site as Founder and Chief Executive Officer. The organization describes his earlier role in developing blind cricket in India and founding Score Foundation to challenge societal attitudes that restrict inclusion. These are the client's existing history and achievements, not accomplishments of the website revamp.

Business and operational context

The site has to communicate with audiences whose needs differ substantially:

• Blind and visually impaired individuals: reach relevant information, counselling, support and the Eyeway helpdesk.
• Families and caregivers: understand programs and identify a practical first contact.
• Educators, employers and institutions: understand inclusion-focused training, accessibility, advocacy and partnership opportunities.
• Potential funders and CSR stakeholders: understand the organization's history, program model, partners, governance documents and ways to support it.
• Volunteers and job applicants: find involvement and career entry points.
• Journalists, researchers and the public: explore the founder story, reports, media and outreach evidence.

The Foundation's public LinkedIn presence and website place it in the nonprofit sector, headquartered in New Delhi. The context is national service delivery, not a locally constrained consumer-business website.

Why this digital experience matters

The primary value of an institutional nonprofit website is orientation and access, not simply aesthetic presentation. Visitors need to understand whom the organization serves, why it exists, which services match their situation, whether it is credible, and how to act. An effective site must place the Eyeway contact route close to the mission while making the larger ecosystem—programs, partnerships, personnel and reporting—discoverable.

This is an interpretation of the delivered site's structure, not a quotation from an unpublished client brief or proof of specific historical conversion problems.

Verified starting context

Score Foundation predates this website revamp by more than two decades, and its programs, media work, founder history, partnerships and published reports also predate the engagement. The Foundation already had a public web presence and an established flagship program. The project owner explicitly characterized this engagement as a website revamp, followed by ongoing maintenance and SEO work.

No verified pre-revamp screenshot set, information architecture, CMS inventory, site-speed baseline or migration brief was available for this curation. Accordingly, the case study does not claim that particular pages, capabilities or accessibility features were absent before the project.

The information challenges reflected in the finished website

• Several distinct audiences: beneficiaries seeking help, funders assessing credibility, volunteers, employers and advocates need different entry points.
• Service complexity: counselling, information, community engagement, advocacy, capacity building and training each require clear descriptions and context.
• Prominence of a critical help channel: a national helpdesk number must be easy to locate from the public website.
• Institutional trust: the founder, team, historical milestones, annual reports, financial statements and partner ecosystem need accessible public presentation.
• Long-lived content: staff profiles, opportunities, contact details, funder information and reports require continued editorial maintenance.
• Accessibility stakes: because people with visual impairment are core users, usability for screen-reader, keyboard and other assistive-technology users is a crucial quality requirement; no formal conformance test is presumed completed.

Constraints and realities observable from the project

• Mission alignment: clear, respectful language focused on participation, dignity and support rather than pity-led framing.
• Multiple content families: structured program descriptions, founder biography, staff profiles, archive reports, photos and contact data.
• High-stakes contact information: mistakes in helpline, address or donation/support information can obstruct help and erode trust.
• Ongoing updates: recruiting, partnerships, reports, program pages and SEO require upkeep after the initial revamp.
• Unknown commercial/internal constraints: budgets, vendor selection, actual deployment process, inherited platform and staff ownership are not documented.

Primary objective

Present Score Foundation as a coherent, credible, findable institutional destination while helping different audiences reach relevant information, services and support pathways.

Secondary objectives inferred from the delivered experience

• Keep the Eyeway helpline and support route discoverable.
• Explain the nonprofit's service areas in enough detail for visitors to identify a relevant program.
• Preserve founder and organizational history in clear, dedicated pages.
• Make annual reports and financial statements available as credibility and governance resources.
• Give prospective partners, supporters, volunteers and applicants identifiable next steps.
• Support the site's long-term discoverability and currency through the ongoing SEO/maintenance relationship described by the project owner.

Observable acceptance evidence

Interpretation: "Present" describes visible site content or a link, not a formal quality or conversion test.

Core visitor journeys

Structuring decisions reflected in the output

1. Mission before mechanics: the home page foregrounds empowerment, information access and the nonprofit's position as a connector.
2. Give Eyeway a dedicated destination: the flagship initiative has its own explanation, service categories and national helpline.
3. Separate the institutional story from services: background, founder, team and program pages address distinct questions.
4. Make evidence navigable: published reports, financial statements, partners and gallery content live in identifiable sections.
5. Offer several participation routes: support, partnership, careers, volunteering and contact actions serve different visitor intents.

These are observed choices in the final site, not documented alternatives or decision records from the original project team.

Public-facing pages and capabilities verified

Website content shown with useful prominence

• Eyeway National Helpdesk: 8800004334 is displayed prominently on the home and initiative pages.
• WhatsApp broadcast: the homepage offers a community-update subscription route and displays a contact number. This is an outbound engagement link, not evidence that any user subscribed.
• Service taxonomy: the homepage enumerates six service categories: Counselling, Information Dissemination, Community Engagement, Advocacy, Capacity Building and Training.
• Founder and peer-led model: the website connects the organizational mission to George Abraham's history and the experience of counsellors who are themselves visually impaired.
• Credibility material: an organizational timeline, partner list, staff biographies, reports and galleries support visitors seeking evidence of past activity.

Scope boundaries

This review does not establish that the developer created every item of editorial content, authored reports, took photographs, designed the brand, developed the Eyeway helpdesk itself, implemented a payment processor, built a content-management backend, or produced the Foundation's real-world impact. The site is the deliverable; the nonprofit's service operations are a separate activity.

Role and engagement

The project owner has stated that they delivered the Score Foundation website revamp and have an ongoing contract for website maintenance and SEO work. This is reliable first-party engagement context for the case study, but it does not disclose a task-by-task contribution record or the work of any other collaborators.

Contribution that may be accurately claimed

Attribution boundaries

George Abraham and Score Foundation are the clients and owners of the organizational work, services, staff biographies, achievements, and published institutional material. The project owner's credited contribution is to the website revamp and continuing technical/SEO engagement, not the Foundation's program achievements.

Solution overview

The delivered experience organizes a mature nonprofit around a clear set of visitor questions: What is the mission? What help is available? Who is behind the work? What has the organization achieved? How can I participate? The homepage communicates the purpose of the organization, introduces Eyeway, gives direct entry to the service areas, and presents calls to action for beneficiaries and partners. Deeper pages give context for specific programs and document the organization’s experience.

Main experience: someone seeking help

1. Land on the homepage and understand Score Foundation's mission and reach.
2. Follow Get Help or Project Eyeway to read about the national helpdesk.
3. Identify topics such as education, employment, life skills or government schemes.
4. Use the published 8800004334 number for direct assistance. A successful phone connection was not independently tested.

Main experience: potential partner or supporter

1. Review the organization’s mission, history and founder story.
2. Explore service verticals, partner categories and evidence of operational history.
3. Consult annual-report and financial-statement archive pages when evaluating institutional credibility.
4. Follow Partnerships, Support Us or Contact Us to pursue next steps. Payment or enquiry completions were not tested.

Main experience: applicant, volunteer or researcher

1. Use the site's navigation for Careers, Volunteering, Media Reports, Outreach or Gallery.
2. Read the available role details, public materials or activity records.
3. Follow the relevant link or published contact details for further action.

Why the solution fits

The value is the combination of clear service navigation, prominent human support, organizational credibility and continuing discoverability. A help-led nonprofit needs practical contact pathways as much as polished storytelling. Using dedicated pages for programs and reporting also gives maintenance and SEO work discrete content destinations instead of placing everything on a single undifferentiated page.

Before → after, without invented historical facts

This table describes context → current delivery, not measured differences between archived screenshots or versions of the software.

What can be confirmed externally

• The website is served from the custom domain https://scorefoundation.org.in/↗ (opens in a new tab).
• The public navigation exposes distinct page URLs for the homepage, organizational information, Eyeway and major service areas.
• Public reports, program information and images are represented through dedicated content pages.
• The homepage's indexed markup exposes Skip to main content and Skip to sidebar navigation links and descriptive text labels for a range of images.
• The site links externally to communication mechanisms such as a telephone number and WhatsApp community route.

What cannot be responsibly inferred

The live public text does not identify the original repository, framework, CMS, database, hosting vendor, deployment pipeline, email backend, form-processing implementation, analytics setup, caching configuration or server security controls. These are intentionally omitted from any claimed technology stack.

Accessibility-specific observation

Because the audience includes blind and visually impaired users, accessibility is a core product requirement, not an optional visual enhancement. The text representation of the homepage shows two skip links, and several image descriptions are exposed on the homepage and gallery. These are useful observable affordances, but they do not establish WCAG 2.2 A/AA conformance or verify screen-reader functionality, focus management, keyboard navigation, contrast, responsive reflow or form usability. Those claims require dedicated testing.

Security, privacy and operations

The available sources do not support claims about penetration tests, compliance certifications, backups, hosting SLAs, secret storage, authentication, donor-payment security, security monitoring or rollback practices. The project owner reports continued maintenance and SEO support, but no underlying operations runbook or monitoring data was supplied.

Known engagement milestones

Delivery metrics

Important: The two archive counts describe indexed website content. They are not development productivity, accessibility, or business-outcome KPIs.

Directly observable delivery outcomes

1. One cohesive public institutional destination. The Foundation's mission, history, founder, team, initiative, service descriptions and involvement routes are presented under its domain.
2. A prominent route to existing beneficiary support. The Eyeway helpdesk is explicitly named and its phone number is easy to discover from the homepage and initiative page.
3. Publicly explorable program structure. Visitors can navigate from a six-category homepage service overview to dedicated service content.
4. Discoverable institutional evidence. The site presents partners, gallery material, annual-report summaries and financial-statement summaries.
5. Continuity after launch. The project owner reports an ongoing maintenance and SEO engagement beyond the initial revamp.

Non-site organizational achievements: context, not project results

The website reports long-established nonprofit activities, such as annual helpdesk interactions, partnerships, media programming, training and advocacy. In particular, its annual-report archive cites 8,471 helpdesk calls for 2021–22, 11,166 queries for 2022–23, and 9,659 queries for 2023–24. Those numbers refer to Score Foundation's existing program operations during those fiscal periods, not traffic, enquiries, donations or uplift caused by this website project.

The homepage's India-wide prevalence statistics are also third-party sector-context figures as presented by the organization, not outcomes of the engagement. They have not been independently audited for this case study.

Outcomes that must not be overstated

Qualitative impact statement

The finished website makes the organization's program structure and public credentials available through clearer, purpose-specific destinations. That is a genuine capability and presentation outcome. Whether the experience has changed real visitor behavior, reduced support friction or increased engagement remains an open measurement question.

Evidence standard: Public website material proves the current site's contents. The project owner's statement establishes the reported engagement. Neither proves quantified uplift or details of the development workflow.

What the website illustrates well

• Mission-first structure: viewers immediately encounter the purpose of the organization before dense program detail.
• Human support visibility: the Eyeway helpdesk is presented as a practical route to help, not buried under institutional history.
• Audience-specific browsing: different visitors can follow dedicated program, reporting and participation paths.
• Credibility through public evidence: founder history, staff profiles, reporting archives and partnerships support institutional evaluation.
• Durable content destinations: the service pages, reports and public profiles provide natural targets for ongoing content and search maintenance.

Areas worth reviewing during ongoing maintenance

1. Contact address consistency. Several pages show 17/107, Vikram Vihar, Lajpat Nagar IV, while the Eyeway↗ (opens in a new tab) and Careers↗ (opens in a new tab) pages display 4, Vikram Vihar Extension, Lajpat Nagar-4. Confirm whether these are separate valid offices or stale variants before harmonizing; do not assume either address is wrong.
2. Service taxonomy clarity. The About↗ (opens in a new tab) page explains five pillars, while the homepage lists six service verticals, with Training separately listed. Both can be accurate, but the relationship should be explained so readers do not assume an editorial inconsistency.
3. Accessibility verification. Run a documented keyboard- and screen-reader-led audit with representative users, covering the navigation, headings, visual media, downloads and action paths. Existing skip links are a positive signal, not evidence of full conformance.
4. Report recency. Ensure public annual-report and financial archive pages are updated whenever newly approved documents become available; do not publish unapproved statements or infer missing fiscal-year records.
5. Content quality and citation checks. Review source dates and wording for high-impact national statistics, organizational claims and partner lists.
6. Search and structured information. Establish a reproducible SEO baseline, page-by-page metadata checks, sitemap/indexing review, and suitable organization/report structured-data validation where supported by the implementation.
7. Enquiry-path verification. Confirm the destination and operation of Support Us, Contact Us, volunteering and career links, including keyboard access and accessible validation if forms exist.

These are recommended next checks, not reported failures or commitments the developer claims already to have completed.

Generalizable insight

For an established nonprofit, a website revamp is primarily an information-access and trust-architecture problem. A compelling mission statement matters, but its practical value depends on the visitor being able to find the right program, help channel, evidence or contact route. Continuing maintenance and search work are part of preserving that utility over time.

What this project can responsibly demonstrate

Delivery of a live, content-rich institutional website and an ongoing client relationship covering maintenance and SEO. Without internal work records, it should not be marketed as proof of a particular frontend stack, audited accessibility rating, quantified SEO uplift or measured fundraising success.

Ongoing service

The project owner reports an active website maintenance and SEO engagement with Score Foundation following the revamp. Contract price, renewal terms, SLA, cadence, assigned team and next review date are intentionally not supplied because the agreement was not attached.