Our commitment
Set-Aside Pro is meant to be usable by everyone, including people who rely on screen readers, keyboard navigation, or other assistive technology. We target conformance with Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Because federal contracting matters to small businesses across the country, we also aim to meet the spirit of Section 508 even though we're an independent publication, not a federal agency.
What we do
- Server-rendered HTML, so screen readers and assistive tech see content directly without waiting on JavaScript.
- Semantic markup — real
<header>,<nav>,<main>,<article>regions and ARIA labels where they help. - Color palette derived from the U.S. Web Design System (USWDS), tuned for sufficient text contrast at body and small sizes.
- Keyboard-accessible navigation, forms, and dropdowns. No mouse-only interactions.
- Visible focus indicators on interactive elements.
- Images have alt text; logos have agency names; icons that carry meaning are accompanied by visible text.
- Forms use real
<label>elements and surface inline errors viarole="alert".
Known gaps
We're not done. Areas we're tracking:
- The assistant chat composer doesn't yet announce streaming responses to screen readers via an ARIA live region — coming in a follow-up.
- Some filter pickers use
<details>elements that, on older versions of NVDA, don't announce their expanded/collapsed state cleanly. - We haven't completed a third-party audit. We do internal review against axe-core and keyboard-only sweeps.
Tell us when we miss
If you hit an accessibility barrier — anything from "this color is too low contrast" to "I can't reach this dropdown with the keyboard" — please email hello@setasidepro.com. Be as specific as you can about the page, the assistive technology, and what happened. We respond to accessibility reports within 5 business days and prioritize them.
Browser and assistive-tech support
We test against the current and previous major versions of Chrome, Firefox, Safari, and Edge, on macOS, Windows, iOS, and Android. We test screen-reader behavior with VoiceOver (macOS/iOS) and NVDA (Windows). If you use a different stack and something breaks, please report it.