Accessibility statement

Our goal

transit.bg partially conforms to WCAG 2.2 level AA: we design for it, but have not yet completed a full audit. Every release is checked automatically with axe-core (WCAG 2.1 A and AA rules) on phone and desktop layouts in light and dark mode, and we test keyboard use by hand. Testing with screen readers is not yet systematic. Known gaps are listed below.

What we do

• KeyboardEverything works with a keyboard, with a clearly visible focus. A skip link leads to the content and “/” opens search.
• Screen readersSemantic headings, landmarks and labelled controls. Live updates are not announced on every refresh, so they do not interrupt.
• Reduced motion and transparencyAnimations turn into simple fades when your system asks for reduced motion. Glass effects become solid with “Reduce transparency” in browsers that support it (currently Chrome and Edge), and with “Increase contrast” or a high-contrast mode in every browser.
• ContrastText meets at least 4.5:1 contrast. Status is never shown by colour alone — “Live”, delays and cancellations are written out.
• Light and dark modeFollows your system setting, or choose one in More. High-contrast and forced-colour modes are supported.
• Text scalingText can be enlarged to 200% and the layout adapts from small phones to large screens without horizontal scrolling.

Known limitations

• The map is visual by nature. Everything shown on it — stops, lines, vehicles and journey plans — is also available as text lists, which work fully with screen readers and keyboards.
• Names in the source data sometimes contain abbreviations or inconsistent spelling from the operators. We tidy them up where we can.
• Route colours come from the operators. We choose the text colour on each badge automatically for sufficient contrast, and the line number is always written.

Compatibility

transit.bg relies on HTML, CSS, JavaScript and WAI-ARIA. It is built for current versions of Chrome, Edge, Firefox and Safari and for screen readers such as NVDA, JAWS, VoiceOver and TalkBack. Static pages like this one also work without JavaScript.

Feedback

If something on transit.bg is hard or impossible for you to use, please tell us at contact@transit.bg. Describe the page, what you tried to do and the device or assistive technology you use. We will reply and, wherever possible, fix the problem or provide the information in another way.