Contents

# Accessibility Check

Review common accessibility problems in the document, and support for PDF/UA specifications in the PDF export dialog and the accessibility deck of the sidebar.

To access this command...

#### From the menu bar:

Choose Tools - Accessibility Check.

Select File - Export as PDF - General - Universal Accessibility (PDF/UA) and click OK.

#### From the keyboard:

Option Alt + 8

#### From the sidebar:

Open the Accessibility Check panel.

#### From the status bar:

Accessibility check

The Accessibility Check tool traverses the document structure and gather all possible accessibility issues. The check can be run manually through the menu or it will be triggered after PDF export dialog, when the PDF/UA support is enabled.

## The Accessibility Check Panel on Sidebar

The Accessibility Check panel on sidebar shows a list of all issues found in the text document.

Links are provided to navigate to the issue immediately. Double click the link to jump and select the object with the accessibility issue.

### Fix button

Click the Fix button to jump to the issue and provide commands to fix it.

## Common accessibility checks

The checks that are currently implemented are:

- Check that the document title is set.

- Check that the document language is set, or that all styles that are in use, have the language set.

- Check all images, graphics, OLE objects for the alt (or title in some objects) text.

- Check that tables do not include split or merged cells, which could be disorienting for users with visual impairments.

- Check for fake/manual numbering (not using integrated numbering). For example writing "1." "2." "3." at the beginning of the paragraphs.

- Check that the hyperlink text is not a hyperlink itself—the hyperlink should be described.

- Check for the contrast between text and the background. The algorithm is described in the WCAG specification.

- Check for blinking text, which can be problematic for people with cognitive disabilities or photosensitive epilepsy.

- Check for footnotes and endnotes, which should be avoided.

- Check for heading order. Order of the headings must increase incrementally with no skips (for example Heading 1 to Heading 3, skipping Heading 2).

- Check, if text conveys additional meaning with (direct) formatting.

Related Topics

Accessibility in LibreOfficeDev

Please support us!