Accessibility

The short version

I want everyone to be able to use this site. Whether you rely on a screen reader, navigate by keyboard, zoom in to 400%, or just happen to be on a slow connection at the ballpark, the experience should work for you.

I'm not going to pretend it's perfect. Scorecards are inherently visual, and making dense SVG grids truly accessible is hard. But I care about getting it right, and I'm working on it.

Where things stand

The site targets WCAG 2.2 Level AA. In practice, that means:

• Keyboard navigation works everywhere: date picker, game cards, theme toggle, all of it
• Colour contrast meets AA in both light and dark themes
• Colour alone never carries meaning. Pitch types, outs, and play results always have text alongside the visual indicators
• The whole thing is plain HTML, CSS, and vanilla JS. No heavy framework. It loads fast and works on anything with a browser

Known issues

I keep a running list of accessibility gaps and work through them over time. Some are trickier than others, dense SVG scorecards especially. If you run into something that isn't working, the fastest way to get it in front of me is the contact form.

What works well

• Date picker: full ARIA grid pattern with arrow keys, Home/End, Page Up/Down, Escape to close
• Collapsible sections: <details>/<summary> with arrow key open/close
• Theme toggle: label updates to describe the target state ("Switch to dark mode" / "Switch to light mode")
• Mobile nav: hamburger button announces expanded/collapsed state
• Focus indicators: 3px solid outlines on all interactive elements
• Keyboard shortcuts: D for dark mode, L for light mode, ←/→ to step the date one day on the schedule page
• Thumbnail SVGs: have role="img" and aria-label

External links (MLB data and other sources) are outside my control and may not meet the same bar.

Tell me what's broken

If something doesn't work for you, I want to hear about it. Send me a message; it goes straight to me, not a form that disappears into nothing. If you can mention what assistive tech you're using and what went wrong, that helps me fix it faster. But even a quick "this didn't work" is useful.