Fixed grammar mistakes in the backstage accessibility docs
Signed-off-by: AmbrishRamachandiran <ambrish.r@infosys.com>
This commit is contained in:
@@ -8,7 +8,7 @@ In an effort to bake accessibility practices further into our process of buildin
|
||||
|
||||
## How to contribute
|
||||
|
||||
There are multiple ways to contribute to making Backstage more accessible, you'll find below a list of examples to help you get started.
|
||||
There are multiple ways to contribute to making Backstage more accessible; you'll find below a list of examples to help you get started.
|
||||
|
||||
### Run Lighthouse in CI on your plugin
|
||||
|
||||
@@ -58,6 +58,6 @@ If your Backstage plugin lives outside of the [Backstage main repository](https:
|
||||
|
||||
### Report identified issues
|
||||
|
||||
It’s important to remember that automated checks can only catch a small number of accessibility issues, therefore we also encourage you to conduct manual testing of your plugins using Assistive technology (screen readers, alternative navigation, and screen magnifiers are a few examples).
|
||||
It’s important to remember that automated checks can only catch a small number of accessibility issues; therefore, we also encourage you to conduct manual testing of your plugins using Assistive technology (screen readers, alternative navigation, and screen magnifiers are a few examples).
|
||||
|
||||
If you have identified accessibility issues and don’t have time to contribute a fix, please open an issue over at [Backstage Issues](https://github.com/backstage/backstage/issues) to let us know.
|
||||
|
||||
Reference in New Issue
Block a user