{"action":"created","issue":{"url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/238","repository_url":"https://api.github.com/repos/auto-wcag/auto-wcag","labels_url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/238/labels{/name}","comments_url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/238/comments","events_url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/238/events","html_url":"https://github.com/auto-wcag/auto-wcag/issues/238","id":355479776,"node_id":"MDU6SXNzdWUzNTU0Nzk3NzY=","number":238,"title":"Chore: Update \"Contribute\" with more info and links","user":{"login":"annethyme","id":15611692,"node_id":"MDQ6VXNlcjE1NjExNjky","avatar_url":"https://avatars1.githubusercontent.com/u/15611692?v=4","gravatar_id":"","url":"https://api.github.com/users/annethyme","html_url":"https://github.com/annethyme","followers_url":"https://api.github.com/users/annethyme/followers","following_url":"https://api.github.com/users/annethyme/following{/other_user}","gists_url":"https://api.github.com/users/annethyme/gists{/gist_id}","starred_url":"https://api.github.com/users/annethyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/annethyme/subscriptions","organizations_url":"https://api.github.com/users/annethyme/orgs","repos_url":"https://api.github.com/users/annethyme/repos","events_url":"https://api.github.com/users/annethyme/events{/privacy}","received_events_url":"https://api.github.com/users/annethyme/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-08-30T08:32:31Z","updated_at":"2018-08-30T11:04:29Z","closed_at":null,"author_association":"COLLABORATOR","body":"**NOTE:** Working draft for fuller documentation on the \"Contribute\" page:\r\n\r\n# Contribute to Auto-WCAG\r\nAuto-WCAG is a [W3C](https://www.w3.org/) [Community Group](https://www.w3.org/community/) group open to anyone interested in accessibility or accessibility testing, manually or automated. \r\n\r\nWe welcome contributions from anyone, and there are many ways to contribute, from Github issues and pull requests, to contribution to our monthly teleconferences.\r\n\r\nYou don't have to be a member of the Auto-WCAG Community Group to contribute by [giving feedback on rules](#) or [suggesting new rules](#).\r\n\r\nIf you want to get even more out of your involvement in our rule creation project, you can officially [join the Auto-WCAG Community Group](#) to [get on the mailing list](#) and [participate in monthly teleconferences](#).\r\n\r\n## Give feedback on rules\r\n\r\nAnyone can provide feedback on rules on our open [Auto-WCAG Github repository](#), so you don't even have to be a member of the Auto-WCAG Community Group to contribute in this way.\r\n\r\nWhen giving feedback on rules, it is important to consider: \r\n\r\n- Is the rule an appropriate test for the accessibility requirement it sets out to test, e.g. from [WCAG 2](https://www.w3.org/TR/WCAG21/), and in line with the supporting documents, e.g. [Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/) and [Techniques for WCAG 2.0](https://www.w3.org/TR/WCAG-TECHS/)?\r\n- Does the rule allow for solutions both through native markup languages and other technologies such as WAI-ARIA?\r\n- Does the rule live up to requirements set out in the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/)?\r\n\r\n### Feedback for ideas and early drafts (Github Issues) \r\n@@@ A small paragraph about what we use issues for\r\n\r\nStart giving feedback on issues:\r\n\r\n- See the [ideas and early drafts that might need input](#)\r\n- Learn more about [commenting on issues](#)\r\n\r\n### Feedback and reviews for draft rules (Github Pull Requests )\r\n@@@ A small paragraph about what we use PRs for\r\n\r\nStart giving feedback and doing reviews for draft rules:\r\n\r\n- See the [draft rules that need reviews](#)\r\n- See [algorithms that need reviews](#)\r\n- See [other pull requests that need reviews](#)\r\n- Learn more about [reviewing and commenting on pull requests](#)\r\n\r\n### Feedback/corrections for existing rules\r\nWe welcome any input for changes, also for existing rules. \r\nThe rules should be as precise as possible, limiting the number of potential false positives and false negatives, and for this it is important to draw on as many implementations and expert opinions as possible. \r\nFeedback and corrections for existing rules can target both on the sections of the rule itself (Applicability, Expectations, Accessibility Support, etc.) and the test cases, to expand the edge cases they cover.\r\n\r\nYou have several options for correcting existing rules: \r\n\r\n- **Open a discussion:** If you want to open a discussion, you can [open a new issue on Github](#) repository to discuss the issue with the existing rule. Learn more about [creating issues](#).\r\n- **Make the change yourself:** If you know exactly what you want changed, you can do the change yourself as a [pull request on Github](#) and submit it for review. Learn more about [creating pull requests](#).\r\n\r\n## Suggest new rules\r\n\r\nAnyone can suggest new rules on our open [Auto-WCAG Github repository](#), so you don't even have to be a member of the Auto-WCAG Community Group to contribute in this way.\r\n\r\nWhether you have a single great idea for an accessibility rule or you work for an organisation that wants to contribute a whole repository of rules, we welcome the contribution. \r\n\r\n### Submit an idea for discussion (Issue on Github)\r\n\r\n@@@ A small paragraph about creating issues for new rules\r\n\r\n### Submit a draft for a rule (Pull Request on Github)\r\nBefore contributing new rules, we recommend you checked their validity with several experienced accessibility auditors first. This helps you identify potential stumbling blocks early in their design. \r\nIf you want to use the experts in the Auto-WCAG Community Group for this, submit your rule suggestion as an Issue (see “Submit and idea for discussion” above). \r\n\r\n[Learn more about the process for submitting and reviewing rules](#)\r\n\r\n## Join the Auto-WCAG Community Group\r\n\r\nThe best way to stay informed about the activities of Auto-WCAG is to become a member.\r\n\r\n### Mailing list keeps you up to date\r\n\r\nBy becoming a member you will be added to the mailing list, and you will receive all the latest updates, meeting invites etc.\r\n\r\n### Participate in our monthly calls\r\nThe Auto-WCAG Community Group has conference calls every month. It is (usually) on the second Thursday of the month at 16:00 to 17:30 Central European Time. [See the meeting time in your own timezone](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Auto-WCAG+Community+Group+meeting&iso=20180920T16&p1=259&ah=1&am=30).\r\n\r\nParticipating in the Auto-WCAG conference calls is the easiest way to become an active contributor, get to know the other members of the Auto-WCAG Community Group, and learn from the shared pool of knowledge held by the accessibility experts in the group. \r\n\r\nThe invitation and agenda for these meetings is sent out through the mailing list a few days in advance.\r\n\r\n### How to join the Auto-WCAG Community Group\r\n\r\nTo join the Auto-WCAG Community, you need a W3C Account. If you don’t already have one, [get a W3C account here](https://www.w3.org/accounts/request).\r\n\r\nGo to [Join the Auto-WCAG community group now!](#) and join the group.\r\n\r\nIf you work for a W3C Member organization, you will need to request approval. This request will be sent to your organization’s representative in the W3C’s Advisory Committee."},"comment":{"url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/comments/417280360","html_url":"https://github.com/auto-wcag/auto-wcag/issues/238#issuecomment-417280360","issue_url":"https://api.github.com/repos/auto-wcag/auto-wcag/issues/238","id":417280360,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNzI4MDM2MA==","user":{"login":"annethyme","id":15611692,"node_id":"MDQ6VXNlcjE1NjExNjky","avatar_url":"https://avatars1.githubusercontent.com/u/15611692?v=4","gravatar_id":"","url":"https://api.github.com/users/annethyme","html_url":"https://github.com/annethyme","followers_url":"https://api.github.com/users/annethyme/followers","following_url":"https://api.github.com/users/annethyme/following{/other_user}","gists_url":"https://api.github.com/users/annethyme/gists{/gist_id}","starred_url":"https://api.github.com/users/annethyme/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/annethyme/subscriptions","organizations_url":"https://api.github.com/users/annethyme/orgs","repos_url":"https://api.github.com/users/annethyme/repos","events_url":"https://api.github.com/users/annethyme/events{/privacy}","received_events_url":"https://api.github.com/users/annethyme/received_events","type":"User","site_admin":false},"created_at":"2018-08-30T11:04:29Z","updated_at":"2018-08-30T11:04:29Z","author_association":"COLLABORATOR","body":"**Note:** Suggesting a new page for this: \r\n\r\n# Checklist for reviewers\r\n\r\nWhen giving feedback on rules, it is important to consider: \r\n\r\n- Is the rule an appropriate test for the accessibility requirement it sets out to test, e.g. from [WCAG 2](https://www.w3.org/TR/WCAG21/), and in line with the supporting documents, e.g. [Understanding WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/) and [Techniques for WCAG 2.0](https://www.w3.org/TR/WCAG-TECHS/)?\r\n- Does the rule allow for solutions both through native markup languages and other technologies such as WAI-ARIA?\r\n- Does the rule live up to requirements set out in the [ACT Rules Format](https://www.w3.org/TR/act-rules-format/)?"}}
{"actor":{"display_login":"annethyme"}}