# VGAR Navigation Requirements

## Pagination (NAV-WEB-007)

### Ensure pagination controls are accessible

Pagination controls must be identified as navigation elements by adding the attribute role="navigation" to all pagination controls.

All pagination controls must also have the aria-label="pagination". If there are multiple pagination elements, make sure they each have a unique label that contains the word pagination.

### Requirements

#### Pagination is Navigation (NAV-WEB-007-01)

Pagination controls MUST have the attribute role="navigation".

```javascript

```

#### Label Pagination (NAV-WEB-007-02)

Pagination controls MUST have the attribute aria-label="Pagination". If there are more than one pagination controls on a page, they MUST have unique labels, but still contain the word "Pagination".

```javascript

```

### Test Procedures

#### Juicy Studio > ARIA > Document Landmarks (NAV-WEB-007-01-T)

Confirm that any pagination controls on the screen have role="navigation".

#### Screen reader Landmarks (NAV-WEB-007-02-T)

Cycle through each landmark role with each supported screen reader and confirm that any pagination controls have the word "Pagination" included in their aria-label.

### Related Content

#### WCAG Success Criteria

- [4.1.2 Name, Role, Value](http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html)

#### W3C Techniques

- [ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used](http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/ARIA14)
- [ARIA4: Using a WAI-ARIA role to expose the role of a user interface component](http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/ARIA4)

#### Common Failures

- [F59: Failure of Success Criterion 4.1.3 due to using script to make a div or a span a user interface control in HTML without providing a role for the control](https://www.w3.org/TR/WCAG20-TECHS/F59.html)
- [F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely](https://www.w3.org/TR/WCAG20-TECHS/F15.html)
- [F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name](http://www.w3.org/TR/2015/NOTE-WCAG20-TECHS-20150226/F68)