DEV Community

Piyush Sahu
Piyush Sahu

Posted on

“Build something with open-source AI at its core.”

Ability360: Making Opportunities Accessible to Every Student

What I Built

What if a student has the talent to become an engineer, entrepreneur, researcher, or developer — but cannot find opportunities that are actually accessible to them?

That is the problem I wanted to solve with Ability360.

I am building Ability360 as an accessibility and opportunity platform specifically designed for Divyangjan students.

The problem is not that opportunities don't exist.

The problem is that they are scattered across the internet, often difficult to discover, difficult to understand, and rarely designed around the individual accessibility needs of a student.

A student may have the skills.

They may have the ambition.

They may even have the qualifications.

But somewhere between “I want to do this” and “I can actually apply for this”, there are dozens of barriers.

Ability360 is designed to remove some of those barriers.

Instead of asking a student to search through hundreds of websites, Ability360 aims to create one accessible place where they can:

  • Discover scholarships, internships, competitions and jobs
  • Assess their skills
  • Understand possible career paths
  • Build a personalized career roadmap
  • Find mentorship and support
  • Discover opportunities relevant to their skills
  • Access accessibility and Divyangjan-focused resources

The vision is simple:

Your disability should not decide how much of the internet you can access. Your potential should.

The Person Behind the Problem

I didn't want to build another AI project just because AI is trending.

I wanted to build something for students who are often expected to adapt themselves to systems that were never designed with them in mind.

As a student myself, I have seen how difficult it can be to discover the right opportunity even when you have access to the internet, communities, mentors and technology.

Now imagine having to do all of that while also dealing with accessibility barriers.

That made me think:

Why should a student have to fight the platform before they can fight for their dream?

Ability360 started from that question.

Demo

Live Prototype:

https://ability360.lovable.app

The current prototype includes:

  • Accessible student onboarding
  • Skill Assessment
  • Student DNA
  • Career-role exploration
  • Opportunity discovery
  • Personal Career Roadmap
  • Accessibility & Divyangjan Support
  • Mentorship and community concepts

The prototype is designed around the student's journey rather than around a collection of disconnected features.

Understand me → Understand my abilities → Show me possibilities → Help me take the next step.

Code

GitHub:

https://github.com/Piyushsahu99/ability360

The project is being developed with the goal of keeping the platform open and extensible so that developers, colleges and communities can build on it.

How I Built It

The core idea behind Ability360 is to combine accessibility + AI + opportunity discovery.

Instead of treating AI as a chatbot sitting on the side of the application, AI becomes part of the student's journey.

A simplified version of the system looks like this:

Student Profile

↓

Skills + Interests + Goals + Accessibility Needs

↓

AI-powered Understanding

↓

Career & Skill Mapping

↓

Relevant Opportunities

↓

Personalized Roadmap

For example, instead of simply showing a student:

“Here are 100 internships.”

Ability360 should eventually be able to understand:

“These are your current skills, this is the career direction you're interested in, these skills are missing, and these are opportunities you can work toward.”

That changes the experience from searching to guidance.

The platform is being built with a modern web stack, with the AI layer designed around open-weight AI models and open tooling so that the intelligence behind the platform can evolve independently from the rest of the application.

Why Does Open Innovation Matter?

This is probably the most important part of Ability360.

Accessibility technology deals with something deeply personal: a person's identity, abilities, challenges, goals and future.

I don't want the future of that student to depend completely on one closed AI provider.

With open AI, Ability360 can move toward models that can be:

  • Self-hosted
  • Run locally where practical
  • Swapped for better models
  • Fine-tuned for specific accessibility use cases
  • Adapted for Indian languages and educational contexts
  • Audited and improved by the community

Imagine a college wanting to deploy Ability360 for its students.

It shouldn't have to ask:

“Are we allowed to send all our students' information to someone else's AI server?”

With an open approach, institutions can have significantly more control over where and how the AI runs.

And there is another reason this matters.

Accessibility is not one-size-fits-all.

A solution that works for one student may not work for another.

Open technology gives developers and communities the ability to modify the system rather than simply accepting whatever functionality a closed platform provides.

That means we can eventually build specialized AI experiences for:

  • Students with visual impairments
  • Students with hearing impairments
  • Students with mobility-related disabilities
  • Students with learning difficulties
  • Students who prefer regional languages
  • Students who need simplified explanations

Open innovation turns accessibility from a fixed feature into something the community can continuously improve.

Why This Matters to Me

I have participated in hackathons, built communities and spent a lot of time discovering internships, competitions and learning opportunities.

For me, finding an opportunity often means searching through multiple platforms, reading requirements, asking friends and figuring out what to do next.

And I kept thinking:

What happens to the student who doesn't have that network?

What happens when the information is not accessible?

What happens when the opportunity exists, but the student doesn't know it exists?

What happens when the student has the ability but doesn't have someone telling them:

“You can do this. Here is how.”

That is the student I am building Ability360 for.

I don't want Ability360 to simply become another website listing opportunities.

I want it to become the starting point between a student's potential and their next opportunity.

What I Want to Build Next

The current prototype is only the beginning.

The next version of Ability360 will focus on:

  1. AI Career Mentor

    A personalized assistant that understands the student's skills, goals and progress.

  2. Accessibility-Aware Opportunity Matching

    Matching students with opportunities while considering accessibility requirements.

  3. AI-Powered Student DNA

    Turning assessments, interests, skills and achievements into a continuously evolving student profile.

  4. Personalized Learning Roadmap

    Identifying skill gaps and recommending what the student should learn next.

  5. Accessible Community

    A moderated community where students can ask questions, share experiences and find mentors.

  6. Institutional Deployment

    Making it possible for colleges and organizations to deploy the platform for their own students.

My Agent Session

I used AI-assisted development while building and iterating on Ability360.

DevRelay Agent Session: [ADD YOUR DEVRELAY LINK]

The session demonstrates the process of turning the accessibility problem into a working prototype.

Prize Categories

  • Hacktoberfest Weekend Challenge
  • Open-Source AI / AI Innovation
  • Accessibility & Social Impact

Final Thought

There are millions of students with different abilities, ambitions and dreams.

Technology has already made information available to almost everyone.

Now we need to make opportunity accessible too.

Ability360 is my attempt to build that bridge.

Because accessibility shouldn't mean giving someone a smaller version of the world.

It should mean giving them equal access to the whole world.

Top comments (0)