COTS

What is COTS?

COTS stands for Commercial Off-The-Shelf, referring to software products that are ready-made and available for purchase by the general public. Unlike custom-developed software, COTS solutions are pre-built, standardized products that organizations can implement with minimal customization. Examples include Microsoft Office, Salesforce, Adobe Creative Suite, and various content management systems like WordPress or Drupal.

COTS and Digital Accessibility

In the context of web accessibility and digital inclusion, COTS products present unique challenges and opportunities. Organizations must ensure that any COTS solution they adopt meets accessibility standards such as WCAG 2.1 (Web Content Accessibility Guidelines) and complies with regulations like the Americans with Disabilities Act (ADA), Section 508, and Germany's BFSG (Barrierefreiheitsstärkungsgesetz).

The responsibility for accessibility compliance becomes shared between the COTS vendor and the implementing organization, making it crucial to evaluate accessibility features before procurement and implementation.

Practical Implementation Tips

When selecting and implementing COTS solutions for accessibility:

  • Procurement Phase: Request Voluntary Product Accessibility Templates (VPATs) from vendors to understand WCAG compliance levels
  • Evaluation: Conduct accessibility testing on COTS products before purchase, focusing on keyboard navigation, screen reader compatibility, and color contrast
  • Configuration: Ensure accessible configuration of COTS products, including proper heading structures, alt text for images, and form labels
  • Integration: When integrating COTS with existing systems, maintain accessibility standards throughout the implementation process
  • Training: Provide accessibility training to teams using COTS products to ensure ongoing compliance

Common Mistakes and Misconceptions

Several misconceptions surround COTS and accessibility:

  • Assumption of Compliance: Many organizations assume that popular COTS products are automatically accessible, which is often not the case
  • Vendor Responsibility Only: Some believe accessibility is solely the vendor's responsibility, ignoring the need for proper implementation and configuration
  • One-Size-Fits-All: Assuming that if a COTS product works for one organization's accessibility needs, it will work for all
  • Post-Purchase Fixes: Believing that accessibility issues can be easily resolved after implementation without significant additional costs

COTS in Different Platforms

COTS accessibility considerations vary across platforms:

  • Web Applications: Must meet WCAG standards and work with assistive technologies
  • Mobile Apps: Should comply with iOS and Android accessibility guidelines
  • Desktop Software: Must support operating system accessibility features
  • CMS Platforms: Should enable content creators to produce accessible content easily

Best Practices and Key Takeaways

The most important takeaway for organizations is to make accessibility a primary consideration in COTS procurement. This includes:

  • Establishing accessibility requirements before vendor selection
  • Incorporating accessibility criteria into RFP processes
  • Budgeting for accessibility testing and potential remediation
  • Creating ongoing accessibility monitoring processes for COTS implementations
  • Maintaining documentation of accessibility decisions and configurations

By treating accessibility as a core requirement rather than an afterthought, organizations can ensure their COTS implementations support digital inclusion and meet regulatory compliance requirements while avoiding costly retrofitting later.