OpenAI 2026 hackathon

Can You Read Me Now?

A simple tool that shows a different way to check how readable your text really is.

Solo project by MV Braverman · 0 likes · 0 comments

View the project on Devpost

Archive position — measured, not model output

0 likes on Devpost

2,263 of the 7,850 archived projects have more likes, and 5,587 share exactly 0 — so this project's #3,105 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,587
11,758
2284
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,58771.2%
11,75822.4%
22843.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,850 archived projects, captured when this archive was built.

User Stories BotA demo video on every pull request

Get a demo video on every new feature

GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.

Executive Summary

What the company appears to be

The author states that "Can You Read Me Now?" is a standalone playground tool for designers and developers to explore how text contrast and typography affect readability. It is described as an interactive sibling to a larger project, Readable.FYI, which inspects real web pages for readability.

What changed

No evidence of prior versions or changes is provided. The description only presents this as a single project submitted to the OpenAI 2026 hackathon.

Single most important open question — commercial due-diligence read

Is there any evidence that this tool has traction, revenue, or adoption beyond its author’s own submission? The description does not indicate any of these.

Back to contents

What The Product Actually Is

The description states that the product is a standalone HTML, CSS, and JavaScript playground designed to help users change text color, background color, font size, and font weight. It compares two contrast measurement systems: WCAG 2 and APCA, showing both results side-by-side.

It includes:

  • Interactive controls for changing visual properties
  • Real-time display of contrast ratios
  • Visual feedback on readability using APCA guidance
  • Keyboard accessibility and screen-reader support

The tool is built without frameworks or external dependencies and uses GPT-5.6 as a development collaborator during build week.

Inference This is an exploratory tool, not a SaaS product or platform with ongoing usage or monetization.

Back to contents

Positioning & Claim Evolution

The author claims that the tool:

  • Makes the disconnect between contrast compliance and readability visible
  • Helps designers and developers understand why certain dark-mode patterns are hard to read despite passing standards like WCAG 2 AAA
  • Is a “playground” version of a larger tool, Readable.FYI

It is positioned as an educational or illustrative tool rather than a commercial product.

Inference The positioning is focused on usability and awareness, not monetization or scale.

Back to contents

Target Customer & ICP

The description states that the target users are:

  • Designers
  • Developers

They are described as people who work with typography and contrast in SaaS websites.

There is no evidence of segmentation beyond this general audience. No specific personas, buyer roles, or customer types are mentioned.

Inference The ICP appears to be technical professionals working on web UI/UX design or development.

Back to contents

Business Model & Pricing Evidence

No business model or pricing information is provided in the description.

There is no mention of:

  • Revenue streams
  • Subscription tiers
  • Licensing models
  • Paid features or freemium offerings

Inference The tool appears to be a prototype or demo, not a commercial offering.

Back to contents

Technical & Delivery Signals

The project was built using:

  • HTML, CSS, JavaScript
  • No framework or package manager
  • GPT-5.6 for development assistance
  • Vercel deployment
  • APCA library (adapted from Myndex/apca-w3 v0.1.9)
  • WCAG 2 relative luminance implementation

The author notes:

  • The tool works offline and is inspectable
  • It includes automated contract tests
  • It supports keyboard navigation and screen readers
  • It avoids build steps or runtime dependencies

Inference The technical approach is minimalistic, static, and focused on accessibility and usability.

Back to contents

Traction & Maturity Signals

There is no evidence of:

  • Customers
  • Revenue
  • Usage metrics
  • Product adoption
  • Market traction

The description states that the tool was submitted to a hackathon and is part of a broader project, but does not indicate any real-world deployment or user base.

Inference This is an early-stage prototype with no demonstrated traction or maturity.

Back to contents

Competitive Context

No competitive analysis or market context is provided in the description.

There is no mention of:

  • Competing tools
  • Market size
  • Industry trends
  • Prior art

Inference The competitive landscape is unknown, and there is no evidence of existing solutions or differentiation.

Back to contents

Open Questions & Risks

Key risks and open questions include:

  • No revenue or customer data — the tool appears to be a prototype
  • No indication of scalability or monetization strategy
  • The project is described as a hackathon submission, suggesting it may not have evolved into a product
  • No evidence of team size beyond one person (MV Braverman)
  • No mention of IP, patents, or proprietary technology

Inference The tool lacks commercial viability indicators and may be a proof-of-concept only.

Back to contents

Questions the description leaves open

  1. Is the larger project, Readable.FYI, currently in development or deployed?
  2. Has the playground been used by any teams or organizations beyond personal use?
  3. What is the roadmap for monetization or product evolution?
  4. Are there plans to expand beyond the current scope (e.g., support for more fonts, integrations)?
  5. How does this tool compare to existing contrast-checking tools in the market?

Back to contents

Overall Assessment

There is no evidence of:

  • Revenue
  • Customers
  • Product-market fit
  • Scalability
  • Commercial traction

The project is described as a hackathon submission and prototype, with no indication of commercial viability or growth potential.

Inference This tool is not ready for investment or partnership consideration at this time. It may be an early-stage idea or demonstration with limited commercial relevance.

Back to contents

User Stories BotA demo video on every pull request

Get a demo video on every new feature

GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on Devpost. Back to the full gallery on Devpost.

This competitive analysis was produced by top-founders.com (opens in a new tab)

Generated by a language model from this project's public Devpost page — its tagline, the author's own write-up and any built-with tags listed there — as captured in August 2026. Short quotations are the author's words. It is an opinion on the idea as a business, not on the people behind it, and it reflects the description as published then. If the project has moved on, request a correction below. The analysis is not independent research and contains no verified traction, revenue or customer data.

An independent guide by KFG International LLC — not affiliated with, endorsed by, or connected to Devpost or OpenAI.

Are you the author of this project? Request removal or a correction (support@kfginternational.com). Requests from authors are acted on within 48 hours, and in any case within seven days. Privacy notice.