List of services | A-Z listing of services

Sitemap

Blackpool Council | Transport policy

Blackpool Council | Social media sites

Blackpool Council | Contact us

Privacy policy and cookies

Blackpool Council | Paying for services

Accessibility statement

Blackpool Council libraries | Catalogue search | Library search

Blackpool Council Tax | Help if you are struggling to pay

All controls on the page - including links, buttons, and fields - should clearly 
indicate when they have been selected by the keyboard.

This is a stricter version of [WCAG 2.4.7](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html),
which requires that the focus indicator is visible, but doesn't specify how clearly
it should be visible.

You can confirm this yourself by loading a webpage and using the Tab key to navigate 
through it. Anything you can select should clearly alter its appearance when selected. 
For example, a text field might change color, or have a distinctive border applied. 

## The requirements

The [official requirements](https://w3c.github.io/wcag/understanding/focus-appearance.html) are 
complicated. A simplified version is:

* Surround the control with a solid outline
* The outline must have at least 3:1 contrast with its background
* The outline must have at least 3:1 contrast with its surroundings, or be at least 2px thick

The actual requirements allow for more variation, but generally require that you 
calculate the perimeter and/or area of the focus area, which can be very difficult.

## How to fix

Links and form controls should use a focus selector which contrasts with their
unfocused state, as well as any surroundings of the focus state. 

In practice, the easiest way to accomplish this is to use a two-color focus, like so:

```css
/* ensure high-contrast mode still has an indicator */
outline: 2px transparent solid;

/* Apply a thick yellow box-shadow with 
   a thin dark blue indicator in the middle */
box-shadow: 0 0 0 2px #F9F9D1, 0 0 0 4px #396196, 0 0 4px 8px #F9F9D1;
``` 

From [Technique C40](https://www.w3.org/WAI/WCAG22/Techniques/css/C40).

Using two contrasting colors guarantees that the focus state will be visible, 
regardless of the background or surrounding colors.

## Troubleshooting

### Elements appear to change in the browser

Focus states should be defined in CSS alone, and not require JavaScript to work. 

Try disabling JavaScript on the page, and see if focus is still visible. If it not, 
then the focus state won't work with assistive technologies that don't have a physical
keyboard, e.g. mobile phones.

Some more unusual means of implementing a focus state cannot be detected or measured
automatically. These include:

* Focus implemented via pseudo-elements - such as `::after` or `::before`. 
* Focus using `:focus-within` (JavaScript current provides no way to access these).
* Focus cascaded to child elements, e.g. a `<span>` inside an `<a>` tag. We detect
  some of these cases, but there are variations that we cannot detect.

Currently, there is no practical way to assess these focus states automatically.

### Elements over images not analyzed

Silktide cannot assess the contrast of elements that are over images. This is because
the contrast of an element is calculated by comparing the color of the element with the
color of the background. 

If the element is over an image, the background color is the
color of the image, which varies from pixel-to-pixel, and may vary further as the page
is resized, due to responsive design.

### Unexpected elements are focusable

You may be surprised to see tags like `<div>` or `<span>` being shown as focusable.
If an element has a `tabindex` of 0 or higher, it becomes focusable. Any HTML tag can be made 
focusable in this way, this is so that custom controls (e.g. your own drop-down menus, or 
sliders) can support keyboard navigation. [Learn more about tabindex on MDN](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex).

## Further reading

This is part of the draft WCAG 2.2 specification and is subject to change.

* [WCAG 2.4.11](https://w3c.github.io/wcag/understanding/focus-appearance.html)

ensure-focus-appearance

May 2024

April 2024

Blackpool Council

Title / URL	Issues
List of services \| A-Z listing of serviceswww.blackpool.gov.uk/List-of-Services.aspx	100
Sitemapwww.blackpool.gov.uk/Sitemap.aspx	100
Blackpool Council \| Transport policywww.blackpool.gov.uk/Residents/Parking-roads-and-transport/Transport/Transport-policy.aspx	51
Blackpool Council \| Social media siteswww.blackpool.gov.uk/Social-media.aspx	40
Blackpool Council \| Contact uswww.blackpool.gov.uk/Contact-us.aspx	29
Privacy policy and cookieswww.blackpool.gov.uk/Privacy-policy-and-cookies.aspx	22
Blackpool Council \| Paying for serviceswww.blackpool.gov.uk/Pay-It/Pay-It.aspx	20
Accessibility statementwww.blackpool.gov.uk/Accessibility.aspx	17
Blackpool Council libraries \| Catalogue search \| Library searchwww.blackpool.gov.uk/Residents/Libraries-arts-and-heritage/Libraries/Library-catalogue-search.aspx	16
Blackpool Council Tax \| Help if you are struggling to paywww.blackpool.gov.uk/Residents/Council-tax/Help-if-you-are-struggling-to-pay.aspx	15

Ensure controls clearly indicate when they are selected

Blackpool Council

Where this issue has occurred