Add files via upload

Author: janmaarten-a11y

CODEOWNERS

@@ -0,0 +1,3 @@
+# This repository is maintained by: 
+* @github/accessibility-design
+scenarios-framework.md @mattobee

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <opensource@github.com>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,41 @@
+## Contributing
+
+[fork]: https://github.com/github/annotation-toolkit/fork
+[pr]: https://github.com/github/annotation-toolkit/compare
+
+Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's CC-BY 4.0 open source license](./LICENSE.md).
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
+
+## How can you contribute to the Figma library
+
+We would love your feedback and contributions to help improve the Annotation Toolkit. As they're often used on proprietary and unreleased work, tools like this tend to be built and used in isolation. If you have customized this library for your own use, you can help this open source tool grow and evolve so that others can benefit from your innovation. **We are happy to consider integrating ideas you've explored in your own library forks and submitted as a new [issue](https://github.com/github/annotation-toolkit/issues).** 
+
+Due to how Figma handles open source files, we can only take _direct_ contributions from **GitHub staff**.
+
+## GitHub staff contributions
+
+1. To make changes you first need to create a new branch from Annotation Toolkit by selecting “Create branch...” from the dropdown or via the command palette. Name it `@username/changes-being-made`. For example: `@ericwbailey/update-basic-annotations`.
+2. When you are satisfied with the changes you made, request a review from the maintainers. If you are not sure who that is, reach out in the `#annotation-toolkit` slack channel. Add a detailed message describe what you changed and why.
+3. Once your branch is approved, a maintainer will take care of merging and publishing the changes to the library.
+
+We use this process to make sure no accidental changes get added to the library. It also allows us to better track changes added by a branch. Think of it as a repo that does not allow direct pushes to the main branch.
+
+### Merging contributions (for maintainers)
+Only maintainers with editor rights can merge contributions.
+
+#### Process for merging branches
+1. Reset the main file to the latest release or the last time a branch was merged by hovering over the item, clicking the dots to show the more menu and selecting “restore version”.
+2. Open the branch and review & test everything to make sure it works
+3. Open the review window by clicking on the “In Review” badge next to the name
+4. Make sure there are no conflicts
+5. Merge the branch
+
+### Publishing changes (for maintainers)
+Only maintainers with editor rights can publish changes.
+
+#### Process for publishing releases
+1. Select “Publish library” from the dropdown next to the file name.
+2. In the dialog check that all changes that will be published are valid.
+3. Add a very descriptive description. This will be part of the release notes later so make sure to include what was changed and why.
+4. Press the “Publish” button and your release is done.