Skip to content

13 508 Accessibility Compliance

Jump to bottom
Em Markowitz (NOAA) edited this page Dec 9, 2021 · 7 revisions

From past meetings:

Requirements

The "Big 5" list (“the bare minimum”)

List from NOAA library that will be used by John DeVore for checking assessment reports submitted to the Pacific Fisheries Management Council:

  • Tagged content: The PDF is a tagged PDF. Auto-tagging is acceptable. If this step is not done, no other elements will pass because they rely on tagging elements. List of Standard PDF tags from Adobe. https://helpx.adobe.com/acrobat/using/editing-document-structure-content-tags.html#standard_pdf_tags
  • Bookmarks: Bookmarks are present on documents over 20 pages and illustrate the structure of the document. If a Table of Contents is present, bookmarks should reflect this.
  • Alternative Text: Alt text is present for all figures, charts, maps, equations, etc.
  • Logical reading order: The reading order of the elements is logical and follows the flow of the document.
  • Document properties: Title and language are present. These features are metadata, where Adobe provides resources about creating and editing document metadata. https://helpx.adobe.com/acrobat/using/pdf-properties-metadata.html

Comprehensive list of features of accessible documents

  • correct tags to all text elements
  • structurally correct headings 1-6
  • each paragraph is marked as single paragraph
  • listings marked as (interlaced) lists
  • table headers defined for data tables
  • the documents correct reading sequence can be identified
  • alternative texts is present for charts and images
  • layout graphics and headers and footers are in the background
  • document has the correct language assigned
  • define language changes within the document
  • bookmarks are available for easier navigation
  • security settings are defined such that they don't block assistive technologies, best to not have security at all
  • field labels for all form fields
  • internal and external references are defined (clickable links and indexes)
  • correct assignments of foot notes
  • reading by means of text flow

What documents need to be Section 508 compliant?

More info on alternative text

How descriptive should it be? Info on alternative text for complex images https://www.w3.org/WAI/tutorials/images/complex/

Solutions and information

Assorted links to info online

Resources

Example Repos:

  • NWFSC:
    • Kelli Johnson, Aaron Berger, Chantel Wetzel, Andi Stephens, and Ian Taylor are all using using markdown, knitr, or latex for stock assessment reports
    • Erin Steiner automated the creation of Economic Data Reports but now that it’s all online with FISHEyE, had planned to write unformatted tech memos to word and let Al Brown (NWFSC Technical Editor) handle the formatting, but would prefer to use Rd or Rmd. https://www.fisheries.noaa.gov/west-coast/science-data/economic-data-collection-reporting
    • Nick Tolimeri
  • SWFSC:
  • AFSC:
    • Jim Ianelli is working on this presumably along with the folks to whom he forwarded an email on the subject (including the S&T folks below): Ben Williams, Cole Monnahan, Ingrid Spies
    • Josh London with NMML has a package that does some accessibility stuff but not full 508 compliance (https://github.com/jmlondon/uswebr) - will be presented via August 13th FIT meeting (contact Corinne Bassin to attend) S&T National Modeling Team
    • Christine Stawitz and Corinne Bassin are thinking about this stuff on a national level and across assessment platforms
  • West Coast Region
    • Stacey Miller is coordinator for the Pacific Whiting/Hake treaty and working with Aaron and Kelli (above) and their Canadian counterparts to make all documents posted to the regional website compliant
  • NEFSC
    • Dan Hennen hired a contractor (Tom Price) to make their reports 508 compliant - sounds like they have a working model and are working on creating a package (pending funding?): https://tug.org/tug2020/preprints/Price-Moore-AccessibleTikZ-slides.pdf
    • Andy Beet (EDAB) has been working on making markdown/rmarkdown docs 508 compliant. Focus has been on alt text for images. Many documents (markdown/Rmarkdown) created in EDAB have many images. Converting to word via a reference doc, then to pdf solves the alt text problem (But it’s an ugly process)
  • Other
    • Rmarkdown/latex combination with source code and data for Bering Sea pollock: https://github.com/afsc-assessments/EBSpollock
    • Assessment template (very minimal and I am working on updating it with the latest commits so give me a week) but creates a tagged pdf with alt text github.com/nwfsc-assess/sa4ss

Creative Commons v1.0 Universal license

Clone this wiki locally