Accessibility

What's in place today

• Labels on every form field

  Every input, dropdown, and calculator field has a visible label that is programmatically connected to it — nothing relies on placeholder text alone.

• Keyboard operability

  Everything you can click — deal cards, save bookmarks, status filters, the pipeline stages, the live calculator — can also be reached with Tab and operated with Enter or Space, and keyboard focus is marked with a clear green outline.

• Checked color contrast

  The text colors used on our dark background were verified with computed WCAG contrast ratios (not by eye), and the shades that fell short of the 4.5:1 minimum for normal-size text were adjusted.

• Never color alone

  Deal Scores pair the green/yellow/red color with the number and a text label, price trends pair the arrow with a word, and the password checklist changes its symbol as well as its color.

• Text alternatives for visuals

  Score rings and score-breakdown bars carry spoken descriptions for screen readers, and the price-trend chart is backed by a full comparable-sales table with the same data as text.

• Honest, plain-language errors

  Error and status messages are announced to assistive technology, written in plain English, and never replaced by raw technical output.

Known limitations

This list comes from our own audit of the app — it is what we know is not fully accessible yet, stated plainly:

• The price-trend chart is a visual line chart. It has a short spoken summary and the full comparable-sales table below it carries the same data as text, but the chart itself cannot be explored point-by-point with a keyboard or screen reader.
• The pipeline stage picker on Saved deals (Watching → Purchased → Listed → Sold) is a row of buttons you move through with Tab. Screen readers announce it as a radio group, which usually implies arrow-key navigation — arrow keys do not move between stages yet.
• The Deal Room calculator recalculates on every keystroke, and the updated Deal Score is announced politely. For screen reader users this can feel chatty while typing a number.
• The thin borders around input fields are lower-contrast than WCAG recommends for component boundaries; fields are still identified by their labels and by the green highlight they receive on focus.
• There is no skip-to-content link yet. The header navigation is short (five links), so tabbing past it is quick, but we know a skip link is the proper fix.
• ChronoScout currently runs on seeded sample data, and "View listing" links point at a placeholder marketplace domain in a new tab (the new-tab behavior is announced in the link name) — those pages are outside our control.
• We have not yet commissioned a third-party accessibility audit; testing so far has been in-house keyboard walkthroughs and automated contrast checks.

Tell us what's not working

If any part of ChronoScout is hard or impossible for you to use, we want to know — a short note about what you were trying to do and what got in the way is enough. Email revanthsurjeet12@gmail.com and we'll do our best to fix it or suggest a workaround.

Last updated: 2026-08-18