Accessibility checks on published output
See what is checked before publish, how the checks run and how to report a barrier.
What is checked
Checks run on the published web pages and PDF files for each edition and weekly change set.
Headings in order
Add headings in order on every page. Do not skip a level to make text look bigger.
Table headers
Mark the header row and column for every table so a reader can follow each cell.
Alt text
Add text that describes every picture that carries meaning. Mark decorative pictures as decorative.
Language
Set the page language and keep it the same across the edition and the PDF file.
Contrast
Use text and background colours that can be read easily. Do not use colour alone to carry meaning.
Keyboard use
Make every control reachable and usable by keyboard, with a clear order and a visible focus.
PDF tagging
Tag PDF files so headings, tables and text alternatives travel with the file.
Reading order
Keep the reading order the same as the visual order in the PDF file, from heading to paragraph to table.
How checks run
Run the checks on the edition, fix each finding in the paragraph and run the checks again before you publish.
Open the edition or weekly change set
Open the edition in the app and check the list of paragraphs it contains.
Run the pre-publish check
Run the check for the edition. Read each finding and note the paragraph it names.
Fix the paragraph
Open the paragraph, fix the heading, table header, alt text, language, contrast or keyboard order it names, and save a new version with a reason.
Run the check again
Run the check again. Repeat the fix and re-run steps until no blocking finding remains.
Review a sample chapter by hand
Open a sample of the published pages, read them with a keyboard and a screen reader, and record the checker name and date on the edition record.
- Blocking findings stop publish until they are fixed or an approver records a reason
- Every picture needs alt text or a decorative mark
- The check result, checker and date stay on the edition record
Report a barrier
Tell the team what stopped you, where it happened and what you were trying to do.
Note the page and paragraph
Copy the page address, the publication, edition date and paragraph reference.
Write what you tried
Write the steps you took, the device and browser you used, and whether you used a keyboard, screen reader or magnification.
Send the detail
Send the note through the Request a demo page. Add the page address and paragraph reference at the top of your message.
Keep a note of your report
Keep the date you sent the report and the page details so you can follow up if you need to.
Report a barrier or ask a question
Send the page address and paragraph reference so the team can find the exact page you read.