# Accesslint > To cancel your plan and immediately disconnect AccessLint from all repositories for an account: --- # Source: https://accesslint.com/help/change-or-cancel-plan [ Help ](/help) # How do I change or cancel my plan? To cancel your plan and immediately disconnect AccessLint from all repositories for an account: 1. Visit the [AccessLint listing on the GitHub Marketplace](https://github.com/marketplace/accesslint). 2. Click on "Edit your plan". 3. Choose the account that you want to cancel for. 4. Click on "Cancel this plan". --- # Source: https://accesslint.com/help/github-permissions [ Help ](/help) # What GitHub permissions does AccessLint require? AccessLint requires the following GitHub project permissions for installation: * Read access to repository contents * Read access to metadata * Read and write access to commit statuses * Read and write access to issues * Read and write access to pull requests ## Repository Contents (read only) AccessLint uses the [ Repository Contents permission ](https://developer.github.com/v3/apps/permissions/#permission-on-contents) to access files in your repository related to a Pull Request. We need to see contents of the change you've made in context of the surrounding code to help us identify accessibility issues. We access _only the files that you change in a Pull Request, and only during the lifecycle of that Pull Request_. ## Metadata (read only) All GitHub Apps require the [ Repository Metadata permission ](https://developer.github.com/v3/apps/permissions/#metadata-permissions). _These permissions are a collection of read only endpoints for accessing metadata for various resources that do not leak sensitive private repository information._ ## Commit Statuses (read & write) We use the [ Commit Status permission ](https://developer.github.com/v3/apps/permissions/#permission-on-statuses) to set and update status indicators for your Pull Requests. ## Issues (read & write) We use the [ Issues permission ](https://developer.github.com/v3/apps/permissions/#permission-on-issues) to create reviews and associated comments on your Pull Requests. ## Pull Requests (read & write) We use [ Pull Requests permission ](https://developer.github.com/v3/apps/permissions/#permission-on-pull-requests) to listen for new Pull Requests and assess those changes for accessibility issues. Visit [ GitHub’s developer documentation ](https://developer.github.com/v3/apps/permissions/) for more details on access these permissions give. --- # Source: https://accesslint.com/help # Help * [How do I install AccessLint?](/help/install-accesslint) * [What GitHub permissions does AccessLint require?](/help/github-permissions) * [What’s covered in a review?](/help/what-is-covered) * [What file types are supported?](/help/supported-file-types) * [How do I change or cancel my plan?](/help/change-or-cancel-plan) If you can’t find your answer, [email us](mailto:support@accesslint.com) at **support@accesslint.com** --- # Source: https://accesslint.com/help/install-accesslint [ Help ](/help) # How do I install AccessLint? 1. Sign into GitHub and visit [ AccessLint’s Marketplace Listing ](https://github.com/marketplace/accesslint). 2. Choose the plan that’s right for you (private project review is available in the Professional Plan). 3. Choose which projects you want AccessLint to review. 4. Review and accept the permissions AccessLint requires. The next time you open a Pull Request on GitHub, AccessLint will comment with any accessibility issues we detect. Visit [What’s covered in a review?](/help/what-is-covered) to learn more about what AccessLint looks for. --- # Source: https://accesslint.com/help/supported-file-types [ Help ](/help) # What file types are supported? AccessLint will review all files in your pull requests, and identify issues in files that have HTML-style syntax, as well as Markdown. Note that server-side code (e.g. image_tag and label_tag in Rails) is not evaluated. Only fully formed HTML tags will be tested. --- # Source: https://accesslint.com/help/what-is-covered [ Help ](/help) # What’s covered in a review? AccessLint reviews markup in supported file types for these issues: * Unlabelled form elements * Positive value for tabindex * Images with missing alt text. * Invalid ARIA attribute names