add rogue mapping a11y doc

mapping/accessibility.md

@@ -0,0 +1,14 @@
+# Tips for General Mapping Accessibility
+
+#### Is your data tabular?
+If your data was tabular to begin with, consider making that:
+- available for download, or 
+- available for display on the same or another page.
+
+This has the added benefit of sidestepping difficulties with making the map itself functionally accessible, since all the data will be present and digestible elsewhere.
+
+
+#### Do you have lots of keyboard navigable elements on your map?
+If your map has a ton of elements that can be tabbed through, and also has more content underneath it, consider adding in a skip block.
+
+[Skip blocks](https://webflow.com/made-in-webflow/website/Skip-Blocks) are normally recommended for elements that are repeated across multiple different pages (i.e nav bars). But in the case of the [Chicago Recovery Plan's](https://chirecoveryplan.com/) homepage map, there are 75+ elements to tab through before you can focus on the content below the map. This kind of skip block is more of a nice quality of life feature.