Accessibility Statement.
1. Our commitment
We want everyone to be able to use sourceBOLD, regardless of how they browse. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA across both this marketing site and the signed-in portal. That’s a goal we design and build toward, not a certification — where we fall short, we’d rather tell you plainly (see the known limitations below) and fix it.
2. What we’ve built
Accessibility is part of how the product is built, not a layer added at the end. Concretely, that includes:
- Keyboard access. You can navigate and operate the site and portal without a mouse. Dialogs and menus trap focus while open, restore it when closed, and close on
Esc; a “skip to content” link lets keyboard users jump past the navigation. - Visible focus. Every interactive element shows a clear focus indicator when reached by keyboard, and it stays visible in Windows High Contrast and other forced-color modes — where many sites’ focus rings disappear entirely. We check this by tabbing through pages by hand in a real browser, not only in code.
- Reduced motion. If your system requests reduced motion, we turn off non-essential animation (including the scrolling marquee and progress-bar motion).
- Semantic structure. Pages use real headings and landmark regions (
nav,main,footer) so assistive technology can understand and skip through the layout. - Color and contrast. Body text and controls are chosen to meet AA contrast — with the exceptions we list below — and we never rely on color alone to convey status: states are labeled in words as well.
- Forms. Fields have programmatic labels. Required fields are marked for sighted users and announced as required by assistive technology, rather than leaning on the asterisk alone. When something you entered is rejected, the message is attached to the field it’s about — so you hear it on reaching that field, not only as a notice above the form. Common fields are tagged so your browser or password manager can fill them.
- Data tables. Operational tables in the portal carry proper header semantics so screen-reader users can associate each cell with its column.
3. Known limitations
We keep this list honest rather than claiming perfection. As of the date above, we’re aware that:
- Some small supporting text — captions under a figure, secondary labels, the faintest tier of helper text — sits slightly under our contrast target on certain backgrounds. Nothing is available only there: every such line repeats or explains something stated at full contrast nearby. It’s on the list.
- Some documents that come from outside sourceBOLD — a blank government tax form, or a scan or photo somebody uploaded — may not meet the same standard as our own pages. A scan in particular has no text in it for a screen reader to read. Ask us and we’ll get you an accessible copy.
- While a form is submitting, and on controls that aren’t currently available to you, the label is dimmed. The guidelines exempt inactive controls, but it’s worth saying plainly — the result of the action is always announced when it completes, so you don’t need to read the faint state to know what happened.
4. How we keep it up
We review accessibility periodically and hold new or redesigned surfaces to the same standard before they ship, so the product doesn’t drift. Accessibility isn’t a one-time audit for us — it’s part of the definition of “done.”
Some of that is now automatic: a set of checks runs whenever we change the code and fails the build if a color pair, a focus indicator, a form label or a page’s structure slips back. Those checks can’t tell us whether a page is actually usable, though — only that specific things we’ve already fixed haven’t broken again. The judgment still comes from testing by hand, and from what you tell us.
5. Report a barrier
If you hit something that doesn’t work for you — a page, a control, a document, anything — please tell us. Email hello@sourcebold.com with the page address and a short description of what happened (and the assistive technology you were using, if any). We’ll respond and work with you on an accessible alternative while we fix the underlying issue.
6. Changes to this statement
As we remediate known issues or the standard we target changes, we’ll update this page and bump the “Last updated” date above.
7. Contact
Questions about accessibility? Email hello@sourcebold.com or see our Privacy Policy and Terms of Service for the broader picture.