CXT Software Client Portal - Voluntary Product Accessibility Report (VPAT)

Product name/version: CXT Software Client Portal (Web Application), version: 24.8.6.0 (tested August 2025)

Report date: August 2025

Product description:

The CXT Software Client Portal is a web‑based application that allows logistics customers to place orders, track parcels, generate reports and manage account information. The portal provides a left‑hand navigation menu and various order creation forms. The login workflow requires a username and password to access the portal. This evaluation focuses on the authenticated customer interface, the primary “Place Order” page, administrative sections, as well as the publicly available knowledge‑base (“CXT Support”) used for support documentation.

Contact information:

For questions regarding this report, please contact CXT Software’s product team at product@cxtsoftware.com. This report was prepared for CXT Software.

Evaluation methods used:

Manual inspection of the Client Portal and the CXT Support knowledge‑base was carried out using the Chromium browser in August 2025. Testing included keyboard navigation (Tab/Shift+Tab), visual examination of color contrast, and review of form controls, link labels, and page structure. The portal and documentation were assessed against applicable WCAG 2.0 Level A and Level AA success criteria and the corresponding Revised Section 508 provisions (501 Web/Software, 504.2 Authoring Tools and 602.3 Support Documentation). Automated accessibility tools (such as Lighthouse or pa11y) could not be executed due to environment restrictions; therefore, some criteria remain unevaluated.

Applicable standards/guidelines:

Standards/Guidelines	Included in this report (yes/no)
Web Content Accessibility Guidelines (WCAG) 2.0 – Levels A and AA	Yes
Revised Section 508 – 501 (Web/Software)	Yes
Revised Section 508 – 504.2 (Authoring Tools)	No (not applicable)
Revised Section 508 – 602.3 (Support Documentation)	Yes
EN 301 549 Accessibility requirements	No
WCAG 2.0 Level AAA	No

Conformance terminology:

· Supports – The functionality of the product/document has at least one method that meets the criterion without known defects or meets it with equivalent facilitation.

· Partially Supports – Some functionality does not meet the criterion.

· Does Not Support – The majority of functionality does not meet the criterion.

· Not Applicable (N/A) – The criterion is not relevant to the product/document category.

· Not Evaluated (NE) – The product/document has not been evaluated against the criterion.

WCAG 2.0 and Revised Section 508 Report

For each WCAG 2.0 success criterion below, conformance is reported separately for the following categories:

· 501 Web/Software: The interactive client portal (customer interface).

· 504.2 Authoring Tools: Authoring or content‑creation functionality. The portal does not include authoring tools; therefore all entries for this category are marked N/A.

· 602.3 Support Documentation: The CXT Support knowledge‑base (Knowledge Base ) provided by the user. Where possible, basic accessibility observations were made.

Level A Criteria

Success Criterion	Category	Conformance Level	Remarks and explanations
1.1.1 Non‑text Content (A)[1]	501 Web/Software	Partially Supports	The portal includes meaningful images and icons (e.g., a large customizable graphic and Google/GPS/barcode icons) without apparent alternative text or accessible names. Decorative images should have empty alt attributes; meaningful images must have descriptive alt or aria-label values[1].
	504.2 Authoring Tools	N/A	No authoring functionality.
	602.3 Support Docs	Partially Supports	The CXT Support site uses Confluence, which provides structural semantics; however, logos and some icons may not have explicit alt text.
1.2.1 Audio‑only and Video‑only (Prerecorded)	501	N/A	No prerecorded audio or video content in the portal.
	504.2	N/A
	602.3	N/A	No standalone audio or video on the support site.
1.2.2 Captions (Prerecorded)	501	N/A	No prerecorded multimedia in the portal.
	504.2	N/A
	602.3	N/A
1.2.3 Audio Description or Media Alternative (Prerecorded)	501	N/A	No multimedia content.
	504.2	N/A
	602.3	N/A
1.3.1 Info and Relationships	501	Partially Supports	Most form fields are labeled (e.g., Username, Password), but some rely on placeholder text (e.g., “Enter a location”). Placeholder text disappears once users type and is not programmatically associated with the input[2].
	504.2	N/A
	602.3	Supports	The support documentation uses proper headings, lists and tables in Confluence. Labels for navigation and search fields are present.
1.3.2 Meaningful Sequence	501	Supports	The reading order generally follows the visual order[3].
	504.2	N/A
	602.3	Supports	Content on the support site is presented in a logical sequence; headings and sections are logically ordered.
1.3.3 Sensory Characteristics	501	Supports	Instructions do not rely solely on color, shape or sound[4].
	504.2	N/A
	602.3	Supports	Support articles avoid referring only to color or shape.
1.4.1 Use of Color	501	Partially Supports	Notification banners use color (orange, teal, blue) with minimal accompanying text. Users who cannot perceive color may not understand the significance[5].
	504.2	N/A
	602.3	Supports	The support site uses high‑contrast blue links on a white background; color is not the sole means of conveying information.
1.4.2 Audio Control	501	N/A	No audio that starts automatically.
	504.2	N/A
	602.3	N/A
2.1.1 Keyboard[6]	501	Partially Supports	Navigation and form entry are possible via keyboard, but several controls (close buttons on banners, kebab menu, icons in address selectors) are not focusable. The focus indicator is weak. All functionality should be operable via keyboard without requiring specific timing[6].
	504.2	N/A
	602.3	Supports	The support site’s navigation and search fields are keyboard accessible; focus styles are visible and menus can be navigated using the keyboard.
2.1.2 No Keyboard Trap	501	Supports	Users can move focus away from components using standard keys[7].
	504.2	N/A
	602.3	Supports	No keyboard traps observed in the support site.
2.2.1 Timing Adjustable	501	N/A	There are no time‑limited tasks.
	504.2	N/A
	602.3	N/A
2.2.2 Pause, Stop, Hide	501	Supports	Notification banners can be dismissed (though “Close” links should be accessible via keyboard)[8].
	504.2	N/A
	602.3	Supports	No moving or auto‑updating content on the support site.
2.3.1 Three Flashes or Below Threshold	501	N/A	No flashing content.
	504.2	N/A
	602.3	N/A
2.4.1 Bypass Blocks	501	Does Not Support	There is no “Skip to main content” link or landmark navigation to bypass the left‑hand menu[9].
	504.2	N/A
	602.3	Partially Supports	The support site does not display an explicit “skip to content” link; however, the page structure allows users to tab to the main content after the top navigation.
2.4.2 Page Titled	501	Supports	Pages have descriptive <title> values[10].
	504.2	N/A
	602.3	Supports	Confluence pages include descriptive titles such as “CXT Support – Knowledge Base Overview.”
2.4.3 Focus Order	501	Partially Supports	Most elements follow the visual order, but some custom controls are skipped[11].
	504.2	N/A
	602.3	Supports	The support site uses standard HTML elements; focus order is logical.
2.4.4 Link Purpose (In Context)	501	Supports	All link text sufficiently describe the destination or purpose[12].
	504.2	N/A
	602.3	Supports	Links on the support site use descriptive text (e.g., “Operations App,” “Client Portal”), conveying their purpose.
3.1.1 Language of Page	501	Supports	The page declares lang="en"[13].
	504.2	N/A
	602.3	Supports	Support documentation pages declare the language appropriately.
3.1.2 Language of Parts	501	NE	No multilingual content encountered; not tested[14].
	504.2	N/A
	602.3	NE
3.2.1 On Focus	501	Supports	Elements receiving focus do not trigger unexpected changes[15].
	504.2	N/A
	602.3	Supports	Navigation and search fields do not trigger context changes on focus.
3.2.2 On Input	501	Supports	Data entry does not result in unexpected navigation[16].
	504.2	N/A
	602.3	Supports	Forms on the support site (e.g., search) submit on user request.
3.2.3 Consistent Navigation	501	Supports	The navigation menu stays consistent across portal pages[17].
	504.2	N/A
	602.3	Supports	The support site uses consistent navigation menus.
3.2.4 Consistent Identification	501	Supports	Buttons and controls are labeled consistently[18].
	504.2	N/A
	602.3	Supports	Controls and links on the support site are consistently labeled.
3.3.1 Error Identification	501	NE	Error handling (e.g., required field validation) was not tested.
	504.2	N/A
	602.3	NE	Support documentation does not include forms that require user input.
3.3.2 Labels or Instructions	501	Partially Supports	Some inputs have clear labels, but others rely on placeholder text or unlabelled icons[19].
	504.2	N/A
	602.3	Supports	Labels and instructions are provided for search and navigation fields.
4.1.1 Parsing	501	NE	The underlying markup was not checked for validity.
	504.2	N/A
	602.3	NE
4.1.2 Name, Role, Value	501	Partially Supports	Standard HTML controls expose appropriate names and roles; however, custom icon buttons and menus may lack programmatically determinable names or states[20].
	504.2	N/A
	602.3	Supports	The support site uses built‑in Confluence components that expose names and roles properly.

Level AA Criteria

Success Criterion	Category	Conformance Level	Remarks and explanations
1.4.3 Contrast (Minimum) (AA)[21]	501	Does Not Support	Customizable text and icon combinations on the portal (e.g., dark green text on dark backgrounds; light gray placeholder text on white) do not meet the 4.5:1 contrast ratio required for normal text[21].
	504.2	N/A
	602.3	Supports	The support documentation uses dark text on white backgrounds and high‑contrast blue links; color contrast appears to meet or exceed the required ratio.
1.4.4 Resize Text	501	Supports	Text can be resized via browser zoom up to 200% without loss of content or functionality[22].
	504.2	N/A
	602.3	Supports	Text on the support site can be resized using browser zoom without loss of function.
1.4.5 Images of Text	501	Supports	Other than logos, the portal avoids images of text[23].
	504.2	N/A
	602.3	Supports	The support site rarely uses images of text; textual content is real text.
2.4.5 Multiple Ways	501	Supports	Users can navigate using the left navigation menu or the browser’s history[24].
	504.2	N/A
	602.3	Supports	Users can navigate support documentation via menu, search bar or breadcrumb links.
2.4.6 Headings and Labels	501	Partially Supports	Some sections lack proper heading tags; some input fields rely on placeholder text rather than labels[25].
	504.2	N/A
	602.3	Supports	The support site uses appropriate headings and labels throughout articles.
2.4.7 Focus Visible	501	Partially Supports	A thin colored underline indicates focus, which may be difficult for some users to perceive. A more pronounced focus indicator is recommended[26].
	504.2	N/A
	602.3	Supports	Focus indicators on the support site are clearly visible (e.g., blue outlines).
3.1.3 Unusual Words	501	Supports	No uncommon jargon requiring definitions; the criterion requires a mechanism to identify specific definitions of words or phrases used in an unusual or restricted way[27].
	504.2	N/A
	602.3	Supports	Support articles define specialized terms where appropriate.
3.1.4 Abbreviations	501	Supports	Abbreviations are straightforward (e.g., “CXT”); the success criterion requires a mechanism for identifying the expanded form or meaning of abbreviations[28].
	504.2	N/A
	602.3	Supports	Abbreviations are spelled out or widely recognized.
3.1.5 Reading Level	501	Supports	Content appears to be written in an accessible manner. The success criterion requires that supplemental or simpler content be provided when text requires reading ability more advanced than the lower secondary education level[29].
	504.2	N/A
	602.3	Supports	Support documentation is written in clear, straightforward language.
3.1.6 Pronunciation	501	N/A	No words requiring pronunciation guidance.
	504.2	N/A
	602.3	N/A
3.2.5 Change on Request	501	Supports	Context changes occur only after explicit user actions (e.g., selecting templates); the success criterion specifies that changes of context must be initiated only by user request or a mechanism be available to turn off such changes[30].
	504.2	N/A
	602.3	Supports	Navigation in the support site does not automatically shift context without user request.
3.3.3 Error Suggestion	501	NE	Error suggestions (e.g., input correction) were not evaluated.
	504.2	N/A
	602.3	NE
3.3.4 Error Prevention (Legal, Financial, Data)	501	NE	Transaction submission was not tested.
	504.2	N/A
	602.3	N/A	No such processes in support documentation.
4.1.3 Status Messages	501	Partially Supports	Visual status messages (e.g., loading spinners) are not always announced via ARIA roles; screen readers may not be notified[31].
	504.2	N/A
	602.3	Supports	Confluence uses proper ARIA roles to announce status messages (e.g., search results).

Notes

This report reflects the evaluator’s observations at the time of testing and is not a comprehensive certification of accessibility. The Web and Software category (501) covers the customer portal. The Authoring Tools category (504.2) is marked not applicable because the portal does not provide content‑creation functionality. The Support Documentation category (602.3) has been partially assessed using the public knowledge‑base at the URL provided by the user; a complete audit of all documentation pages was not possible within this engagement.

To achieve greater conformance with WCAG 2.0 and Revised Section 508, we recommend that CXT Software address the noted issues: provide descriptive alternative text for all meaningful images, improve color contrast, ensure all interactive elements are keyboard accessible with visible focus indicators, use descriptive link text instead of raw URLs, add skip navigation links, and verify that custom controls expose their names, roles and states via ARIA. Additional testing with screen readers and automated accessibility tools is strongly recommended.

[1] Understanding Success Criterion 1.1.1: Non-text Content | WAI | W3C

Understanding Success Criterion 1.1.1: Non-text Content | WAI | W3C

[2] Understanding Success Criterion 1.3.1: Info and Relationships | WAI | W3C

Understanding Success Criterion 1.3.1: Info and Relationships | WAI | W3C

[3] Understanding Success Criterion 1.3.2: Meaningful Sequence | WAI | W3C

Understanding Success Criterion 1.3.2: Meaningful Sequence | WAI | W3C

[4] Understanding Success Criterion 1.3.3: Sensory Characteristics | WAI | W3C

Understanding Success Criterion 1.3.3: Sensory Characteristics | WAI | W3C

[5] Understanding Success Criterion 1.4.1: Use of Color | WAI | W3C

Understanding Success Criterion 1.4.1: Use of Color | WAI | W3C

[6] Understanding Success Criterion 2.1.1: Keyboard | WAI | W3C

Understanding Success Criterion 2.1.1: Keyboard | WAI | W3C