Giters

ryersondmp / sa11y

Sa11y is an accessibility quality assurance tool that visually highlights common accessibility and usability issues. Geared towards content authors, Sa11y straightforwardly identifies errors or warnings at the source with a simple tooltip on how to fix them.

Home Page:https://sa11y.netlify.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Existing Sa11y project

jasonschroeder-sfdc opened this issue · comments

commented

Hi, there is another project with the same goals at https://github.com/salesforce/sa11y which predates this package. Can we work together, or would you consider renaming your project?

commented

Hey @jasonschroeder-sfdc,

If we are checking the commit history, it appears my project predates yours by a few days. My repository was created on March 9, 2020. Salesforce created its repository on March 12, 2020. My project was also first publicly advertised on Global Accessibility Awareness Day on May 21st in 2020.

For your convenience, here are links to the very first commits of both repositories:

  • Sa11y by TMU (formerly Ryerson University): 1395a62 (Verified by GitHub on March 9)
  • Sa11y by Salesforce: salesforce/sa11y@099a6da (Committed on March 12)

You can also use the following tool to confirm the creation dates of both of our repositories: https://www.syncwithtech.org/github-repos-size-creation-date/#bookmarklet

Our projects indeed share a common goal of making the web more accessible, but in my opinion, our projects are vastly different in many ways. Sa11y by Salesforce is a comprehensive testing library for developers (with output in terminal), whereas my project strictly checks for content accessibility issues and is geared towards content editors (GUI based). Feel free to learn more about Sa11y by visiting our project webpage: https://sa11y.netlify.app/

I know Salesforce is also a big supporter of academic institutions like TMU where our Sa11y was started. So I am happy to explore how we can collaborate and help advance the cause of digital accessibility.

I also understand the technical challenges of renaming a repository, and it would be a big ask. Therefore, I am OK with Salesforce using Sa11y. Although to prevent confusion, I would suggest using your long name or a variation of it when advertising, for example: Sa11y Automated Accessibility Testing, SalesForce Sa11y, Salesforce A11y, etc.

Happy Friday!