Skip to main content

Ways to work with Upriver

Every team is at a different point. Some have a service that is already failing people and a deadline approaching. Some are building something new and would rather get it right the first time. These are four ways to work together, ordered by commitment.

Find the plan that matches your needs

Sprint1–2 weeks

Accessibility Fix Sprint

We bring your storefront or landing page up to standard before it becomes a legal problem.

Ideal for

Companies selling online in Spain and the EU. The European Accessibility Act has applied since June 2025, and in Spain it is law under Ley 11/2023.

What's included

  • Audit against EN 301 549, the European standard that incorporates WCAG 2.1 AA
  • Fixes to checkout, forms, navigation, contrast and keyboard paths
  • Accessibility statement drafted to EU requirements
  • Retest and sign-off once fixes are live

Deliverables

  • A fixed storefront
  • An accessibility statement you can publish
  • A conformance summary for your records
Study3–5 weeks

Research With Disabled Users

We identify what blocks your users, through research with the people it affects.

Ideal for

Teams who suspect their service excludes people, but cannot yet point to where or why.

What's included

  • Task-based sessions on your real flows with blind and low-vision participants, recruited and paid as experts
  • Screen reader walkthroughs across NVDA, JAWS and VoiceOver
  • Thematic analysis of what blocked people and why

Deliverables

  • Findings report with direct participant quotes
  • Session clips, shared with consent
  • Prioritized opportunities tied to specific flows
Project4–8 weeks

Accessible Design & Build

We design and build accessible services, whether you are starting fresh or fixing what exists.

Ideal for

Towns, agencies and nonprofits with a service that is failing people and a deadline approaching. Product and civic tech teams who would rather build it right than pay for it twice.

What's included

  • If it exists: an audit of the current experience against WCAG 2.1 AA, using real assistive technology
  • If it does not: accessible foundations first — color, type, focus, states, components
  • Flows, navigation and content designed with keyboard and screen reader paths from the first wireframe
  • Testing with blind and low-vision participants
  • Front-end implementation, or developer-ready specs with acceptance criteria

Deliverables

  • Designed accessible flows and components
  • An implemented front-end, or prioritized tickets your developers can act on
  • An accessible token set with usage documentation
  • A conformance summary you can attach to a procurement record
RetainerOngoing, monthly

Embedded Accessibility Lead

We join your team as your accessibility lead.

Ideal for

Organizations with developers but no accessibility expertise, who need it to hold after a project ends.

What's included

  • A set number of days each month
  • Design and code review before things ship
  • Standards and component guidance your team can apply without asking
  • Training, and escalation for the genuinely hard problems

Deliverables

  • Reviewed work moving through your backlog
  • A living standard your team maintains
  • A quarterly conformance check

Not sure which one fits? Tell us about the problem and we will point you to the right one.