hannalaakso

Background

We currently have an inline script tag in the page template that adds the 'js-enabled' class

<script>
    document.body.className = ((document.body.className) ? document.body.className + ' js-enabled' : 'js-enabled');
  </script>

This is for usability reasons: we don't want to have to wait for the GOV.UK Frontend JS file to load before the correct classes and styling is applied - this approach avoids the flash of content for instance hiding the toggleable content of details and accordion components.

hannalaakso

/*
  Accordion

  This allows a collection of sections to be collapsed by default,
  showing only their headers. Sections can be exanded or collapsed
  individually by clicking their headers. An "Open all" button is
  also added to the top of the accordion, which switches to "Close all"
  when all the sections are expanded.

hannalaakso

Findings from a phone call with Ed Horsford on 10th July 2018:

1. govuk-country-and-territory-autocomplete should remain its own repo as much of the logic is specific to country data (more specific notes made about the workings of that repo).

2. We should make it easy for depts to consume accessible-autocomplete while adding their own data / logic to it.

3. We should add the following (in this order of priority?) to accessible-autocomplete:

• Sorting (what would be an example of this?)
• Synonyms (for instance on typing "gb", render "United Kingdom (GB)")
• Typos (replace mistyped word with correct word)

hannalaakso

RFC: Audit the Design System to see what in GOV.UK Frontend has not been documented there

Note: Some of these are documented in Updating your code (but not everyone will go through that page).

https://trello.com/c/TC6tcdKA/1045-audit-the-design-system-to-see-what-in-govuk-frontend-has-not-been-documented-there

1. Components not documented in the Design System

• Hint
• Label
• Number, tel, password etc. inputs because DS has only "Text input" - should it be called just "Input"?

hannalaakso

Support for assistive technology

GOV.UK Frontend will allow you to build services that comply with the guidance in the Service Manual.

Currently, GOV.UK Frontend officially supports the following assistive technology:

Software	Version	Type	Browser
JAWS	15 or later	screen reader	Internet Explorer 11

hannalaakso

## Support for assistive technology

GOV.UK Frontend will allow you to build services that comply with the [guidance
in the Service Manual](service-manual-assistive-technologies).

Currently, GOV.UK Frontend officially supports the following assistive technology:

| Software                 | Version        | Type               | Browser                  |
|--------------------------|----------------|--------------------|--------------------------|
| JAWS                     | 15 or later    | screen reader      | Internet Explorer 11    |

hannalaakso

Accessibility criteria for Modal Dialog - WIP

User story

As an Assistive Technology (AT) user, I want to be informed that a modal dialog has opened, what its purpose is, and how to action / close it.

Acceptance criteria

The modal dialog must:

hannalaakso

JS:

var notes = [];
var key = "webDesignerNotes";

window.onload = function() {
  var submitButton = document.getElementById("submit");
	submitButton.onclick = createNote;
	if (!window.localStorage) {
		alert("The Web Storage API is not supported.");