Accessibility statement

The target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site does not fully meet them yet, and it has not been audited against them by an outside party. This page describes where things stand; it is not a claim of conformance.

What has been done

• Every page has a "Skip to content" link, a labelled main menu and one main area, so keyboard and screen reader users can jump past the header. The search box is labelled and announces its list of matches.
• Links, buttons and fields show a visible outline when they have keyboard focus.
• Animations stop when your device is set to reduce motion.
• Light and dark themes, from the switch in the header.
• Chart colours are checked against the card behind them: a team colour is lightened or darkened until it has at least 3:1 contrast with the card (WCAG 1.4.11), and two subjects on one dashboard get colours far enough apart to tell apart.
• Charts are drawn as labelled images, and the stats pages show the numbers as real tables you can sort.
• In the dashboard maker, the main actions have keys: A adds a widget, the arrow keys move the selected widget while you edit the dashboard, Delete removes it, Ctrl + D copies it, Ctrl + Z and Ctrl + Y undo and redo, Esc closes what is open, and ? lists the keys.
• You can zoom the pages; nothing blocks pinch-zoom.
• On October 9, 2026 every page was checked at phone, tablet and desktop sizes, from 320 to 1920 pixels wide, in Chromium and in WebKit (the engine behind Safari): no page scrolls sideways, text fields are 16 pixels on touch screens so iPhones do not zoom in on them, and buttons and links have touch targets of at least 44 by 44 pixels. An independent re-check the same day confirmed the results.

Known limitations

• Charts are labelled images: a screen reader hears what a chart is, not each number in it. Many of the same numbers are on the stats, team, player and game pages as tables, but not every chart has a text version yet.
• Resizing a widget on a dashboard means dragging its edge, so it needs a mouse or a touch screen.
• Body text is 14 pixels on every screen, phones included. Your browser's zoom and text-size settings make it larger.
• A few controls are drawn smaller than 44 pixels on phones (the graphics maker's ↑ ↓ ✕ buttons and an empty dashboard's preset buttons), though each answers to a 44-pixel touch area.
• On a phone, the game page sometimes leaves a sorted table column off to the right instead of sliding it into view.
• Images you download (PNG and GIF) carry no text description; add one when you post them.
• The microphone next to Ask uses your browser's speech recognition, which not every browser has. Typing always works.
• The checks so far were automated runs in browsers. The whole site has not yet been tested with a screen reader (such as VoiceOver, NVDA or JAWS), or on a real iPhone or iPad.

Tell us about a problem

If something on Pigskin Lab is hard or impossible to use, email [email protected] or use "Send feedback" at the bottom of any page (no account needed). Say which page, what you were trying to do, and which device, browser and assistive technology you use. Every message reaches the person who runs the site. We aim to reply promptly, and will try to fix the problem or get you the information another way.

About this statement

This statement was last reviewed on October 12, 2026. Pigskin Lab is run by Obegi Software LLC (Mason Obegi), a Washington limited liability company.