Comfort Mode Hub 🏠

The research and knowledge center for community-driven web accessibility

Welcome to the central hub where web accessibility ideas turn into real tools that help people. This is where we discuss, research, and plan new accessibility features before they get built.

What is Comfort Mode?

Comfort Mode is a framework that lets website users customize accessibility settings to their personal needs - colors, fonts, motion, and more - rather than accepting one-size-fits-all "accessible" designs.

The Goal: Give users control over their web experience while keeping websites beautiful.

How to Get Involved

💡 I have an idea for an accessibility feature

Go to: GitHub Discussions

• Share your idea in the "Ideas" category
• Describe who it would help and why
• Community will discuss and provide feedback

🔬 I want to help with research

Go to: Research Projects

• Check "Research Needed" column for active investigations
• Pick a topic that interests you
• Follow our research template to contribute findings

💻 I want to write code

Go to: Implementation repositories based on what you want to build:

• Main Tool: @cm/core repo [ Sub repos to be added ]

📚 I want to help with documentation

[ To be added ]

🧪 I want to help with testing

Go to: Any implementation repo's "Issues" tab

• Look for "testing-needed" label
• Help verify features work across different browsers
• Test with real accessibility tools

How Ideas Become Real Features

Step 1: Community Discussion

• Someone suggests an accessibility feature
• Community discusses: Is this needed? Who would it help?
• Moderators review for quality and feasibility

Step 2: Research Phase

• Volunteers research the accessibility need
• Find academic papers, user studies, best practices
• Write a research summary using our template

Step 3: Specification Creation

• Research gets turned into a technical specification
• Clear requirements: What exactly should be built?
• Technical approach: How should it work?

Step 4: Moderation Review

• Moderators check specification for:
  • Quality of research
  • WCAG compliance
  • Technical feasibility
  • User value

Step 5: Implementation

• Approved specs become issues in the right repository
• Developers build the feature following the specification
• Code gets reviewed and tested

Step 6: Integration

• New features get integrated into @cm/core
• Documentation gets updated
• Users can start using the feature

Our Quality Standards

Research Must Be:

• Evidence-based: Backed by academic papers or user studies
• Specific: Clear about who it helps and how
• Feasible: Technically possible to implement
• Valuable: Addresses real user needs

Code Must Be:

• Tested: Works across different browsers and devices
• Documented: Clear instructions for other developers
• Accessible: Follows WCAG guidelines
• Maintainable: Clean, readable code

Features Must Be:

• User-centered: Solves actual user problems
• Customizable: Users can adjust to their needs
• Non-intrusive: Doesn't break existing designs
• Performance-friendly: No impact on website speed

Project Structure

cm-hub/
├── discussions/          # Where ideas start
├── research/            # Research summaries and specs for features
├── contributions/      # guides for contributions and accessibility resources
├── templates/          # Templates for consistent contributions
└── docs/               # Documentation and guides

Research Template

[ To be added ]

Code Contribution Guide

Before You Start

1. Check if there's already a specification for what you want to build
2. If not, start a discussion in the Hub first
3. Make sure you understand the technical requirements

Development Process

1. Fork the appropriate repository
2. Create a feature branch
3. Build following the specification
4. Test thoroughly across browsers
5. Document your changes
6. Submit a pull request

Code Standards

• Follow existing code style in the repository
• Write tests for new features
• Update documentation
• Include accessibility considerations

Community Guidelines

Be Respectful

• Remember we're all trying to help people
• Be patient with newcomers
• Provide constructive feedback

Be Evidence-Based

• Back up claims with research
• Cite sources when possible
• Avoid assumptions about user needs
• Lived and observed suggestions are very welcome and encouraged

Be Collaborative

• Help others learn and contribute
• Share knowledge and resources
• Build on each other's work

Getting Help

New to Accessibility?

[ WIP ]

• Check out WebAIM's resources

New to Open Source?

• Read our First Contribution Guide
• Start with documentation or testing tasks
• Ask questions in GitHub Discussions

Technical Questions?

• Check existing issues first
• Create a new issue with details
• Tag appropriate maintainers

Repository Links

• Main Hub: cm-hub (you are here)
• Core Tool: cm-core

[ To be added ]

Research Foundation

This project is based on the research paper "Beyond Compliance: A User-Autonomy Framework for Inclusive and Customizable Web Accessibility" currently under review at Universal Access in the Information Society.

License

This project is open source and will remain free forever. Forking for commercialization is prohibited. All contributions are welcome under our Code of Conduct.

---

🌟 Ready to make the web more accessible for everyone?

Start by introducing yourself in GitHub Discussions and let us know how you'd like to contribute!# Comfort Mode Hub 🏠