Ben Franklin Transit

Top things to fix

Score by category

Over time

Overall score across the last 20 checks — unchanged since 2026-07-08.

What changed since your last check

• Correctness— no change
• Freshness— no change
• Rider experience— no change
• Realtime quality— no change

What changed in this feed

Overall grade and score held steady since 2026-07-08.

Same feed file as 2026-07-08; the published zip did not change.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

What changed over time

On 2026-06-19 this feed started at grade B. On 2026-06-20 it cleared scorecard_rt_trip_updates_unreachable. On 2026-06-24 it cleared expired_calendar, stop_too_far_from_shape_using_user_distance. On 2026-06-25 it cleared scorecard_rt_trip_updates_unreachable. As of 2026-07-09 it holds grade B.

A plain-language history of this feed, newest first.

• 2026-06-27 Score rose 3 points, realtime rose 15 points.
• 2026-06-26 Score fell 3 points, realtime fell 16 points.
• 2026-06-24 Score rose 4 points, correctness rose 10 points.

Everything we checked

• Warning2704 instances

  2704 of 2704 trips don't say whether the vehicle is wheelchair accessible.

  Even with accessible stops, riders need to know the bus itself can take them.

  Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Agencies here usually clear this within about 1 week (based on 5 observed fixes).

  Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning631 instances

  631 of 851 stops don't say whether a wheelchair user can board there.

  Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

  Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

  Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

• Warning1 instance

  The feed contains no fare information.

  Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

  Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

  Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

• 10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (42, 10, 67, 48, 50, and more).

  Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

• 837 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Quinault Ave at Okanogan Pl", "Young St at Canal Dr", "Canal Dr at Crosswind Blvd", and more).

  Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Some fixes we can make for you

These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.

• Trimmed surrounding whitespace 4 changes

  For example: 'stop_desc': 'Road 68 at Three Rivers Drive / ' -> 'Road 68 at Three Rivers Drive /'

Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip