Replies: 2 comments
-
https://blog.mozilla.org/wp-content/uploads/2018/05/MZOTS_OS_Archetypes_report_ext_scr.pdf |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am starting this thread to discuss some loose plans.
PHASE 1: REDUCE COST, INCREASE ACCESS
Currently, I am creating an accessibility platform similar to anything on the market. The goal is to create a low to no cost solution that can compete against existing scanning services. A cheaper solution means more users can scan more pages. Also, by building a foundation with common features, we'll be able to understand what unique features to build in further phases.
PHASE 2: INNOVATION
With knowledge from Phase 1, we can start to innovate. I predict we'll build some sort of automated fixing process. The process will allow users to fix WCAG errors. For instance, we could offer suggestions of different color alternatives for contrast issues and then integrate with the web server or repo to fix those issues dynamically.
Alternatively, folks might be interested in our low-cost ability to provide complete site accessibility checking. In that case, we would double down on building the most accessible accessibility scanning platform that allows you to scan every site.
FUNDING THE WORK
To pay for all this work, I hope we can leverage our hosted service, equalify.app.
I like hosted services better than donation models, if the hosted services are founder-run. Managed services create a business need to make the tech better. At the same time, the benevolent founder has moral desire to keep ever-better tech open.
I intend for the hosted service to be cheaper than any other solution so that we can achieve our mission of resolving compliance issues for as many people as possible.
Money for the hosted service would largely go back into the open-source project. We would do that through bug bounties and by hiring .app devs who work full-time to improve open source code (a better Equalify will mean a better Equalify.app).
If the hosted service fails to generate enough money to sustain the open-source app, I would hope people are donating to the project. If donations don't work, no one wants an open source, accessibility platform.
I have another six months or so to continue devoting full-time work to qualify before I have to get a job that pays the bills, so I'm desperately hoping we can create a business model that pays me and others a modest salary before my passion and bank account runs out.
Again, these are just random ideas I have. Curious for any feedback. Happy to change anything and everything.
Beta Was this translation helpful? Give feedback.
All reactions