Legal
Accessibility Statement
Effective date: August 24, 2026
Longleaf Picks is committed to making longleafpicks.com usable by everyone, including people who use assistive technology such as screen readers, screen magnification, or keyboard-only navigation. This statement describes our approach, the standard we aim to meet, and how to reach us if you run into a barrier.
1. Standard We Aim For
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the standard most commonly referenced by U.S. courts and the Department of Justice as a reasonable benchmark for website accessibility. This is a goal we work toward continuously, not a certification of full compliance.
2. Measures We've Taken
On this site, we've specifically worked to:
- Provide sufficient color contrast between text and its background;
- Make interactive controls — buttons, toggles, search, and sort — operable by keyboard alone, with a visible focus indicator;
- Label form inputs and interactive controls so screen readers announce their purpose (for example, our picks-page sort/search toolbar and mode toggle use proper ARIA labeling);
- Provide text alternatives for meaningful images, such as team logos; and
- Provide a screen-reader-accessible data table alongside our visual backtest chart, so the same information is available in both forms.
3. Known Limitations
Despite our efforts, some parts of the Service may not yet be fully accessible — for example, areas that rely on third-party embeds or content we don't fully control. We are actively working to identify and correct these gaps as we find them.
4. Feedback & Contact
If you encounter an accessibility barrier on longleafpicks.com, please tell us — we want to know about it and fix it. Email lplasch@longleafpicks.com with a description of the issue, the page it occurred on, and the browser or assistive technology you were using. We'll do our best to respond and address the issue promptly.
5. Ongoing Effort
Accessibility is an ongoing effort rather than a one-time fix. As we add new features to the Service, we review them against WCAG 2.1 AA and update this statement as our practices evolve.