Embark

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

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.

Everything we checked

• Warning387 instances

  387 of 12730 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)

• Warning171 instances

  171 of 1644 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)

• Warning70 instances

  Missing bike allowance (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning36 instances

  Some rider-facing names are in ALL CAPS or all lowercase.

  ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

  Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

  Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning15 instances

  The feed contains route shapes no trip uses.

  Harmless to riders, but it bloats the feed and suggests stale export data.

  Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)

  Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning10 instances

  Some stops exist in the feed but no trip ever stops at them.

  Riders may walk to a stop where no bus is scheduled to arrive.

  Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning2 instances

  Same route and agency url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: same_route_and_agency_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Some service calendars in the feed have already ended.

  Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

  Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

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

  Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Warning1 instance

  Some service calendars have no days of the week switched on.

  Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

  Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

  Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info17 instances

  Some files contain columns that are not part of the GTFS spec.

  Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

  Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

  Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info2 instances

  Big gap in service (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

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

  Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

• Info1 instance

  Service window outside feed period (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

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

  Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Beyond the grade

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

• 21 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (002, 008, 011, 012, 013, 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.

• 1526 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("S Walker Ave @ SW 44 St", "S May Ave @ I-240 Service Rd", "SW 29 St @ S May Ave", 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 1 change

  For example: 'existing_route_long_name': 'East Route-Oklahoma River Cruise ' -> 'East Route-Oklahoma River Cruise'

• Recased shouting stop names 4 changes

  For example: S HARVEY AVE @ SW 21ST ST -> S Harvey Ave @ Sw 21st St

• Recased shouting route names 38 changes

  For example: N COLTRANE -> N Coltrane

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