fix typo

accessibility/README.md

@@ -18,7 +18,7 @@ For more on this, see https://overlayfactsheet.com
 
 The W3C has put together a set of guidelines called the Web Content Accessibility Guidelines (WCAG), with the goal of standardizing accessibility. This is occasionally updated, with the latest version being 2.1. These guidelines are made of testable criteria and are split into a few major sections:
 
-* Perceivable - Info and ui components must be presentable to all users. They cannot be invisible to any of the user’s senses.
+* Perceivable - Info and UI components must be presentable to all users. They cannot be invisible to any of the user’s senses.
 * Operable - UI and navigation must be operable. They cannot require operations that a user cannot perform.
 * Understandable - Info and operation of UI must be understandable. This involves making sure that users know what to expect when interacting with the page.
 * Robust - Content must be robust enough to be interpreted by a wide variety of user agents, including assistive tech. This means future proofing content against evolving technologies.
@@ -58,4 +58,4 @@ If you wanted to go a little deeper into a11y with a project, you could check it
 
 The WCAG 2.1 VPAT provided by the ITI is convenient, in that the criteria are separated by conformance. So if you wanted, you can just focus on all level A items. It also has links on each criterion that go back to their respective section on the WCAG page to help you understand the item a little more.
 
-Check out the [ITI's page for more context on the VPAT](https://www.itic.org/policy/accessibility/vpat), or [download the WCAG 2.1 VPAT](https://www.itic.org/dotAsset/7edcd54d-c6a6-4649-8375-4a0f0c68eff2.doc).
+Check out the [ITI's page for more context on the VPAT](https://www.itic.org/policy/accessibility/vpat), or [download the WCAG 2.1 VPAT](https://www.itic.org/dotAsset/7edcd54d-c6a6-4649-8375-4a0f0c68eff2.doc).