Brightspot CMS Accessibility Conformance Report
WCAG Edition (Based on VPAT® Version 2.5Rev)
Name of Product/Version: Brightspot CMS / Version 5.0
Report Date: January 2026
Product Description: Brightspot CMS is an enterprise-level Content Management System designed for organizations to create, manage, and deliver digital experiences across multiple channels.
Contact Information: info@brightspot.com
Notes
Evaluation Methods Used: Testing was performed by testers with knowledge of general product functionality.
The following applications were used to evaluate this product:
- Desktop Browsers: Chrome, Firefox, Safari
- Accessibility testing tools: Browser developer tools
"Voluntary Product Accessibility Template" and "VPAT" are registered service marks of the Information Technology Industry Council (ITI)
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.0 | |
| Level A | Yes |
| Level AA | Yes |
| Level AAA | Yes |
| Web Content Accessibility Guidelines 2.1 | |
| Level A | Yes |
| Level AA | Yes |
| Level AAA | Yes |
| Web Content Accessibility Guidelines 2.2 | |
| Level A | Yes |
| Level AA | Yes |
| Level AAA | 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.x Report
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Supports | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only or video-only media. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | Brightspot CMS does not contain any prerecorded media that requires captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | Brightspot CMS does not contain any prerecorded video media that requires audio descriptions or a media alternative. |
| 1.3.1 Info and Relationships (Level A) | Supports | All visual information, structure, and relationships are also accessible as text or programmatically discoverable in Brightspot CMS. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | A correct reading order, where the sequence of presentation affects the content's meaning, is programmatically determinable within the Brightspot CMS. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | Brightspot CMS does not contain any instructions that rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. |
| 1.4.1 Use of Color (Level A) | Supports | Brightspot CMS does not rely on color as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| 1.4.2 Audio Control (Level A) | Not Applicable | Brightspot CMS does not contain any audio media that plays automatically for more than 3 seconds. |
| 2.1.1 Keyboard (Level A) | Supports | Brightspot CMS is fully operable using only a keyboard interface. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Brightspot CMS allows users to move focus away from any component using only a keyboard interface. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) | Supports | The Brightspot CMS includes a single-character keyboard shortcut, "/", to open the search function. Users are provided with a profile setting that allows them to disable this shortcut if desired. |
| 2.2.1 Timing Adjustable (Level A) | Supports | Brightspot CMS includes an interface with time limits, Content Locking, which offers users ways to extend the session timeout. Specifically, the feature warns an idle user when the configured time limit is approaching and provides an option to extend the timeout. The default timeout duration for this feature can also be adjusted on the settings page. |
| 2.2.2 Pause, Stop, Hide (Level A) | Supports | Brightspot CMS generally avoids content that moves, blinks, or scrolls automatically. For the few elements that do update in real-time (such as feeds for recent activity, conversations, and live blogs), a user profile setting is available to disable these automatic updates. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | Brightspot CMS does not contain anything that flashes more than three times in any one second period. |
| 2.4.1 Bypass Blocks (Level A) | Supports | Brightspot CMS provides skip links for users to navigate directly to specific regions of a page. In version 5.0 users are able to navigate between regions using key shortcuts (Alt+Tab for Mac and F6 for Windows). |
| 2.4.2 Page Titled (Level A) | Supports | The page titles within Brightspot CMS align with the corresponding section name, such as "Sites & Settings." |
| 2.4.3 Focus Order (Level A) | Supports | The focus order of components within the Brightspot CMS is logical and consistent, ensuring that users can interact with the system in a meaningful and operable way. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | The purpose of every link within Brightspot CMS is discernible from the link text alone or when considered alongside its programmatically determined context. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) | Supports | Brightspot CMS does not have any functionality that uses multipoint or requires path-based gestures. Slide controls used for zoom and weighted lists can be adjusted with a single click and do not require users to drag in a straight line. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) | Supports | In Brightspot CMS, most actions are initiated on the "up-event." Drag and drop operations can be canceled in two ways: by dragging the item outside of a valid target area or by returning it to its starting location. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) | Supports | Accessible names may include additional descriptive text but always contain any visible text for buttons in Brightspot CMS. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) | Supports | Brightspot CMS does not utilize either device or user motion as a trigger for any of its functionalities. |
| 3.1.1 Language of Page (Level A) | Supports | The language of pages can be identified by the lang attribute on the html element in Brightspot CMS. |
| 3.2.1 On Focus (Level A) | Supports | Brightspot CMS does not have any elements that change a user's context on focus. |
| 3.2.2 On Input (Level A) | Supports | Brightspot CMS does not have any elements that change a user's context on input. Change of content may occur in some cases but these changes are described and predictable (ex. Show Named Revisions will change the content in Version History). |
| 3.2.6 Consistent Help (Level A 2.2 only) | Supports | The Brightspot CMS offers self-help support through "Guides," which are consistently located throughout the interface. Users can access full-page guides via the left navigation toolbar, while field-level guides are always positioned directly after the corresponding field label. |
| 3.3.1 Error Identification (Level A) | Supports | Brightspot CMS notifies users of errors through multiple methods: a general message displayed at the top of the page, visual indicators on the tabs containing errors, and specific, descriptive messages next to the fields where the errors are located. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Brightspot CMS provides labels and/or instructions whenever content requires user input. |
| 3.3.7 Redundant Entry (Level A 2.2 only) | Supports | Brightspot CMS generally prevents users from having to re-enter previously input information within the same process. Exception: Re-entry is only required for security purposes when a user sets a new password, necessitating a confirmation field. This falls under the acceptable exception: "the information is required to ensure the security of the content." |
| 4.1.1 Parsing (Level A) WCAG 2.0 and 2.1 – Always answer 'Supports' WCAG 2.2 (obsolete and removed) - Does not apply | 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 | Brightspot CMS provides the correct name, role, and value for all user interface components. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | Brightspot CMS does not contain any live media that requires captions. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | Brightspot CMS does not contain any prerecorded media that requires audio descriptions. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) | Supports | Brightspot CMS does not restrict the view or operation of any function to a single orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) | Supports | Brightspot CMS identifies the purpose of each input when possible, but most inputs are generic or specific for an implementation. |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | Brightspot CMS is designed with sufficient contrast for all default text. However, end-users retain the capability to customize certain colors, which could potentially result in insufficient contrast. |
| 1.4.4 Resize text (Level AA) | Supports | Brightspot CMS can still be operated without loss of content or functionality when text is resized up to 200%. |
| 1.4.5 Images of Text (Level AA) | Supports | The Brightspot CMS avoids using images of text. The only exception is for Logotypes, which are considered essential and acceptable based on the success criterion. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) | Supports | The Brightspot CMS interface maintains its functionality and information integrity when viewed at a width of 320 pixels or a height of 256 pixels, in most cases. Exception: Interfaces that rely on a two-dimensional layout for meaning or use (such as table-based layouts) are an acceptable exception to this success criterion. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) | Supports | By default, Brightspot CMS offers adequate contrast for most of its user interface components. Furthermore, users can activate a "High" Contrast setting within their profile, which guarantees sufficient contrast for all controls. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) | Supports | In Brightspot CMS, there is no loss of content or functionality when the following text spacing properties are adjusted, provided no other style properties are changed: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) | Supports | In Brightspot CMS, content that is revealed on hover or focus is designed to be persistent and accessible. Specifically, this additional content will not hide other essential content and can be interacted with (hoverable). |
| 2.4.5 Multiple Ways (Level AA) | Supports | Brightspot CMS provides multiple ways of locating and navigating to pages. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Brightspot CMS has clear and descriptive headings and labels when provided. |
| 2.4.7 Focus Visible (Level AA) | Supports | Brightspot CMS displays a visible border around any user interface control that receives focus. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) | Supports | All user interface components in the Brightspot CMS are visible when they receive keyboard focus. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) | Partially supports | Brightspot CMS provides a single pointer interaction for moving elements inside of rich text fields, sliders, and adjusting weighted lists. It does not currently provide a single pointer alternative for drag and drop interfaces. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) | Supports | Brightspot CMS provides a minimum target size of 24 by 24 pixels for all pointer inputs. |
| 3.1.2 Language of Parts (Level AA) | Supports | The language of parts can be identified by the lang attribute on the html element in Brightspot CMS. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Brightspot CMS displays navigational mechanisms in a consistent order and structure across pages. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Brightspot CMS displays components with the same functionality consistently throughout the interface. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Brightspot CMS provides suggestions and direction for the correction of errors when known. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | Brightspot CMS does not have any functionality that causes legal commitments or financial transactions. The CMS provides error checking for all inputs that modify or delete user-controllable data. All changes are reversible, with the exception of permanent record deletion, which requires confirmation via a system dialog before proceeding. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) | Supports | Brightspot CMS provides alternate authentication methods utilizing SAML to enable single sign-on options and OAuth for third-party login. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) | Supports | Brightspot CMS uses aria-live regions to announce status messages. |
Table 3: Success Criteria, Level AAA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.6 Sign Language (Prerecorded) (Level AAA) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only media. |
| 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only or video-only media. |
| 1.2.8 Media Alternative (Prerecorded) (Level AAA) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only or video-only media. |
| 1.2.9 Audio-only (Live) (Level AAA) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only media. |
| 1.3.6 Identify Purpose (Level AAA 2.1 and 2.2) | Supports | Brightspot CMS indicates the purpose of icons, regions, and components and uses ARIA landmarks to identify regions of a page. |
| 1.4.6 Contrast (Enhanced) (Level AAA) | Does Not Support | Brightspot CMS does not provide any mode where contrast ratio is at least 7:1. |
| 1.4.7 Low or No Background Audio (Level AAA) | Not Applicable | Brightspot CMS does not contain any prerecorded audio-only media. |
| 1.4.8 Visual Presentation (Level AAA) | Does Not Support | Brightspot CMS does not provide the necessary mechanisms to users in order to fulfill this criteria. |
| 1.4.9 Images of Text (No Exception) (Level AAA) | Supports | Brightspot CMS only uses images of text for Logotypes which are considered essential and an acceptable exemption. |
| 2.1.3 Keyboard (No Exception) (Level AAA) | Supports | Brightspot CMS provides a method to perform all functions within the CMS using only the keyboard. |
| 2.2.3 No Timing (Level AAA) | Supports | The Content Locking interface in Brightspot CMS, which is the sole interface that features a time-out mechanism can be turned off within Sites & Settings. |
| 2.2.4 Interruptions (Level AAA) | Does Not Support | Brightspot CMS does not currently provide a way for individual users to disable updates and alerts. |
| 2.2.5 Re-authenticating (Level AAA) | Supports | Brightspot CMS automatically saves work in progress for users to prevent loss of data if an authenticated session expires and will redirect to the work in progress once the user has re-authenticated. |
| 2.2.6 Timeouts (Level AAA 2.1 and 2.2) | Supports | The Content Locking interface in Brightspot CMS, which is the sole interface that features a time-out mechanism will alert users if their lock is expiring due to inactivity. |
| 2.3.2 Three Flashes (Level AAA) | Supports | Brightspot CMS does not contain anything that flashes more than three times in any one second period. |
| 2.3.3 Animation from Interactions (Level AAA 2.1 and 2.2) | Does Not Support | Brightspot CMS does not currently provide a way for individual users to disable animations. |
| 2.4.8 Location (Level AAA) | Supports | Brightspot CMS provides a way for the user to orient themselves within a set of pages by indicating their current location within navigation bars. |
| 2.4.9 Link Purpose (Link Only) (Level AAA) | Supports | Brightspot CMS ensures that the purpose of every link is identifiable. This is achieved through mechanisms like descriptive link text, the combination of text and iconic representations, and the use of aria-labels to convey the link's purpose even when the text is not visually present. |
| 2.4.10 Section Headings (Level AAA) | Supports | Brightspot CMS uses section headings to organize content. |
| 2.4.12 Focus Not Obscured (Enhanced) (Level AAA 2.2 only) | Does Not Support | Brightspot CMS does not obscure focus in most cases. An exception was found in longer settings pages where it was possible to focus below the fold before the scroll catches up. Scroll-padding will be added to address this. |
| 2.4.13 Focus Appearance (Level AAA 2.2 only) | Does Not Support | Brightspot CMS does not currently provide sufficient contrast for the focus indicator. |
| 2.5.5 Target Size (Level AAA 2.1 and 2.2) | Does Not Support | Brightspot CMS does not provide a target area that is at least 44 by 44 pixels for all controls. |
| 2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 and 2.2) | Supports | Brightspot CMS does not restrict the use of input modalities available on any platform. |
| 3.1.3 Unusual Words (Level AAA) | Does Not Support | Brightspot CMS does not provide a mechanism for identifying specific definitions of words or phrases. |
| 3.1.4 Abbreviations (Level AAA) | Does Not Support | Brightspot CMS does not provide a mechanism for identifying the expanded form or meaning of abbreviations. |
| 3.1.5 Reading Level (Level AAA) | Does Not Support | Brightspot CMS does not provide the necessary mechanisms to users in order to fulfill this criteria. |
| 3.1.6 Pronunciation (Level AAA) | Does Not Support | Brightspot CMS does not provide a mechanism for identifying specific pronunciation of words. |
| 3.2.5 Change on Request (Level AAA) | Supports | Changes of context are initiated only by user request in Brightspot CMS. |
| 3.3.5 Help (Level AAA) | Supports | Brightspot CMS provides context-sensitive help through page-level and field-level guides. |
| 3.3.6 Error Prevention (All) (Level AAA) | Supports | Brightspot CMS provides error checking for all inputs and all submissions are reversible. |
| 3.3.9 Accessible Authentication (Enhanced) (Level AAA 2.2 only) | Supports | Brightspot CMS provides alternate authentication methods utilizing SAML to enable single sign-on options and OAuth for third-party login. |
Legal Disclaimer (Brightspot)
© 2025 Perfect Sense, DBA Brightspot. As of the date of publication indicated above, this report represents the current view of Brightspot regarding information about the Brightspot® platform relating to information outlined in the ITI's "VPAT® 2.4 Revised Section 508 Standards". Brightspot cannot guarantee that any information in this Conformance Report will remain accurate after date of publication, but works continuously to monitor the accessibility of the product. Any modification or customization to the Brightspot platform may render some or all of this Conformance Report to become inapplicable. This report is provided "as is" and for informational purposes only.