The Siteimprove accessibility testing tool raised an issue with our having a div with role=region in the page that was: - empty - with no label The status has a role of 'region' which makes it a generic landmark. This means that, unlike <nav> or <footer>, users don't get any hint of its purpose from its HTML tag. If we did want this, we'd have to give it a label to explain that. I don't think we do want those things. I think it's more of a sentence that sits between the searchbox and the results, just saying how many are there. That being the case, we should just remove the role. It's also what design system do with their character count, which is similar: https://design-system.service.gov.uk/components/character-count/ Unlike that component, I don't think we need to use aria-describedby to set the status as the description of the searchbox because it describes the results, not the search term.
notifications-admin
GOV.UK Notify admin application - https://www.notifications.service.gov.uk/
- Register and manage users
- Create and manage services
- Send batch emails and SMS by uploading a CSV
- Show history of notifications
Setting up
Python version
At the moment we run Python 3.6 in production.
NPM packages
brew install node
NPM is Node's package management tool. n is a tool for managing different versions of Node. The following installs n and uses the long term support (LTS) version of Node.
npm install -g n
n lts
environment.sh
In the root directory of the application, run:
echo "
export NOTIFY_ENVIRONMENT='development'
export FLASK_APP=application.py
export FLASK_ENV=development
export WERKZEUG_DEBUG_PIN=off
"> environment.sh
AWS credentials
To run parts of the app, such as uploading letters, you will need appropriate AWS credentials. See the Wiki for more details.
To run the application
# install dependencies, etc.
make bootstrap
# run the web app
make run-flask
Then visit localhost:6012.
Any Python code changes you make should be picked up automatically in development. If you're developing JavaScript code, run npm run watch to achieve the same.
To test the application
# install dependencies, etc.
make bootstrap
# run all the tests
make test
# continuously run js tests
npm run test-watch
To run a specific JavaScript test, you'll need to copy the full command from package.json.
To update application dependencies
requirements.txt is generated from the requirements.in in order to pin versions of all nested dependencies. If requirements.in has been changed, run make freeze-requirements to regenerate it.