Merge branch 'develop'

Author: =

.babelrc

@@ -0,0 +1,4 @@
+# Browsers that we support
+
+> 0.25%
+not dead

.browserslistrc

@@ -0,0 +1 @@
+node_modules

.dockerignore

@@ -0,0 +1,7 @@
+MAPBOX_TOKEN=
+API_SERVER=
+ROUTING_SERVER=
+TILE_SERVER=
+ANALYTICS=no
+ANALYTICS_SERVER=
+ANALYTICS_KEY=

.env.sample

@@ -1,34 +1,22 @@
-extends:
-  eslint-config-airbnb
-
-parser:
-  babel-eslint
-
-settings:
-  ecmascript: 6
-
-ecmaFeatures:
-  jsx: true
-  modules: true
-  destructuring: true
-  classes: true
-  forOf: true
-  blockBindings: true
-  arrowFunctions: true
-
-env:
-  browser: true
-
-rules:
-  indent: 2
-  func-style: 0
-  func-names: 0
-  comma-dangle: 0
-  no-console: 0
-  no-param-reassign: 0
-  linebreak-style: 0
-  import/no-extraneous-dependencies: 0
-  import/no-unresolved: 0
-  import/extensions: 0
-  jsx-quotes: [2, "prefer-single"]
-  react/jsx-filename-extension: 0
+{
+  "extends": [
+    "eslint:recommended",
+    "plugin:react/recommended",
+    "plugin:jsx-a11y/recommended",
+    "plugin:import/errors",
+    "prettier"
+  ],
+  "parser": "babel-eslint",
+  "parserOptions": {
+    "ecmaVersion": 6,
+    "sourceType": "module"
+  },
+  "env": {
+    "es6": true,
+    "browser": true,
+    "node": true
+  },
+  "settings": {
+    "import/resolver": "webpack"
+  }
+}

.eslintrc

@@ -5,5 +5,7 @@ static
 *.log*
 _nogit
 *.swp
+public
 
+.env
 set_envs.sh

.gitignore

@@ -0,0 +1,37 @@
+# Accessibility Audit
+
+We want AccessMap to be an accessible web site for screen readers and tab navigation.
+At the moment, we are limited by the component toolkit we've adopted, `react-md`, which
+has decent aria-label/accessibility support, but still has significant holes.
+
+The most popular issue on GitHub for the `react-md` repository indicates that it may
+no longer be under particularly active development, so we should consider using a
+different toolkit and/or rolling our own. Wrapping web components could be a nice way
+forward.
+
+## Known issues
+
+### `role="radio"` combined with `aria-pressed` for radio control groups
+
+The profile selection tabs are modeled as a radio control group, and each selection
+has `role="radio"`. Because `react-md` represents the icons for radio buttons using
+their internal `AccessibleFakeInkedButton` component, they come with an inappropriate
+`aria` attribute: `aria-pressed`.
+
+Proposed solution: write our own control group widget and/or switch to a new
+component kit.
+
+### Slider thumbs have no labels, are announced as "button" on screen readers
+
+There is no way to add a label to slider thumbs due to how they are implemented in
+`react-md`. As they have `role="button"`, they get announced as "button", which is
+useless for someone using a screen reader.
+
+### Keyboard navigation of profiles is awkward, lacks feedback, doesn't meet ARIA
+
+Tab navigation should highlight the profiles group and moving left/right with the
+keyboard should change profiles, same as a radio button group. It doesn't. Instead, it
+shows no feedback whatsoever, and the user is expected to hit 'space' to select a
+profile. This is part of `react-md`'s core behavior.
+
+Proposed solution: write our own control group and/or switch to a new component kit.

.nvmrc

@@ -0,0 +1,11 @@
+FROM node:10-alpine
+
+RUN apk add --no-cache sqlite-dev
+
+WORKDIR /www/
+
+COPY . /www/
+
+RUN if [ -d node_modules ]; then rm -r node_modules; fi
+
+RUN npm ci

ACCESSIBILITY-AUDIT.md

@@ -0,0 +1,22 @@
+# accessmap-webapp
+
+## Installation
+
+## Configuration
+
+Set the environment variables found in `set_envs.sample`.
+
+#### Important: if running the development server, prefix all `SERVER`
+
+variables with http://. The proxy won't work otherwise and all the servers will
+break
+
+## Sponsors / Supporters of Open Source
+
+Continued development of AccessMap is sponsored by the Taskar Center for Accessible
+Technology.
+
+Hosting of AccessMap is sponsored by Microsoft Azure.
+
+Cross-browser testing is supported by
+[![BrowserStack](assets/logos/browserstack.png)](https://www.browserstack.com) (BrowserStack).