You can install Grackle Docs here.
When opened, it scans the current document for accessibility issues.
When the scan finishes, Grackle Docs arranges the document’s elements and structures into categories.
These categories can be seen in the user interface on the right side of the screen.
Elements in each are marked as either accessible or inaccessible. Changes are made by selecting and editing these elements in these categories. For example, a table does not have the header row specified with a tag. When an element is changed with Grackle Docs, it edits the tags for that element in the document. This edit is immediate and no saving is required.
Document properties are primarily useful when exporting to tagged, GrackleDocs PDF
Grackle checks for compliance against several accessibility requirements.
Also called “alt tags” and “alt descriptions,” alt text is the written copy that should appear with an image, drawing or equation on a document to help screen-reading tools describe images.
Grackle Docs also flags images that appear to be using their filename as an alt-tag, rather than robust descriptions.
Grackle checks against three accessibility requirements related to headings.
Grackle counts both the highest heading value reached and the number of paragraphs with heading styles.
Pro-tip: Headings should follow a logical order. An H2 heading should follow H1, and should be followed by H3.
Tables are common in corporate and academic documents and are commonly inaccessible.
They pose a special challenge for screen readers because they present textual or numerical data to be easily referenced visually.
A Google Doc does not have the concept of a datas table and represeents a table as a grid without mark up. Once Grackled, this grid turns into a fully functioning, marked up table within PDF.
Grackle visualizes the fields in each table to help the user tag headers and columns.
Grackle checks for three features that help accessibility users recognize and transit the document.
Grackle scans against and helps resolve five (7) content-related accessibility issues.
