News | Shropshire Fire and Rescue Service

Lists of related items should be written [semantically](https://html.com/semantic-markup/) as a 
list.

Usually this means rewriting these to use the `<ul>` or `<ol>` tags.

This allows assistive technologies to more easily navigate from item to
item, or past entire groups of links if the user wants to. 

## Examples 

### Navigation

This navigation:

```html
<a href="/about">About us</a>
<a href="/products">Products</a>
<a href="/contact">Contact us</a>
```

Should be rewritten as a list:

```html
<ul>
  <li><a href="/about">About us</a></li>
  <li><a href="/products">Products</a></li>
  <li><a href="/contact">Contact us</a></li>
</ul>
```

### Tables for content

This single-column table is redundant. There is no
value in placing the content in a table, which makes
it harder for screen reader users to interpret and interact
with.

```html
<table>
  <tr>
    <td>
      Banana
    </td>
  </tr>
  <tr>
    <td>
      Apple
    </td>
  </tr>
  <tr>
    <td>
      Pear
    </td>
  </tr>
</table>
```

Should be rewritten as a list:

```html
<ul>
  <li>Banana</li>
  <li>Apple</li>
  <li>Pear</li>
</ul>
```

## Justification

Users of assistive technologies, like screen readers, can skip an entire
list in one step. In some cases, they can even search inside a list. 

These aids are not available where links are written outside a list. 
Failing to use lists correctly can force users to have to step through
hundreds of items one at a time.

## Methodology

1. Any single-column tables are automatically considered 
   redundant lists. 
2. For non-table elements, recursively work down the page looking inside
   each element for links separated by minimal amounts of non-link text. 
   If the non-link text is below 30 characters 
   in length, we assume we're inside content that should be a list.
   Some exceptions are made, e.g. the presence of an `<hr>` would break
   out of the list.

## More information

See [Technique
H48](https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/H48) for
details.

Title / URL	Issues
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201910	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201804	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201801	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201703	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201501	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/202306	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201803	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/202011	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/201612	1
News \| Shropshire Fire and Rescue Servicewww.shropshirefire.gov.uk/news/202110	1

Write lists or groups of links semantically

Shropshire Fire and Rescue Service

Where this issue has occurred