TiTANWASTAKEN / ClarityVision

ClarityVision is a Chrome extension that enhances web accessibility for users with color blindness. It provides customizable filters for Protanopia, Deuteranopia, and Tritanopia, allowing users to adjust website colors for improved clarity. The extension features a simple interface to apply or reset filters, ensuring a better browsing experience.
2 stars 1 forks source link

Clarity Vision - Chrome Extension for Color Blindness

Version: 1.1
Description: Clarity Vision is a Chrome extension designed to help individuals with color blindness view web content with improved clarity. The extension offers different filters for Protanopia, Deuteranopia, and Tritanopia, enhancing color perception for users with color blindness. It also includes a reset option to remove the applied filters.

Features

Getting Started

  1. Clone this repository to your local machine:

    git clone https://github.com/TiTANWASTAKEN/clarity-vision-extension.git
  2. Open Chrome, go to chrome://extensions/, and enable Developer mode.

  3. Click on Load unpacked and select the folder where the extension is located.

  4. You will now see the Clarity Vision icon in your Chrome toolbar.

  5. Click on the icon to open the popup and apply any of the color blindness filters.

Using the Extension

Pipeline for Future Improvements

Below are some planned pipeline improvements to further enhance the functionality and user experience of Clarity Vision:

1. Improved Filter Accuracy

2. Persisting Filter Across Sessions

3. Customizable Filters

4. Keyboard Shortcuts

5. Localization Support

6. Enhanced UI/UX Design

7. Analytics Integration

Installation and Development

Prerequisites

Installation for Development

  1. Clone the repository:

    git clone https://github.com/TiTANWASTAKEN/clarity-vision-extension.git
  2. Open Chrome and navigate to chrome://extensions/.

  3. Enable Developer mode.

  4. Click Load unpacked and select the cloned directory.

  5. You can now make changes to the code and reload the extension. If you'd like contributors to push their changes to the master branch instead of the main branch, while keeping the main branch sanitized and stable for releases or production, you can update your contributing guidelines to clarify this process. This is a common workflow where master serves as a working branch, and main is reserved for stable releases or deployments.


Contributing

Contributions are welcome! We maintain a main branch for stable releases and a master branch for development. If you’d like to contribute, please fork the repository and create a pull request to the master branch. Once your changes are reviewed and merged into master, they will eventually be merged into main for release.

Contribution Guidelines:

  1. Fork the repo: Create a personal fork of the project.
  2. Create a new branch: Work on your feature in a separate branch.
    • Create a new branch off of master for your feature:
      git checkout -b feature/your-feature-name master
  3. Make your changes: Write clean, maintainable code, following the style guide.
  4. Commit your changes:
    git commit -m "Add [feature/bugfix] - brief description"
  5. Push to your fork:
    git push origin feature/your-feature-name
  6. Create a Pull Request: Open a pull request against the master branch. Provide a clear description of the changes and link any related issues.

Workflow and Branch Management

We encourage contributors to submit pull requests to master to ensure the main branch stays stable and clean for production releases.

Additional Notes:

Thank you for your contributions!


This project is licensed under the MIT License.