Accessibility
Accessibility statement and VPAT
Last updated October 29, 2026. Next review: April 16, 2027. Self-assessed by No Straight Line LLC; not a third-party audit.
Our commitment
No Straight Line LLC wants everyone to be able to tell their career story, including people who use assistive technology. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
- Semantic headings, landmarks, and labeled form fields.
- Full keyboard use with a visible focus ring.
- Text and controls designed to meet WCAG contrast ratios.
- Pages that reflow on small screens and at 400% zoom.
- Reduced motion when your device asks for it.
- Single-column, ATS-safe résumé exports in PDF and Word.
We check with keyboard-only navigation, automated tools, and screen readers including VoiceOver and NVDA.
Known limitations
- Quick start videos do not yet have full captions or transcripts. We plan to add both by January 31, 2027.
- Colors and videos members add to their own portfolios are their choice and may not meet contrast or caption guidelines.
- The Squiggle career graphic is visual. Each chapter is also listed as text on the page.
Conformance report (VPAT)
Modeled on the ITI VPAT 2.5, WCAG edition. Product: No Straight Line web app and public portfolio pages. Standard: WCAG 2.2 Level A and AA. Evaluation: internal review, October 2026.
| Criterion | Conformance | Remarks |
|---|---|---|
| 1.1.1 Non-text content | Supports | Images and icons have text alternatives; decorative graphics are hidden from screen readers. |
| 1.2.1–1.2.5 Time-based media | Partially supports | Quick start videos are short demos. Captions and transcripts are being added. Member-linked videos are hosted by third parties. |
| 1.3.1 Info and relationships | Supports | Headings, lists, landmarks, labels, and tables use semantic markup. |
| 1.3.2 Meaningful sequence | Supports | Reading order matches the visual order. |
| 1.3.3 Sensory characteristics | Supports | Instructions do not rely on shape, size, location, or sound alone. |
| 1.3.4 Orientation | Supports | Works in portrait and landscape. |
| 1.3.5 Identify input purpose | Supports | Sign-in and profile fields use standard autocomplete values. |
| 1.4.1 Use of color | Supports | Status and selection are shown with text or shape as well as color. |
| 1.4.2 Audio control | Supports | No audio plays automatically. Videos start only when you press play. |
| 1.4.3 Contrast (minimum) | Supports | Site text and button colors were adjusted in October 2026 to meet 4.5:1. Colors owners choose for their own portfolios may vary. |
| 1.4.4 Resize text | Supports | Text scales to 200% without loss of content. |
| 1.4.5 Images of text | Supports | Text is real text. The logo and owner-made social cards are the exceptions. |
| 1.4.10 Reflow | Supports | Pages reflow to a 320px width. The Squiggle graphic scrolls within its own area. |
| 1.4.11 Non-text contrast | Supports | Controls and focus indicators meet 3:1. |
| 1.4.12 Text spacing | Supports | Content adapts to user spacing overrides. |
| 1.4.13 Content on hover or focus | Supports | Menus and tooltips are dismissible and stay open while hovered. |
| Criterion | Conformance | Remarks |
|---|---|---|
| 2.1.1 Keyboard | Supports | All features work with a keyboard, including menus, dialogs, and editors. |
| 2.1.2 No keyboard trap | Supports | Dialogs return focus and close with Escape. |
| 2.1.4 Character key shortcuts | Not applicable | No single-key shortcuts are used. |
| 2.2.1 Timing adjustable | Supports | No time limits on writing or editing. |
| 2.2.2 Pause, stop, hide | Supports | No auto-moving content runs longer than five seconds. Motion respects reduced-motion settings. |
| 2.3.1 Three flashes | Supports | No flashing content. Motion respects reduced-motion settings. |
| 2.4.1 Bypass blocks | Supports | Pages use landmarks and a single main region. |
| 2.4.2 Page titled | Supports | Every page has a unique, descriptive title. |
| 2.4.3 Focus order | Supports | Focus follows a logical order. |
| 2.4.4 Link purpose | Supports | Links describe their destination. |
| 2.4.5 Multiple ways | Supports | Pages are reachable through the main menu, footer links, and in-page links. |
| 2.4.6 Headings and labels | Supports | Headings and labels describe their content. |
| 2.4.7 Focus visible | Supports | A visible focus ring appears on every control. |
| 2.4.11 Focus not obscured (minimum) | Supports | The sticky header does not fully cover focused controls. |
| 2.5.1 Pointer gestures | Supports | No multi-point or path-based gestures are required. |
| 2.5.2 Pointer cancellation | Supports | Actions run on release, using standard buttons and links. |
| 2.5.3 Label in name | Supports | Visible labels match accessible names. |
| 2.5.4 Motion actuation | Not applicable | No features use device motion. |
| 2.5.7 Dragging movements | Not applicable | No features require dragging. |
| 2.5.8 Target size (minimum) | Supports | Controls are at least 24 by 24 pixels, and most are 44 pixels tall. |
| Criterion | Conformance | Remarks |
|---|---|---|
| 3.1.1 Language of page | Supports | Pages declare English. |
| 3.1.2 Language of parts | Not applicable | Content is in English. Owner-written text in other languages is not marked. |
| 3.2.1–3.2.2 On focus and on input | Supports | Nothing changes context without a deliberate action. |
| 3.2.3–3.2.4 Consistent navigation and identification | Supports | Navigation and controls stay consistent across pages. |
| 3.2.6 Consistent help | Supports | Help and the contact form are linked from the same place in the footer on every page. |
| 3.3.1 Error identification | Supports | Errors are described in text. |
| 3.3.2 Labels or instructions | Supports | Form fields have labels and short hints. |
| 3.3.3 Error suggestion | Supports | Messages explain how to fix the problem. |
| 3.3.4 Error prevention | Supports | Deletions and purchases ask for confirmation. |
| 3.3.7 Redundant entry | Supports | Information you already entered is saved and reused, not asked for again. |
| 3.3.8 Accessible authentication (minimum) | Supports | Sign-in allows password managers and paste, and offers Google sign-in. No puzzles or memory tests. |
| Criterion | Conformance | Remarks |
|---|---|---|
| 4.1.2 Name, role, value | Supports | Custom controls are built on accessible primitives with correct roles. |
| 4.1.3 Status messages | Supports | Save and error notices are announced to screen readers. |
Feedback and accommodations
If something gets in your way, or you need content in another format, tell us through the contact form with the topic "Accessibility." The form works fully with a keyboard and screen readers. We aim to respond within five business days. Organizations can request this report as part of a procurement package the same way.