Merge pull request #486 from equalizedigital/release/v1.8.0

Release/v1.8.0

.editorconfig

@@ -0,0 +1,25 @@
+# This file is for unifying the coding style for different editors and IDEs
+# editorconfig.org
+
+# WordPress Coding Standards
+# https://make.wordpress.org/core/handbook/coding-standards/
+
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = tab
+
+[*.{yml,yaml}]
+indent_style = space
+indent_size = 2
+
+[*.{gradle,java,kt}]
+indent_style = space
+
+[packages/react-native-*/**.xml]
+indent_style = space
+

.eslintrc

@@ -0,0 +1,13 @@
+{
+	"extends": [ "plugin:@wordpress/eslint-plugin/esnext" ],
+	"env": {
+		"browser": true,
+		"node": false
+	},
+	"globals": {
+		"wp": true,
+		"jQuery": true,
+		"edac_script_vars": true,
+		"ajaxurl": true
+	}
+}

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,120 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+https://equalizedigital.com/contact/.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/),
+version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

.github/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contribution Guidelines
+
+Before filing a bug report or a feature request, be sure to read the contribution guidelines.
+
+## How to use GitHub
+We use GitHub exclusively for well-documented bugs, feature requests and code contributions. Communication is always done in English.
+
+To receive free support for Accessibility Checker we have the following channels:
+* [The support pages on our site](https://my.equalizedigital.com/support/)
+* [Support forums](https://wordpress.org/support/plugin/accessibility-checker/) on WordPress.org
+
+Thanks for your understanding.
+
+## Security issues
+Please do not report security issues here. Instead, email them to security at our domain so we can deal with them securely and quickly.
+
+## I have found a bug
+Before opening a new issue, please:
+* update to the newest versions of WordPress and the Accessibility Checker plugins.
+* search for duplicate issues to prevent opening a duplicate issue. If there is already an open existing issue, please comment on that issue.
+* follow our _New issue_ template when creating a new issue.
+* add as much information as possible. For example: add screenshots, relevant links, step by step guides etc.
+
+## I have a feature request
+Before opening a new issue, please:
+* search for duplicate issues to prevent opening a duplicate feature request. If there is already an open existing request, please leave a comment there.
+* add as much information as possible. For example: give us a clear explanation of why you think the feature request is something we should consider for the plugin.
+
+## I want to create a patch
+Community made patches, localizations, bug reports and contributions are very welcome and help us tremendously.
+
+When contributing please ensure you follow the guidelines below so that we can keep on top of things.
+
+#### Submitting an issue you found
+Make sure your problem does not exist as a ticket already by searching through [the existing issues](https://github.com/equalizedigital/accessibility-checker/issues). If you cannot find anything which resembles your problem, please [create a new issue](https://github.com/equalizedigital/accessibility-checker/issues/new).
+
+#### Fixing an issue
+
+* Fork the repository on GitHub (make sure to use the `develop` branch).
+* Make the changes to your forked repository.
+* Ensure you stick to the [WordPress Coding Standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/) and you properly document any new functions, actions and filters following the [documentation standards](https://make.wordpress.org/core/handbook/best-practices/inline-documentation-standards/php/).
+* When committing, reference your issue and include a note about the fix.
+* Push the changes to your fork and submit a pull request to the `develop` branch of the Accessibility Checker repository.
+
+We will review your pull request and merge when everything is in order. We will help you to make sure the code complies with the standards described above.
+
+#### 'Patch welcome' issues
+Some issues are labeled 'patch-welcome'. This means we see the value in the particular enhancement being suggested but have decided for now not to prioritize it. If you however decide to write a patch for it, we'll gladly include it after some code review.
+
+#### Additional Resources
+* [General GitHub Documentation](https://help.github.com/)
+* [GitHub Pull Request documentation](https://help.github.com/send-pull-requests/)

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+<!-- Please use this template when creating an issue. 
+- Please check the boxes after you've created your issue.
+- Please use the latest version of Accessibility Checker.-->
+
+* [ ] I've read and understood the [contribution guidelines](https://github.com/equalizedigital/accessibility-checker/blob/develop/.github/CONTRIBUTING.md).
+* [ ] I've searched for any related issues and avoided creating a duplicate issue.
+
+### Please give us a description of what happened.
+
+
+
+
+### Please describe what you expected to happen and why.
+
+
+
+
+### How can we reproduce this behavior?
+1.
+2.
+3.
+
+### Technical info
+* WordPress version:
+* Accessibility Checker version:
+<!-- You can check these boxes once you've created the issue. -->
+* If relevant, which editor is affected (or editors): 
+- [ ] Classic Editor
+- [ ] Gutenberg
+- [ ] Classic Editor plugin
+- [ ] Page Builder (please specify):
+
+<!-- You can check these boxes once you've created the issue. -->
+* Which browser is affected (or browsers): 
+- [ ] Internet Explorer
+- [ ] Edge
+- [ ] Chrome
+- [ ] Firefox
+- [ ] Safari
+- [ ] Brave
+
+* Relevant plugins in case of a bug:
+<!-- Please make sure you can reproduce this bug with a default theme such as Twenty Seventeen. Sometimes issues may occur due to theme conflicts. -->
+* Tested with theme:

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,15 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+<!-- Before opening a new issue, please search for duplicate issues to prevent opening a duplicate feature request. If there is already an open existing request, please leave a comment there. -->
+
+## Is your feature request related to a problem? Please describe.
+
+## Describe the solution you'd like
+
+## Why do you think this feature is something we should consider for this plugin?
+
+## Additional context

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/SECURITY.md

@@ -0,0 +1,21 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+You can report any security bugs found in the source code of this plugin through the [Patchstack Vulnerability Disclosure Program](https://patchstack.com/database/vdp/accessibility-checker). The Patchstack team will assist you with verification, CVE assignment and take care of notifying the developers of this plugin.
+
+## Responding to Vulnerability Reports
+
+Equalize Digital takes security bugs seriously.  We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions. Patchstack will work with you and us to deal with the security issue as best as possible.
+
+## Disclosing a Vulnerability
+
+Once an issue is reported, Equalize Digital uses the following disclosure process:
+
+- When a report is received, we confirm the issue and determine its severity together with Patchstack.
+- If we know of specific third-party services or software that require mitigation before publication, those projects will be notified.
+- An advisory is prepared (but not published) which details the problem and steps for mitigation.
+- Patch releases are published and the advisory is published.
+- Release notes and our `changelog.txt` will include a `Security` section with a link to the advisory.
+
+We credit reporters for identifying vulnerabilities, although we will keep your name confidential if you request it.

.github/workflows/lint-js.yml

@@ -0,0 +1,37 @@
+name: Lint JS
+
+on:
+  # Run on pushes to select branches and on all pull requests.
+  push:
+    branches:
+      - main
+      - develop
+      - trunk
+      - 'feature/**'
+      - 'release/**'
+      - 'hotfix/[0-9]+.[0-9]+*'
+  pull_request:
+  # Allow manually triggering the workflow.
+  workflow_dispatch:
+
+# Cancels all previous workflow runs for the same branch that have not yet completed.
+concurrency:
+  # The concurrency group contains the workflow name and the branch name.
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+
+    name: "Lint: JS"
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      # The lint stage doesn't run the unit tests or use code style, so no need for PHPUnit, WPCS or phpcompatibility.
+      - name: 'Install NPM packages'
+        run: npm install
+      - name: 'Run ESLint'
+        run: npm run lint:js

.github/workflows/lint.yml → .github/workflows/lint-php.yml

@@ -1,4 +1,4 @@
-name: Lint
+name: Lint PHP
 
 on:
   # Run on pushes to select branches and on all pull requests.
@@ -36,16 +36,21 @@ jobs:
       - name: Checkout code
         uses: actions/checkout@v3
 
-      - name: Run custom composer script
-        run: ./run-composer.sh
-
-      - name: Install PHP
+      - name: Install PHP for the composer install
         uses: shivammathur/setup-php@v2
         with:
-          php-version: ${{ matrix.php_version }}
-          ini-values: zend.assertions=1, error_reporting=-1, display_errors=On
+          php-version: 7.4
           coverage: none
-          tools: cs2pr
+
+      # The lint stage doesn't run the unit tests or use code style, so no need for PHPUnit, WPCS or phpcompatibility.
+      - name: 'Composer: adjust dependencies - remove PHPUnit'
+        run: composer remove --no-update --dev phpunit/phpunit --no-scripts --no-interaction
+      - name: 'Composer: adjust dependencies - remove Yoast test urils'
+        run: composer remove --no-update --dev yoast/wp-test-utils --no-scripts --no-interaction
+      - name: 'Composer: adjust dependencies - remove PHPCompatibility'
+        run: composer remove --no-update --dev phpcompatibility/phpcompatibility-wp --no-scripts --no-interaction
+      - name: 'Composer: adjust dependencies - remove WPCS'
+        run: composer remove --no-update --dev wp-coding-standards/wpcs --no-scripts --no-interaction
 
       # Install dependencies and handle caching in one go.
       # @link https://github.com/marketplace/actions/install-composer-dependencies
@@ -55,5 +60,13 @@ jobs:
           # Bust the cache at least once a month - output format: YYYY-MM-DD.
           custom-cache-suffix: $(date -u -d "-0 month -$(($(date +%d)-1)) days" "+%F")
 
+      - name: Install PHP for the actual test
+        uses: shivammathur/setup-php@v2
+        with:
+          php-version: ${{ matrix.php_version }}
+          ini-values: zend.assertions=1, error_reporting=-1, display_errors=On
+          coverage: none
+          tools: cs2pr
+
       - name: Lint against parse errors
-        run: composer lint -- --checkstyle | cs2pr
+        run: composer lint -- --checkstyle | cs2pr