Inspiration
People searching for social support often face two problems at once: the life event itself and the complexity of navigating public-service information. That burden is larger for older adults, disabled people, caregivers, people with limited digital confidence, and anyone using a slow connection.
RightsBridge asks a different question: what access barrier is making the next step harder today? It then adapts the presentation without collecting identity data or pretending to make an official eligibility decision.
What it does
RightsBridge is a barrier-aware social-rights navigator with five plain-language entry paths:
- home-care support,
- health coverage / income testing,
- 65+ social support,
- birth / new-child support,
- disability-related support.
The user then chooses the access barrier that matters today: reading difficulty, limited internet, assistive technology, or acting as a caregiver for someone else.
The result is a path card, not an eligibility verdict. It explains why the topic may be relevant, gives three concrete first steps, suggests what information may be useful to prepare, and links to an official public source for current procedures.
Accessibility is part of the product
RightsBridge includes a visible skip link, semantic keyboard flow, large-text mode, high-contrast mode, reduced-motion mode, browser-based read-aloud, print / Save-as-PDF support, responsive mobile layouts, and ARIA live announcements.
Production QA on a 390×844 viewport showed zero horizontal overflow. A native Chrome Tab / Enter flow successfully navigated from the skip link through the selections to the generated result. Console errors and warnings were zero during acceptance testing.
Privacy and safety boundary
The MVP asks for zero personal identifiers. There is no account, identity number, name field, document upload, or application submission.
RightsBridge does not determine legal entitlement and does not represent a public institution. It provides educational navigation and routes users to official public sources for current requirements and decisions.
How we built it
The hackathon MVP is deliberately small and auditable: semantic HTML, CSS, and vanilla JavaScript. Browser-native APIs provide speech synthesis and print/PDF support. The application is deployed on GitHub Pages and requires no API request to generate a path after the initial page load.
Challenges
The main challenge was avoiding the pattern where personalization becomes unnecessary profiling. RightsBridge adapts to an interaction barrier, not to a detailed identity profile. We also kept a strict boundary between useful guidance and an official rights decision.
Hackathon provenance / prior work disclosure
A previous project, sosyalhakrehberi.com, and older repositories such as senih25/SocialRightOS-frontend existed before Code for Humanity. They informed the problem domain, UX learning, and public-content research.
The Code for Humanity submission period began 16 July 2026. The new RightsBridge repository was created 3 September 2026, during the hackathon period.
No application code from the pre-existing repositories was copied into RightsBridge. The submission has a separate repository, codebase, interaction model, accessibility layer, and commit history.
Accomplishments
- 5 social-rights starting paths
- 4 barrier-aware presentation modes
- mobile 390×844: zero horizontal overflow
- native keyboard-only Tab / Enter flow: PASS
- console errors/warnings: 0 in acceptance testing
- no pathway-generation network call after initial load
- zero personal identifiers collected
- public GitHub Pages deployment and MIT-licensed source
- 1:36 demo video with no copyright issue
What's next
The path-card model can expand to more rights, languages, and jurisdictions. Future work can add versioned public-source references, offline/PWA packaging, community accessibility testing, and structured content review while keeping the same invariant: guidance can adapt; legal entitlement remains an official human/public-institution decision.
Links
Live: https://senih25.github.io/rightsbridge-humanity/
Source + QA: https://github.com/senih25/rightsbridge-humanity
Demo: https://youtu.be/YRk8vms5o1M
AI-assisted development disclosure
ChatGPT was used as a development assistant for planning, implementation support, QA automation, and submission preparation. RightsBridge itself does not run AI inference at runtime: path-card generation is deterministic, client-side, and dependency-light. Chrome DevTools was used for production acceptance testing. No paid third-party API is required by the live application.
Built With
- accessibility
- civic-tech
- css3
- github
- html5
- human-centered-design
- javascript
- low-bandwidth
- privacy-by-design
- social-good
- web-speech-api

Log in or sign up for Devpost to join the conversation.