CampbellON Accessibility Conformance Report
WCAG Edition · Based on VPAT® Version 2.5Rev
Online version: campbellon.com/accessibility
Product information
- Name of Product/Version
- CampbellON web application (continuously delivered). This report reflects the release evaluated in September 2026.
- Report Date
- September 2026
- Product Description
- CampbellON is Campbell Scientific's cloud platform for programming, monitoring and visualizing environmental monitoring networks. Customers use it in a web browser to manage stations, dataloggers and sensors, view and explore measurement data, build dashboards, configure alerts and data exports, and administer their organization's users and subscriptions.
- Contact Information
- Campbell Scientific, Inc., 815 West 1800 North, Logan, Utah 84321-1784, USA. To report an accessibility problem or ask a question about this report, contact Campbell Scientific.
Notes
This report covers the CampbellON web application: the signed-in application (every module available to customer organizations), the sign-in, registration and password-reset pages, dashboards shared through public links, and the in-app Help Center.
It does not cover Campbell Scientific dataloggers, sensors and their on-device interfaces; desktop software such as LoggerNet; the CampbellON marketing website and API reference; email notifications; internal tools used only by Campbell Scientific staff; content that customers create, such as dashboard titles, uploaded images and station names; or features that are not yet generally available to customers.
CampbellON is updated continuously. Campbell Scientific tracks the issues described in this report for remediation and will update the report as the product changes.
Summary across the 56 Level A and AA success criteria in this report:
- 25 Supports
- 24 Partially Supports
- 7 Not Applicable
Evaluation Methods Used
Campbell Scientific evaluated CampbellON against WCAG 2.2 Levels A and AA in September 2026. The evaluation combined the following methods:
- Automated testing with axe-core 4.13 (WCAG 2.0, 2.1 and 2.2 Level A and AA rules) in desktop Chromium on 57 application screens, 19 dialogs and 4 sign-in pages (sign in, password reset, registration and authenticator app setup).
- Scripted keyboard testing on the same screens: Tab order, a visible focus indicator at each stop, focused elements hidden by other content, keyboard traps, and closing dialogs with the Escape key.
- Reflow testing at a viewport 320 CSS pixels wide, equivalent to 400% zoom.
- Contrast measurement of text and interface colors in the light and dark themes, including labels drawn inside charts.
- A review of the application’s source code (page templates, styles and interaction logic) against every success criterion, including the shared-dashboard viewer and the sign-in pages. Each finding was checked a second time by an independent reviewer who tried to disprove it.
Testing with screen readers (such as NVDA, JAWS, VoiceOver and TalkBack) and on mobile devices has not yet been performed. Where a result depends on how assistive technology announces content, the remark is based on the code and the automated results.
After the original evaluation, the findings were re-checked in September 2026 against the release that includes the latest accessibility fixes. Each criterion proposed to move to Supports was checked again by a second reviewer who tried to disprove it, and the text spacing test for success criterion 1.4.12 was run in the browser at desktop and phone widths. The other automated scans and scripted keyboard tests described above were run during the original evaluation and were not repeated.
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 (No) |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
| Web Content Accessibility Guidelines 2.2 | Level A (Yes) · Level AA (Yes) · Level AAA (No) |
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.x Conformance Requirements.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports |
Images, icons and charts generally have text alternatives or text summaries. Dashboard image widgets have no field for alternative text: an image is described only by its widget title, and an image in an untitled widget is hidden from screen readers as decorative, so authors should give informative images a descriptive title. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable |
The product contains no prerecorded audio-only or video-only content. |
| 1.2.2 Captions (Prerecorded) | Not Applicable |
The product contains no prerecorded video with audio. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable |
The product contains no prerecorded video. |
| 1.3.1 Info and Relationships | Partially Supports |
Pages use headings, landmarks, lists, labeled form fields and marked-up data tables. Some visible hints are not programmatically tied to their switches or checkboxes, in single sign-on, alert configuration, two-step verification and station device settings, and some group headings in the notifications filter menu are not tied to their checkboxes. |
| 1.3.2 Meaningful Sequence | Supports |
Reading order matches the visual order, including dashboard widgets in every layout. |
| 1.3.3 Sensory Characteristics | Partially Supports |
Most instructions identify controls by name or function. A few dashboard editor hints and Help Center instructions refer to controls only by shape, such as arrow or pencil buttons. |
| 1.4.1 Use of Color | Partially Supports |
Most status information uses text or icons as well as color, and links are underlined. Color alone distinguishes station communication status on the station map, active versus snoozed alert badges, live-data and narrow-screen status dots, and chart series lines, although table views, text details and a color-blind safe palette are available. |
| 1.4.2 Audio Control | Not Applicable |
The product does not play any audio. |
| 2.1.1 Keyboard | Partially Supports |
Most functionality works from the keyboard, including navigation, forms, tables, maps and dashboard layout. Some functions need a pointer: chart widget values and legend toggles, drag reordering in several lists, some file browse and chip remove buttons, controls inside grid-view cards, links inside table cells, the scope editor in the dashboard Dynamic filters dialog, panel resizing and hover-only details. Alternatives such as Data Explorer and table views cover most of these. |
| 2.1.2 No Keyboard Trap | Supports |
Keyboard focus is never trapped, and the code editor provides a documented shortcut for moving focus out. |
| 2.1.4 Character Key Shortcuts | Supports |
There are no single-key shortcuts; shortcuts use a modifier key or work only while their control has focus. |
| 2.2.1 Timing Adjustable | Partially Supports |
Idle users are warned two minutes before sign-out and can extend the session as often as needed. Some limits cannot be extended: sessions end after 10 hours (some areas require signing in again after 8), registration and sign-in pages expire after 30 minutes, and password and authenticator setup steps and email verification or reset links expire after 5 minutes. |
| 2.2.2 Pause, Stop, Hide | Partially Supports |
A pause control stops live updates and moving content on station pages, dashboards, Data Explorer and the Alerts page. Two small text timers keep updating while paused: alert durations in the triggered alerts card view and "last updated" times on favorite measurement cards. |
| 2.3.1 Three Flashes or Below Threshold | Supports |
No content flashes more than three times in any one-second period. |
| 2.4.1 Bypass Blocks | Supports |
Pages provide skip links, landmarks and headings for bypassing repeated content. |
| 2.4.2 Page Titled | Supports |
All pages have descriptive titles. |
| 2.4.3 Focus Order | Partially Supports |
Focus order generally follows the layout, and dialogs and panels manage focus correctly. When an item is removed with its own button, focus is often lost to the top of the page or out of the dialog. A few pop-up panels come at the end of the Tab order, and one scope editor cannot be reached by keyboard. |
| 2.4.4 Link Purpose (In Context) | Supports |
Link purpose is clear from the link text or its surrounding context. |
| 2.5.1 Pointer Gestures | Supports |
No function requires multipoint or path-based gestures. |
| 2.5.2 Pointer Cancellation | Supports |
Actions complete on pointer release, and drag operations can be abandoned. |
| 2.5.3 Label in Name | Partially Supports |
Accessible names generally match or contain the visible labels. The station network chip and multi-value dashboard filter chips show a count that their names leave out, although each name starts with the visible network or filter name. |
| 2.5.4 Motion Actuation | Not Applicable |
The product has no functions operated by device motion or user motion. |
| 3.1.1 Language of Page | Supports |
Every page identifies its default language as English. |
| 3.2.1 On Focus | Supports |
Receiving focus never changes context. |
| 3.2.2 On Input | Supports |
Changing a setting or field never changes context unexpectedly. |
| 3.2.6 Consistent Help | Supports |
The Help button, with support options, is in the same place on every page. |
| 3.3.1 Error Identification | Partially Supports |
Fields that fail validation are marked and described in text. When the server rejects a value, many edit dialogs show only a general error that does not identify the problem. |
| 3.3.2 Labels or Instructions | Partially Supports |
Form fields have visible labels, and required fields and formats are explained. Name fields edited in place from a page title have no visible label or required marker, and countdown widget date and time fields do not state the expected format. |
| 3.3.7 Redundant Entry | Partially Supports |
Multi-step flows keep entered information between steps, and most offer a way back to correct details after a failed save. Create Organization, Add security group, Add distribution group and partial saves in Add station and Add asset offer only Retry, so changing an entry means starting again. |
| 4.1.1 Parsing | Supports |
WCAG 2.2 removed this criterion, which is always satisfied for HTML content. |
| 4.1.2 Name, Role, Value | Partially Supports |
Most controls expose correct names, roles and states. The station link in the Alert history table is not exposed as a link and cannot be reached by keyboard, and one multi-select filter list in the Add measurements dialog is announced as single-select. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable |
The product contains no live audio or video content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable |
The product contains no prerecorded video. |
| 1.3.4 Orientation | Supports |
Content is not restricted to portrait or landscape orientation. |
| 1.3.5 Identify Input Purpose | Supports |
Fields that collect the user's own information identify their purpose for autofill. |
| 1.4.3 Contrast (Minimum) | Partially Supports |
Most text meets the 4.5:1 contrast ratio in both light and dark themes. A few small items fall short, including tooltip notes and loading text in some dashboard widgets, dark-theme chart labels on the Plan usage page, and a character counter in File Manager. |
| 1.4.4 Resize Text | Partially Supports |
Text can be enlarged to 200% throughout the product. At 200% zoom on a typical laptop, dashboards become view-only because editing requires a window at least about 905 CSS pixels wide. |
| 1.4.5 Images of Text | Supports |
Interface text is real text; only logos and product photos contain images of text. |
| 1.4.10 Reflow | Partially Supports |
Pages, side panels and dialogs reflow to 320 CSS pixels without horizontal scrolling. Dashboard editing is unavailable below about 905 CSS pixels wide, where dashboards are shown read-only. |
| 1.4.11 Non-text Contrast | Partially Supports |
Most form controls, focus indicators, icons and chart colors meet the 3:1 contrast ratio. Threshold and event lines on the alert event chart fall below 3:1, and some selected-state buttons in chart settings and the Data Explorer series panel show selection only with a faint fill. |
| 1.4.12 Text Spacing | Partially Supports |
The text-spacing test was run at desktop and phone widths, and most text containers grow to fit. Where text in tables and some titles is shortened, the full text appears in a tooltip that needs a mouse, and some shortened labels in tables, cards and dashboard controls have no tooltip at all. |
| 1.4.13 Content on Hover or Focus | Partially Supports |
Tooltips and hover content stay visible while hovered, can be dismissed with Escape and do not time out. On the Data Explorer map, the station name label disappears when hovered, cannot be dismissed with Escape and can cover nearby markers. |
| 2.4.5 Multiple Ways | Supports |
Pages can be reached through navigation menus, a sitemap, searchable lists and links. |
| 2.4.6 Headings and Labels | Supports |
Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible | Partially Supports |
Interactive elements show a visible focus indicator. Three search boxes inside pop-up panels, in the measurements menu, the alert condition builder and the dynamic filter value picker, show only the text cursor when focused. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports |
Focused items are not hidden by sticky headers, banners or panels. |
| 2.5.7 Dragging Movements | Partially Supports |
Many drag actions have single-pointer alternatives. Dragging is the only pointer method for moving and resizing dashboard widgets, several reorder lists, positioning the photo crop area, resizing the File Manager details panel and reordering table columns, although widgets and the crop area can also be moved with arrow keys. |
| 2.5.8 Target Size (Minimum) | Partially Supports |
Most controls are at least 24 by 24 CSS pixels or have enough spacing. Column resize grips in list tables and widget resize edges in the dashboard editor are smaller and have no larger pointer alternative. |
| 3.1.2 Language of Parts | Supports |
All content is in English, apart from exempt proper names and technical terms. |
| 3.2.3 Consistent Navigation | Supports |
Navigation menus appear in the same place and order on every page. |
| 3.2.4 Consistent Identification | Supports |
Components with the same function are identified consistently. |
| 3.3.3 Error Suggestion | Partially Supports |
Most error messages explain how to correct the input. A few show a technical pattern instead of guidance, and server-rejected input gets a general message whose contact support link does not open a support page. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports |
Deletions and purchases require confirmation or review before they take effect. |
| 3.3.8 Accessible Authentication (Minimum) | Supports |
Sign-in supports password managers, paste, passkeys and single sign-on, with no cognitive tests. |
| 4.1.3 Status Messages | Partially Supports |
Most status messages, including list result counts and errors, are announced without moving focus. Some searches and filters in list filter panels, the Add station and Add asset flow, station and asset pages, the notifications panel and the dashboard editor do not announce their "no matches" message. |
Table 3: Success Criteria, Level AAA
Notes: Level AAA success criteria were not evaluated for this report.
Legal Disclaimer (Campbell Scientific, Inc.)
This report is provided for information only. It describes the accessibility of CampbellON as evaluated on the report date and may not reflect later changes to the product. It does not create any warranty, express or implied, or any contractual obligation. Campbell Scientific continues to improve the accessibility of CampbellON and may update this report at any time.