Back to Blog

The Complete weableColor Ecosystem: VS Code Extension, colorStudio, and NPM Package Integration

10/17/2025

Ecosystem
Integration
VS Code Extension
colorStudio
NPM Package
Workflow
Accessibility

The Complete weableColor Ecosystem: VS Code Extension, colorStudio, and NPM Package Integration

The weableColor ecosystem consists of three powerful tools that work together to create a seamless, accessibility-first color development experience. This guide shows you how to leverage the full ecosystem for maximum productivity and accessibility compliance.

The weableColor Ecosystem Overview

๐ŸŽฏ VS Code Extension

Real-time accessibility checking in your editor

  • Native color picker integration
  • Hover information with WCAG compliance
  • Professional developer workflows
  • Seamless code integration

๐ŸŒˆ colorStudio Web App

Comprehensive color design platform

  • Unified Color Generator (palettes + gradients)
  • AI-powered optimization
  • Multi-format export (Figma, CSS, SVG)
  • Advanced accessibility analysis

๐Ÿ“ฆ NPM Package

Programmatic access and automation

  • @weable/a11y-color-utils library
  • API integration capabilities
  • CI/CD pipeline integration
  • Custom tool development

Professional Workflows

Workflow 1: Design-to-Code Pipeline

This workflow is perfect for designers and developers working together on accessible color systems.

Step 1: Design in colorStudio

  1. Visit colorStudio
  2. Create your color palette:
    • Select base colors
    • Choose harmony types
    • Generate accessible palettes
    • Test gradient combinations
  3. Optimize with AI:
    • Use "Fix My Palette" for accessibility issues
    • Use "Fix My Gradient" for gradient optimization
  4. Export for development:
    • Copy CSS custom properties
    • Export Tailwind configuration
    • Generate Figma-ready color tokens

Step 2: Implement in VS Code

  1. Install the VS Code extension
  2. Paste exported colors into your CSS/SCSS files
  3. Use real-time validation:
    • Hover over colors for accessibility info
    • Click colors to open native color picker
    • Get instant WCAG compliance feedback
  4. Refine as needed:
    • Adjust colors directly in VS Code
    • Test against different backgrounds
    • Ensure accessibility compliance

Step 3: Automate with NPM Package

  1. Install the package:
    npm install @weable/a11y-color-utils
    
  2. Create automated workflows:
    import { generatePalette, checkContrast } from '@weable/a11y-color-utils';
    
    // Generate accessible palettes programmatically
    const palette = generatePalette('#3b82f6', 'triadic');
    
    // Validate contrast in CI/CD
    const isValid = checkContrast('#3b82f6', '#ffffff');
    
  3. Integrate with build processes:
    • Automated accessibility testing
    • Color validation in pull requests
    • Automated color system generation

Workflow 2: Developer-First Approach

This workflow is ideal for developers who want to start with code and validate accessibility.

Step 1: Start in VS Code

  1. Install the VS Code extension
  2. Write your color definitions:
    :root {
      --primary: #3b82f6;
      --secondary: #8b5cf6;
      --accent: #06b6d4;
    }
    
  3. Use real-time validation:
    • Hover over colors for accessibility info
    • Click colors to adjust with native picker
    • Get instant feedback on WCAG compliance

Step 2: Enhance in colorStudio

  1. Copy your colors to colorStudio
  2. Generate harmonious variations:
    • Use harmony types to expand your palette
    • Create light and dark theme variations
    • Generate gradient combinations
  3. Export enhanced palettes:
    • Get CSS custom properties
    • Generate Tailwind configuration
    • Export for design tools

Step 3: Automate with NPM Package

  1. Create automated color validation:
    import { validateColorScheme } from '@weable/a11y-color-utils';
    
    const colors = {
      primary: '#3b82f6',
      secondary: '#8b5cf6',
      accent: '#06b6d4'
    };
    
    const validation = validateColorScheme(colors);
    console.log(validation.accessibilityScore);
    
  2. Integrate with your build process:
    • Automated accessibility testing
    • Color validation in CI/CD
    • Automated documentation generation

Workflow 3: Team Collaboration

This workflow is perfect for teams working on large projects with multiple contributors.

Step 1: Establish Color Standards

  1. Use colorStudio to create master palettes:
    • Define brand colors
    • Create semantic color systems
    • Establish accessibility standards
  2. Export for team use:
    • Generate CSS custom properties
    • Create Tailwind configuration
    • Export Figma color styles

Step 2: Distribute to Team

  1. Share colorStudio links with team members
  2. Provide VS Code extension for all developers
  3. Include NPM package in project dependencies
  4. Create documentation with color usage guidelines

Step 3: Maintain Consistency

  1. Use VS Code extension for real-time validation
  2. Regular colorStudio audits to check compliance
  3. Automated NPM package validation in CI/CD
  4. Team reviews of color changes

Integration Examples

Example 1: React Component with VS Code Extension

// Button.jsx - VS Code extension provides real-time accessibility feedback
import React from 'react';
import './Button.css';

const Button = ({ variant = 'primary', children, ...props }) => {
  return (
    <button 
      className={`btn btn-${variant}`}
      {...props}
    >
      {children}
    </button>
  );
};

export default Button;
/* Button.css - Hover over colors for accessibility info */
.btn {
  padding: 0.75rem 1.5rem;
  border-radius: 0.5rem;
  font-weight: 500;
  transition: all 0.2s ease;
}

.btn-primary {
  background-color: #3b82f6; /* โœ… AAA - Excellent contrast */
  color: #ffffff;            /* โœ… AAA - Excellent contrast */
}

.btn-secondary {
  background-color: #f3f4f6; /* โš ๏ธ AA - Good contrast */
  color: #374151;            /* โœ… AAA - Excellent contrast */
}

Example 2: Automated Color Validation with NPM Package

// colorValidation.js
import { 
  generatePalette, 
  checkContrast, 
  validateColorScheme,
  exportToCSS 
} from '@weable/a11y-color-utils';

// Generate accessible palette
const palette = generatePalette('#3b82f6', 'triadic');

// Validate contrast ratios
const contrastCheck = checkContrast('#3b82f6', '#ffffff');
console.log(`Contrast ratio: ${contrastCheck.ratio}`);
console.log(`WCAG compliance: ${contrastCheck.wcag}`);

// Validate entire color scheme
const validation = validateColorScheme({
  primary: '#3b82f6',
  secondary: '#8b5cf6',
  accent: '#06b6d4',
  background: '#ffffff',
  text: '#1f2937'
});

console.log(`Accessibility score: ${validation.accessibilityScore}`);

// Export to CSS
const css = exportToCSS(palette, {
  format: 'custom-properties',
  prefix: '--color'
});

console.log(css);

Example 3: colorStudio to Figma Integration

  1. Design in colorStudio:

    • Create your color palette
    • Generate gradient combinations
    • Optimize for accessibility
  2. Export for Figma:

    • Copy color values
    • Export gradient definitions
    • Generate color token documentation
  3. Use in Figma:

    • Create color styles
    • Apply to design components
    • Maintain consistency across designs

Best Practices for Ecosystem Integration

1. Start with colorStudio

  • Use colorStudio for initial color exploration
  • Leverage AI-powered optimization
  • Export comprehensive color systems

2. Validate in VS Code

  • Use VS Code extension for real-time validation
  • Test colors in actual code context
  • Ensure accessibility compliance

3. Automate with NPM Package

  • Integrate color validation in CI/CD
  • Create automated accessibility testing
  • Build custom color tools

4. Maintain Consistency

  • Regular color audits across all tools
  • Team training on ecosystem usage
  • Documentation of color decisions

Troubleshooting Integration Issues

Common Issues

Q: Colors don't sync between tools A: Ensure you're using the same color format (hex, RGB, etc.) across all tools. Use colorStudio's export features for consistent formatting.

Q: VS Code extension not showing accessibility info A: Check that the file type is recognized (CSS, SCSS, etc.) and the extension is enabled. Restart VS Code if needed.

Q: NPM package validation failing A: Ensure you're using the latest version of the package and that your color values are valid.

Q: colorStudio export not working A: Make sure you have a valid palette or gradient generated before attempting to export.

Performance Tips

  • Large projects: Use the NPM package for batch operations
  • Real-time validation: Use VS Code extension for immediate feedback
  • Complex designs: Use colorStudio for comprehensive color planning

What's Next

The weableColor ecosystem is constantly evolving:

  • Upcoming: Figma plugin for seamless design tool integration
  • Planned: Team collaboration features in colorStudio
  • Future: AI-powered design suggestions across all tools
  • Roadmap: Advanced animation and interaction tools

Conclusion

The weableColor ecosystem provides a complete solution for accessible color development. By combining the VS Code extension's real-time validation, colorStudio's comprehensive design capabilities, and the NPM package's programmatic access, you can create beautiful, accessible color systems that work for everyone.

Ready to get started? Begin with colorStudio for design, use the VS Code extension for development, and integrate the NPM package for automation.


The weableColor ecosystem is designed to make accessibility effortless. Each tool works independently, but together they create a powerful, integrated workflow for accessible color development.