Heading Text
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer eget hendrerit metus. Curabitur a diam ultricies, vulputate quam non, aliquet sem.
Voluntary Product Accessibility Template® (VPAT®)
WCAG Edition
Streamline CMS – ICT Accessibility Conformance Report
(WCAG 2.1 / Revised Section 508)
The latest and fully accessible version of this document can be found at getstreamline.com/vpat
Name of Product/Version:
Streamline CMS (SaaS platform – cloud-based content management system)
Report Date:
November 3, 2025
Product Description:
Streamline CMS is a cloud-based website management platform purpose‑built for special districts and local government agencies. It enables non-technical staff to create, publish, and maintain accessible, compliant websites through a curated set of features designed around public transparency, communication, and service delivery.
Contact Information:
Email: accessibility@getstreamline.com
Telephone: (888) 765-1970
Evaluation Methods Used:
Combination of automated testing (axe‑core, WAVE, Lighthouse, Pa11y), manual code review, and assistive‑technology user testing. Independent usability audits are conducted quarterly by certified accessibility consultants, including Shawn Jordison (@theaccessibilityguy), Level Access, Inc. (formal periodic platform review), Carter Temm (screen‑reader expert who previously audited Wells Fargo), Dr. Denise Robinson (@DrDeniseMRobinsontech), and Gena Harper (@GenaBlindWomanOfAction). All conformance claims are based on tests with JAWS 2024, NVDA 2024.2, VoiceOver (macOS/iOS), TalkBack (Android), Dragon NaturallySpeaking, and keyboard‑only navigation on the latest versions of Chrome, Firefox, Safari, and Edge.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
|
Web Content Accessibility Guidelines 2.1
|
Level AA (Yes)
|
|
Revised Section 508 of the U.S. Rehabilitation Act (Jan 2018)
|
Section 508 (Yes)
|
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.1 Report
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.1.1 Non-text Content (Level A)
|
Partially Supports
|
Authors must provide meaningful alternative text for non‑decorative images; a ‘decorative’ option sets an empty alt string. The editor provides guidance and automated checks for missing/placeholder alt and flags complex images that may need longer descriptions. Site administrators can review and override AI suggestions; publication warns on issues and offers remediation steps.
|
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
|
Not Applicable
|
The CMS does not host or render prerecorded audio/video modules. If website administrators wish to add video or audio content to their pages they must utilize a 3rd-party service (e.g. YouTube, Vimeo, etc) which allow them to then embed audio or video content within the page with the appropriate alternative formats enabled (e.g. closed caption, alternative transcript).
|
|
1.2.2 Captions (Prerecorded) (Level A)
|
Not Applicable
|
The CMS does not host or render prerecorded audio/video; only text and images are supported.
|
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
|
Not Applicable
|
The CMS does not host or render prerecorded audio/video; only text and images are supported.
|
|
1.3.1 Info and Relationships (Level A)
|
Partially Supports
|
The CMS output uses semantic HTML for structure: real h1–h6 headings in a logical hierarchy, ul/ol for lists, blockquote for quotes, figure/figcaption for images with captions, and meaningful landmarks (header, nav, main, aside, footer). Tables are data tables with th cells, proper header association via scope or headers/id, and captions when appropriate; no layout tables. Forms have programmatic labels and groupings: label/for or aria-labelledby, fieldset/legend for grouped inputs, error messages associated to fields, and instructions tied to the inputs. Authors can bypass heading hierarchy within the WYSIWYG editor; content guidelines and built-in accessibility checker warn but do not block publication; remediation tooling is planned to require headings in semantic order.
|
|
1.3.2 Meaningful Sequence (Level A)
|
Supports
|
Page templates ensure DOM order matches visual order; keyboard focus follows sequential reading; responsive grid and multi‑column layouts read top‑to‑bottom, left‑to‑right across breakpoints; no CSS ‘order’ used to change meaning.
|
|
1.3.3 Sensory Characteristics (Level A)
|
Supports
|
System copy, help text, and templates use explicit control names; labels are programmatic; visual-only cues are avoided.
|
|
1.4.1 Use of Color (Level A)
|
Supports
|
templates and UI include textual labels, icons, patterns, or outlines in addition to color; links have underlines; screen readers announce state changes.
|
|
1.4.2 Audio Control (Level A)
|
Partially Supports
|
The CMS does not host or render prerecorded audio/video; only text and images are supported. Third‑party embeds may auto‑play without accessible controls; guidance provided, but enforcement is limited.
|
|
2.1.1 Keyboard (Level A)
|
Supports
|
All front‑end features are operable via keyboard (Tab/Shift+Tab, Enter/Space, arrow keys). Non‑pointer alternatives provided for drag‑and‑drop; dialogs and menus open and close via keyboard.
|
|
2.1.2 No Keyboard Trap (Level A)
|
Partially Supports
|
Dialogs, menus, and embeds allow Tab/Shift+Tab navigation; Esc closes and returns focus to the opener; verified with keyboard‑only testing. Some third‑party embeds trap focus; we provide guidance or alternative components and are working to replace them.
|
|
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
|
Not Applicable
|
No single‑key shortcuts are implemented. Other keyboard shortcuts are available and adapt to operating system (e.g. Keyboard Shortcuts for Mac OS, PC) as to not conflict with existing screenreader keyboard shortcuts.
|
|
2.2.1 Timing Adjustable (Level A)
|
Not Applicable
|
No time‑limited tasks or sessions in the end‑user experience; only static content is presented.
|
|
2.2.2 Pause, Stop, Hide (Level A)
|
Supports
|
Auto‑rotating sliders automatically pause on hover and there are keyboard navigable controls to start/stop sliders from progressing.
|
|
2.3.1 Three Flashes or Below Threshold (Level A)
|
Supports
|
No flashing content.
|
|
2.4.1 Bypass Blocks (Level A)
|
Supports
|
Templates include a first‑tab ‘Skip to main content’ link targeting main; ARIA/HTML landmarks are present; heading hierarchy enables quick navigation.
|
|
2.4.2 Page Titled (Level A)
|
Supports
|
Templates set a descriptive HTML title using the page/post title with site branding; unique per page; validated across content types, search, and error pages.
|
|
2.4.3 Focus Order (Level A)
|
Supports
|
Sequential focus follows DOM order.
|
|
2.4.4 Link Purpose (In Context) (Level A)
|
Partially Supports
|
Templates enforce descriptive link text; when generic ‘read more’ is used, additional context is appended to the accessible name (e.g., via aria-describedby or visually hidden text). The WYSIWYG allows generic text, but the app warns against it.
|
|
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
|
Supports
|
All interactive components can be operated with a single pointer via explicit controls; carousels include previous/next buttons.
|
|
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
|
Supports
|
Actions are not triggered until pointer release.
|
|
2.5.3 Label in Name (Level A 2.1 and 2.2)
|
Supports
|
Visible button text (e.g., ‘Publish’) is part of the accessible name via inner text or aria-labelledby; additional context may be appended but not substituted.
|
|
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
|
Not Applicable
|
The CMS does not implement device‑motion interactions; all functionality is available via standard controls.
|
|
3.1.1 Language of Page (Level A)
|
Supports
|
Document language is configurable per page and rendered via
|
|
3.2.1 On Focus (Level A)
|
Supports
|
Keyboard focus does not trigger navigation or submission; components activate on Enter/Space; modals open only on activation and return focus on close.
|
|
3.2.2 On Input (Level A)
|
Supports
|
Inputs do not auto‑submit or navigate on change. Any context changes require explicit user action and prior notice.
|
|
3.3.1 Error Identification (Level A)
|
Supports
|
Field-level errors include explanatory text and are associated via aria-describedby; an error summary appears on submit with links to each field; messages are announced in a polite live region.
|
|
3.3.2 Labels or Instructions (Level A)
|
Supports
|
All inputs have visible labels with programmatic associations; instructions and hints are provided and tied to fields via aria-describedby; required status is indicated with text.
|
|
4.1.1 Parsing (Level A)
|
Supports
|
For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.
|
|
4.1.2 Name, Role, Value (Level A)
|
Supports
|
Native HTML controls are used whenever possible. Custom components expose correct roles, accessible names, states, and values; programmatic updates use accessibility‑supported patterns (e.g., ARIA where necessary) without breaking relationships.
|
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
1.2.4 Captions (Live) (Level AA)
|
Not Applicable
|
Product does not host or render live audio/video; only prerecorded or static content is supported.
|
|
1.2.5 Audio Description (Prerecorded) (Level AA)
|
Not Applicable
|
Product does not host or render live audio/video; only prerecorded or static content is supported.
|
|
1.3.4 Orientation (Level AA 2.1 and 2.2)
|
Supports
|
CMS templates and admin UI are responsive; content and controls reflow in portrait and landscape without functionality loss or forced orientation.
|
|
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
|
Partially Supports
|
CMS templates and built-in form builders automatically add correct autocomplete tokens, labels, and grouping semantics to recognized user‑data fields. Users are permitted to embed third-party forms and widgets, where tokens could potentially be missing. Our CMS flags third-party items and instructs site admins to review them for accessibility. However it has no control over these items or any way to enforce accessible markup within them.
|
|
1.4.3 Contrast (Minimum) (Level AA)
|
Partially Supports
|
Design tokens enforce ≥4.5:1 for body text and ≥3:1 for large text. Interactive states (hover, focus, pressed, disabled) and overlays are tested across themes and breakpoints with axe, CCA, and manual sampling. Third‑party widgets or non‑compliant background images can introduce contrast failures; the accessibility checker flags issues with remediation guidance.
|
|
1.4.4 Resize text (Level AA)
|
Supports
|
CMS Templates and reflow with responsive CSS; Text can be zoomed to 200 % via browser controls without loss of content or functionality.
|
|
1.4.5 Images of Text (Level AA)
|
Supports
|
Templates and UI components render text with HTML/CSS; no text is presented as images. Exceptions apply to logos and brand marks per WCAG. Uploaded artifacts containing text must be accompanied by equivalent HTML text or captions.
|
|
1.4.10 Reflow (Level AA 2.1 and 2.2)
|
Partially Supports
|
Public templates reflow at ≥320 CSS px without two‑directional scrolling; data tables provide single‑axis scrolling within the viewport.
|
|
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
|
Supports
|
All active UI components (buttons, focus indicators, icons) meet 3:1 contrast ratio.
|
|
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
|
Supports
|
Content remains readable and functional when the user overrides spacing to the specified metrics.
|
|
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
|
Supports
|
Menus/popovers open on focus and hover, are hover‑persistent, include Esc/close buttons, trap focus appropriately, and dismiss without moving pointer; verified with keyboard-only navigation.
|
|
2.4.5 Multiple Ways (Level AA)
|
Supports
|
Templates provide site search, consistent global navigation. Interior pages have the option to include a side-navigation zone for additional context.
|
|
2.4.6 Headings and Labels (Level AA)
|
Partially Supports
|
The CMS output uses semantic HTML for structure: real h1–h6 headings in a logical hierarchy. Authors can bypass heading hierarchy within the WYSIWYG editor; content guidelines and built-in accessibility checker warn but do not block publication; remediation tooling is planned to require headings in semantic order.
|
|
2.4.7 Focus Visible (Level AA)
|
Supports
|
A clear, consistent focus indicator is rendered across components and remains visible in all states and themes.
|
|
3.1.2 Language of Parts (Level AA)
|
Partially Supports
|
There aren’t default controls to insert lang tags using the WYSIWYG editor. Inline lang tags can be inserted for translated phrases or mixed‑language passages via our HTML embed tools.
|
|
3.2.3 Consistent Navigation (Level AA)
|
Supports
|
Global header, primary navigation, search, breadcrumbs, and footer appear in a consistent position and order across templates and breakpoints; labels are uniform.
|
|
3.2.4 Consistent Identification (Level AA)
|
Supports
|
Reusable components keep uniform labels, icons, roles, and behaviors across templates; accessible names match visible labels.
|
|
3.3.3 Error Suggestion (Level AA)
|
Supports
|
Error messages provide clear suggestions for correction.
|
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
|
Supports
|
Deleting files, images, videos and other high impact assets requires confirmation before the item is removed.
|
|
4.1.3 Status Messages (AA) (Level AA)
|
Supports
|
Inline success, error, and validation messages are exposed with role=‘status’ or appropriate aria‑live semantics; they are perceivable without moving focus and announced in screen readers.
|
Table 3: Revised Section 508 (2018) Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
302.1 Without Vision
|
Supports
|
Pages are fully operable with screen readers: semantic landmarks and headings support navigation; controls have accessible names; errors and status messages are programmatically associated and announced.
|
|
302.2 With Limited Vision
|
Supports
|
Reflow, zoom, and high‑contrast modes supported.
|
|
302.3 Without Perception of Color
|
Supports
|
No information conveyed solely through color.
|
|
302.4 Without Hearing
|
Supports
|
The CMS does not host or render prerecorded audio/video. If website administrators wish to add video or audio content to their pages they must utilize a 3rd-party service (e.g. YouTube, Vimeo, etc) which allow them to then embed audio or video content within the page with the appropriate alternative formats enabled (e.g. closed caption, alternative transcript).
|
|
302.5 With Limited Hearing
|
Supports
|
Same as above
|
|
302.6 Without Speech
|
Supports
|
Speech not required
|
|
302.7 With Limited Manipulation
|
Supports
|
Keyboard operable; large clickable targets; no drag‑and‑drop required.
|
|
302.8 With Limited Reach and Strength
|
Supports
|
No time‑dependent, rapid gestures.
|
|
302.9 With Limited Language, Cognitive, and Learning Abilities
|
Supports
|
UI uses plain language; navigation is consistent; content is organized with headings and TOCs; forms provide instructions, inline validation, and autosave; confirmations prevent accidental changes; search tolerates misspellings.
|
Table 4: Support Documentation and Services (Chapter 6)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
|
602.2 Accessibility and Compatibility Features
|
Supports
|
Public documentation and FAQs describe screen‑reader, keyboard, and language features.
|
|
602.3 Electronic Support Documentation
|
Supports
|
Documentation is provided in HTML and Video. HTML versions meet WCAG 2.1 AA. Support video includes closed captions
|
|
602.4 Alternate Formats for Non-Electronic Support Documentation
|
Supports
|
Documentation can be supplied in accessible Word, Braille, or large‑print upon request.
|
|
603.2 Information on Accessibility and Compatibility Features
|
Supports
|
Dedicated accessibility contact (accessibility@getstreamline.com) and phone line; VPAT publicly available.
|
|
603.3 Accommodation of Communication Needs
|
Supports
|
We provide support via accessible email, chat, phone. Users may request support via Aira live interpreters or Relay services. Our support portal meets WCAG 2.1 AA; accommodation requests are honored and documented.
|
Legal Disclaimer
This report represents the good‑faith assessment of Streamline CMS as of the report date. Conformance applies to CMS‑provided templates and components. Embedded third‑party widgets/media are the publisher’s responsibility; the CMS offers guidance, checks, or approved alternatives. Accessibility is an ongoing effort; we welcome feedback and will address new issues as they are identified.