Add accessibility first draft doc. (#254)

* Add accessibility first draft doc.

* Update timestamp.

.vuepress/config.js

@@ -76,6 +76,7 @@ export default defineUserConfig({
           // '/guides/setup-lando-on-windows-with-wsl-2.html',
           '/guides/updating-to-rc2.html',
           '/guides/lando-corporate-network-tips.html',
+          '/guides/accessibility.html',
         ],
       },
       {

guides/accessibility.md

@@ -0,0 +1,35 @@
+---
+title: Accessibility and Lando
+description: Using Lando with adaptive services.
+guide: true
+
+authors:
+  - name: Team Lando
+    pic: https://gravatar.com/avatar/c335f31e62b453f747f39a84240b3bbd
+    link: https://twitter.com/devwithlando
+updated:
+  timestamp: 1703011953000
+---
+
+## Introduction
+
+Lando is committed to ensuring digital accessibility for people with disabilities. As a text-based CLI tool, Lando should be compatible with most screenreaders. Indeed, accessibility is primarily a challenge of having a terminal application that integrates well with your screen reader or other adaptive devices.
+
+## Accessibility Features
+
+1. **Keyboard Navigation**: All Lando functionalities are accessible via keyboard. Users can navigate through the interface, access all features, and execute commands using standard keyboard shortcuts.
+
+2. **Screen Reader Compatibility**: Lando should be compatible with popular screen readers, although again this primarily depends on your terminal application's compatibility. Textual information, including command outputs and error messages, is structured to be screen reader friendly. If you find command output that is challenging to your screen reader, let us know!
+
+3. **Contrast and Text Size**: Since Lando primarily operates in a command-line interface, we suggest using your terminal application's ability to switch to high contrast modes and adjust text size for users with visual impairments.
+
+4. **Documentation in Accessible Formats**: Lando's electronic documentation should largely conform to WCAG 2.0 A and AA specifications.
+
+## Support and Feedback
+
+We welcome your feedback on the accessibility of Lando. Please let us know if you encounter accessibility barriers:
+
+- **Contact Information**: vpat@lando.dev
+- **Support**: Support for Lando as a free, open-source tool is provided by the Lando community on a volunteer basis via [documented support channels.](https://lando.dev/support)
+
+Please [contact us](https://lando.dev/contact) if you're interested in paid enterprise support, including accessibility support.

guides/lando-corporate-network-tips.md

@@ -88,8 +88,22 @@ update-ca-certificates
 
 Note the location of the certs may change depending on your Linux distribution.
 
+### Add Cert to Lando
 
-### Add Cert to Lando Containers
+Lando creates a CA cert on your host environment at `~/.lando/certs/.lndo.site.pem` that is added into all Lando containers. If you replace this cert with your decryptor's CA cert (or whatever chain of certs you think is necessary for your environment), that should resolve ALL downstream certificate issues.
+
+Follow these steps:
+
+1. Uninstall Lando and Docker (if already installed).
+2. Remove the ~/.lando folder: `rm -rf ~/.lando`
+3. Reinstall Lando
+4. Before running any Lando commands, move your cert to `~/.lando/certs/.lndo.site.pem`: `mv /path/to/your/cert.pem ~/.lando/certs/.lndo.site.pem`
+5. Try starting a new application.
+
+It's important to wipe out all exisitng Lando containers (hence the uninstall) and make sure to add your cert **BEFORE running any Lando commands** to ensure that your cert is populated into the containers.
+
+
+### Add Cert to Individual Lando Containers
 
 Once Lando is running, there are a number of cases where code running inside Lando's containers may need to have the certs installed as well. To do this, first **store the certificates somewhere in your Lando project directory.** We just put them in our project's root directory, so within the container the cert is available at `/app/yourcert.crt`.