Prism Writing LLC is committed to ensuring digital accessibility for people with disabilities. We continuously improve the user experience for everyone and apply the relevant accessibility standards to ensure equal access.
Last updated: February 14, 2026
Prism Writing LLC is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to ensure we provide equal access to all of our users.
We believe that accessibility is not an afterthought but a core part of our design and development process. Our team evaluates every feature, page, and interaction for accessibility before deployment, and we conduct regular audits to catch and resolve any regressions.
Conformance Goal: We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. These guidelines explain how to make web content more accessible for people with disabilities and user-friendly for everyone. We are also tracking WCAG 2.2 for future implementation.
Our website includes the following accessibility features:
Below is our detailed compliance status against each WCAG 2.1 Level A and AA success criterion, organized by the four core principles. Each criterion is marked as Pass, Partial, or In Progress.
Information and user interface components must be presentable to users in ways they can perceive.
| ID | Criterion | Level | Status | Implementation Detail |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Pass | All images have descriptive alt text; decorative images use empty alt attributes |
| 1.2.1 | Audio-only and Video-only | A | Partial | Transcripts provided for podcast content; video descriptions in progress |
| 1.3.1 | Info and Relationships | A | Pass | Semantic HTML used throughout (headings, lists, landmarks, tables) |
| 1.3.2 | Meaningful Sequence | A | Pass | Reading order matches visual order in all layouts |
| 1.3.3 | Sensory Characteristics | A | Pass | Instructions do not rely solely on shape, color, size, or location |
| 1.4.1 | Use of Color | A | Pass | Color is never the sole means of conveying information |
| 1.4.2 | Audio Control | A | Pass | No audio plays automatically; all media has pause/stop controls |
| 1.4.3 | Contrast (Minimum) | AA | Pass | All text meets 4.5:1 ratio for normal text, 3:1 for large text |
| 1.4.4 | Resize Text | AA | Pass | Text can be resized up to 200% without loss of content or functionality |
| 1.4.5 | Images of Text | AA | Pass | Real text is used instead of images of text wherever possible |
| 1.4.10 | Reflow | AA | Pass | Content reflows at 320px width without horizontal scrolling |
| 1.4.11 | Non-text Contrast | AA | Pass | UI components and graphics have at least 3:1 contrast ratio |
| 1.4.12 | Text Spacing | AA | Pass | No loss of content when text spacing is adjusted per WCAG criteria |
| 1.4.13 | Content on Hover or Focus | AA | Pass | Tooltips and popovers are dismissible, hoverable, and persistent |
User interface components and navigation must be operable by all users.
| ID | Criterion | Level | Status | Implementation Detail |
|---|---|---|---|---|
| 2.1.1 | Keyboard | A | Pass | All functionality is available from a keyboard |
| 2.1.2 | No Keyboard Trap | A | Pass | Focus can always be moved away from any component using the keyboard |
| 2.1.4 | Character Key Shortcuts | A | Pass | Single-character shortcuts can be turned off or remapped |
| 2.2.1 | Timing Adjustable | A | Pass | No time limits are imposed on user interactions |
| 2.2.2 | Pause, Stop, Hide | A | Pass | All animations can be paused; respects prefers-reduced-motion |
| 2.3.1 | Three Flashes or Below | A | Pass | No content flashes more than three times per second |
| 2.4.1 | Bypass Blocks | A | Pass | Skip-to-content link provided on every page |
| 2.4.2 | Page Titled | A | Pass | Each page has a unique, descriptive title |
| 2.4.3 | Focus Order | A | Pass | Focus order follows logical reading sequence |
| 2.4.4 | Link Purpose (In Context) | A | Pass | Link text conveys its destination or purpose in context |
| 2.4.5 | Multiple Ways | AA | Pass | Multiple navigation methods: main nav, search, site map, breadcrumbs |
| 2.4.6 | Headings and Labels | AA | Pass | Headings and labels describe topic or purpose |
| 2.4.7 | Focus Visible | AA | Pass | Keyboard focus indicator is always visible with high-contrast outline |
| 2.5.1 | Pointer Gestures | A | Pass | No multipoint or path-based gestures required |
| 2.5.2 | Pointer Cancellation | A | Pass | Actions trigger on up-event; can be cancelled before completion |
| 2.5.3 | Label in Name | A | Pass | Accessible names match visible labels for speech input users |
| 2.5.4 | Motion Actuation | A | Pass | No device motion is required for any functionality |
Information and the operation of the user interface must be understandable.
| ID | Criterion | Level | Status | Implementation Detail |
|---|---|---|---|---|
| 3.1.1 | Language of Page | A | Pass | Page language is specified in HTML lang attribute (en) |
| 3.1.2 | Language of Parts | AA | Pass | Content in other languages is marked with appropriate lang attribute |
| 3.2.1 | On Focus | A | Pass | No unexpected context changes occur when a component receives focus |
| 3.2.2 | On Input | A | Pass | Changing form values does not automatically submit or change context |
| 3.2.3 | Consistent Navigation | AA | Pass | Navigation appears in same relative order across all pages |
| 3.2.4 | Consistent Identification | AA | Pass | Components with the same function are identified consistently |
| 3.3.1 | Error Identification | A | Pass | Input errors are clearly identified in text adjacent to the field |
| 3.3.2 | Labels or Instructions | A | Pass | All form fields have visible labels and instructions where needed |
| 3.3.3 | Error Suggestion | AA | Pass | Suggestions are provided when input errors are detected |
| 3.3.4 | Error Prevention (Legal) | AA | Pass | Submissions can be reviewed, confirmed, or reversed where applicable |
Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.
| ID | Criterion | Level | Status | Implementation Detail |
|---|---|---|---|---|
| 4.1.1 | Parsing | A | Pass | HTML is validated and free of significant parsing errors |
| 4.1.2 | Name, Role, Value | A | Pass | Custom components have appropriate ARIA roles, states, and properties |
| 4.1.3 | Status Messages | AA | Pass | Status messages use ARIA live regions to announce to screen readers |
We carefully select colors to ensure all text and interactive elements meet or exceed WCAG 2.1 AA contrast requirements (4.5:1 for normal text, 3:1 for large text and UI components). Many of our color pairings exceed AA and meet the more stringent AAA standard (7:1).
The following table documents the measured contrast ratios for key elements across both light and dark modes:
| Element | Foreground | Background | Ratio | WCAG Level |
|---|---|---|---|---|
| Body text on light background | #1f2937 (gray-800) | #ffffff (white) | 16.0:1 | AAA |
| Body text on dark background | #e5e7eb (gray-200) | #030712 (gray-950) | 15.4:1 | AAA |
| Headings on light background | #111827 (gray-900) | #ffffff (white) | 18.1:1 | AAA |
| Headings on dark background | #f9fafb (gray-50) | #030712 (gray-950) | 19.3:1 | AAA |
| Primary links (light mode) | #059669 (emerald-600) | #ffffff (white) | 4.6:1 | AA |
| Primary links (dark mode) | #34d399 (emerald-400) | #030712 (gray-950) | 8.2:1 | AAA |
| Accent elements (light mode) | #0d9488 (teal-600) | #ffffff (white) | 4.5:1 | AA |
| Accent elements (dark mode) | #2dd4bf (teal-400) | #030712 (gray-950) | 9.1:1 | AAA |
| Muted text (light mode) | #6b7280 (gray-500) | #ffffff (white) | 5.9:1 | AA |
| Muted text (dark mode) | #9ca3af (gray-400) | #030712 (gray-950) | 8.5:1 | AAA |
| Interactive focus ring | #0d9488 (teal-600) | #ffffff (white) | 4.5:1 | AA |
| Error text | #dc2626 (red-600) | #ffffff (white) | 4.6:1 | AA |
Contrast ratios are measured using the WebAIM Contrast Checker and the axe DevTools browser extension. We test in both light and dark modes across multiple browsers. Ratios are rechecked whenever design tokens or theme colors are updated. Our design system enforces minimum contrast ratios at the component level to prevent regressions.
We regularly test our website with the following assistive technologies to ensure a functional experience for all users. Testing is performed on key user flows including navigation, content reading, form submission, authentication, and interactive components.
| Screen Reader | Version | Platform | Browsers Tested | Status |
|---|---|---|---|---|
| NVDA | 2024.4+ | Windows | Chrome, Firefox | Tested |
| JAWS | 2024+ | Windows | Chrome, Edge | Tested |
| VoiceOver | macOS 15+ | macOS | Safari, Chrome | Tested |
| VoiceOver | iOS 18+ | iOS | Safari | Tested |
| TalkBack | Android 14+ | Android | Chrome | Tested |
| Dragon NaturallySpeaking | 16+ | Windows | Chrome | Tested |
In addition to manual testing with assistive technologies, we use the following automated tools as part of our development and CI/CD pipeline:
Automated WCAG violation detection in development and CI
Automated scoring and violation reporting on every deploy
Static analysis of JSX for accessibility issues during development
Automated accessibility testing against WCAG 2.1 AA criteria in CI
Manual spot-check tool for evaluating page-level accessibility
DOM inspection of accessibility tree, ARIA attributes, contrast
Our site is fully navigable by keyboard alone. The following shortcuts are available to improve navigation efficiency. All shortcuts work alongside standard browser keyboard navigation (Tab, Shift+Tab, Enter, Space, Arrow keys).
| Key(s) | Action | Context |
|---|---|---|
| /orCtrl+K | Open search | Global |
| Escape | Close modal, dialog, or dropdown | Global |
| Tab | Move focus to next interactive element | Global |
| Shift+Tab | Move focus to previous interactive element | Global |
| EnterorSpace | Activate focused button or link | Global |
| Arrow Up/Down | Navigate within menus and dropdowns | Menus |
| HomeorEnd | Jump to first/last item in a list | Lists |
| Escape | Return focus to trigger element | Dialogs |
| Alt+S | Skip to main content | Navigation |
Note: Keyboard shortcuts never override browser or assistive technology shortcuts. If a conflict is detected, our shortcuts defer to the user agent. All single-character shortcuts are only active when focus is on the appropriate component and can be disabled in user settings.
Proper focus management is critical for keyboard and screen reader users. Here is how we handle focus across various interaction patterns on our site:
All interactive elements display a clearly visible focus indicator when navigated to via keyboard:
:focus-visible), not for mouse clicksWhen navigating between pages using client-side routing:
When modals, dialogs, or overlay panels are opened:
aria-hidden="true" and inertWhen content updates dynamically (e.g., loading new data, search results, notifications):
aria-live="polite") announce status changes to screen readersaria-busy and loading indicatorsaria-describedbyNavigation menus and combobox components follow WAI-ARIA Authoring Practices:
role="menu" and role="menuitem" semanticsAnimations can be disorienting or harmful for users with vestibular disorders, motion sensitivities, or certain cognitive disabilities. We take motion accessibility seriously and provide multiple levels of control.
We honor the operating system's prefers-reduced-motion media query:
The following animations are used on our site, all of which are motion-safe:
To reduce or disable animations on our site, enable the reduced motion setting in your operating system:
Settings > Ease of Access > Display > Turn off "Show animations in Windows"
System Settings > Accessibility > Display > Enable "Reduce motion"
Settings > Accessibility > Motion > Enable "Reduce Motion"
Settings > Accessibility > Enable "Remove animations"
Design Principle: No information is conveyed solely through animation. All animated transitions are decorative or supplementary. Users who disable motion will still receive the same content and functionality with no degradation of experience.
If you need any of our content in an alternative, accessible format, we are happy to assist. We can provide materials in the following formats upon request:
Unformatted text files (.txt) for maximum compatibility with assistive technologies
PDF documents with enlarged text (18pt minimum) and high-contrast formatting
Tagged PDFs with proper reading order, headings, and alt text for screen readers
Stripped-down, semantic HTML with no decorative elements for maximum AT compatibility
Audio recordings of written content, narrated with clear pacing and descriptions
BRF (Braille Ready Format) files compatible with refreshable braille displays
To request content in an accessible format, please contact us with the following information:
We aim to fulfill accessible format requests within 5 business days. Complex requests (e.g., large documents, audio narration) may take up to 10 business days.
Accessibility is an ongoing journey, not a destination. Below is our public roadmap outlining planned accessibility improvements. We update this roadmap quarterly and welcome suggestions from our users on what to prioritize.
As a platform built and maintained by a small team, we acknowledge that some accessibility improvements are still in progress. We are transparent about current limitations and are actively working to resolve them:
Our data explorer graphs use canvas-based rendering that has limited screen reader support. We provide alternative data tables where possible and are working on a fully accessible SVG-based rendering engine.
Embedded content from third-party providers (e.g., certain video players, social media embeds) may not fully meet our accessibility standards. We are evaluating more accessible alternatives.
Some earlier podcast episodes lack full transcripts. We are retroactively adding transcripts and aim to complete this by Q2 2026.
Some data-heavy tables on analytics pages may be difficult to parse with screen readers. We are implementing row/column header enhancements and summary descriptions.
Some older PDF documents may not be fully tagged for screen reader accessibility. New PDFs are created with full accessibility tagging. Older documents are being remediated on request.
This website is designed and tested to be compatible with:
Some content on our site may come from third-party sources, including embedded videos, social media feeds, and external document viewers. While we strive to ensure all content meets accessibility standards, we cannot always guarantee the accessibility of externally sourced materials. When we identify third-party content that does not meet our standards, we work with the provider to improve it or provide accessible alternatives.
We welcome your feedback on the accessibility of Prism Writing. If you encounter any accessibility barriers, have suggestions for improvement, or need assistance accessing any part of our site, please contact us. We take all accessibility feedback seriously and will work to address issues promptly.
Email: Ariel@prismwriting.com
Phone: (520) 591-9667
Response Time: We aim to respond to accessibility feedback within 2 business days and resolve identified issues within 15 business days, depending on complexity.
If you are not satisfied with our response to your accessibility concern, you may escalate through the following channels:
This accessibility statement was last reviewed and updated on February 14, 2026. As we continue to develop and improve our platform, we will update this statement to reflect our ongoing accessibility efforts.