bbertucc / wcat Goto Github PK

Problem

Big ideas are difficult to implement without support. There’s currently no information on how WCAT will be sustained in README.md. This is blocking future work on the project outside of purely altruistic collaboration.

Solution

Some folks have suggested building and raising money for a startup that pushes the ideals of this project. Startups can raise funding rather quickly with the minimal promise of deliverables. The downside is that startups require investors and investors to trade cash currency; they are out for profits beyond impact.

Another option might be a non-profit. There are several models for creating a sustainable startup. One model I like is how Khronos supports its 3D technology. Khronos charges partners a fee for being involved with committees that develop technology, which is then exploited by the partners.

I imagine companies that sell accessibility compliance products would be interested in partnering with WCAT non-profit to reduce the costs of underlining technology. Organizations, like Universities, that must maintain accessibility compliance over thousands or millions of web pages would also be able to reduce their technology costs by adopting WCAT. Any partnering organization would be able to set guidelines that benefit their unique needs. (Side note: we could create a charter that only goes into effect when a certain amount of organizations agree to participate, ensuring funding and a diverse group of interests.)

The downside of the non-profit route is limited capitalization. Technology development requires lots of R&D that would not be possible without budgets that may only be able to be raised in for-profit fundraising.

The third option is for governments to support WCAT. I could see WCAT becoming part of the US General Services Administration (GSA) and other similar government organizations or, better yet, part of some sort of international group to create tooling that supports access to the internet.

Government support would ensure that WCAT's development is not impeded by funding restrictions. Governments also, in theory, trade in "the public good," and so WCAT would be able to work to satisfy that most desirable currency, "goodness," instead of profits.

Beyond the difficulties of setting up an internationally recognized government organization, government solutions are notoriously monolithic and this approach might impede the development of website accessibility.

Finally, there is the option of relying on some sort of anarchy to develop these solutions. Let’s call this anarchy “altruism.” While things like Mardi Gras that claim great fits of altruism are fun, technological solutions cannot subsist on altruism forever. Altruism will always be key to WCAT's success but continued growth and sustainability of the project will require organized support.

Impact

Whatever WCAT is sustained by, it must ensure an outcome-driven, forward-moving opportunity to make the internet ever more accessible.

Problem

README.md proposes a grand vision without specific technological requirements for how to reach that vision.

Solution

Draft requirements based on research on existing accessibility technology. CivicActions published a list of accessibility tools that can be referenced. A survey of these and other tools should help define the requirements of WCAT development. Requirements may include suggestions of languages, testing workflows, and desired input/output outcomes. The aim of these tech requirements is to inspire the open-source development of new technologies and funding of that development under the auspices of "WCAT."

Impact

Tech requirements should inspire open-source contributors to develop WCAT and funders to contribute financial resources to support the project.

There’s no need for #2 if there's nothing to sustain.