Grackle Docs Version Changes
There are now 19 checks.
Document Title – use the Google Doc Name in a single check
With this release we have added a single checkbox that allows the user to specify that they want to use the name of the Google Doc as the Document Title. This avoids the user having to open a dialog box and update the name in that dialog box and save. Now they just click and it’s done. The user can still use the Edit dialog box and change it if they want in the future.
Auto-Detect the Language of a Document
The language of the document is required to be specified when creating PDF. Previously we had assumed it was English and relied on the user to set it properly otherwise. One challenge we have is the google API’s don’t allow us to see what the user has set on the Google Doc through the Google Doc menu which would be ideal. So what we have added in this release is a new check for Document language. We fail on the first check until the user sets it. They can set it by clicking Edit and then setting it in the Document Properties Dialog or they can click “Detect” and this uses the Google Translate API to detect the language of the content of the Google Doc.
Changes to Tables
One Click Tagging Based on Style of Table
When a table was identified and the user wanted to tag it (even a “simple” table with a single column header and/or row header) then it still took a few clicks to select the row and mark it as a header, mark the column as a header and then associate the data cells. Now that can be accomplished with a checkbox.
See the updated table tagging dialog box.
Warn against empty cells
There was much discussion on accessibility websites where an empty cell is ok — but not an empty header — which should fail. A single empty cell is fine but not an entire row or column. For now, we created a warning for any empty cell.
Warn against merged cells
Again a lot of discussion here. Sometimes a merged cell is fine. E.G. in a Header row or column or sub header — but not in a data cell. For now, we are just warning against any merged cell.
Changed fine Print from Error to Warning
Users provided feedback that they liked the check but felt an Error on small fonts wasn’t required.
Although not officially required by standards it is considered best practice to have a single H1. There are some scenarios where multiple H1’s could make sense so we now Warn if there is more than one H1 in a document – but don’t generate an error. University of Colorado Boulder raised this and even in their group they had a disagreement on if multiple Heading 1s should be allowed so for now we are just warning about it.
Identify Suspicious Headings
One of our most common requests! Inexperienced users will often make text larger (and bold) so it looks like a heading but is not. .
We now detect text that the user may have actually intended on creating a heading but didn’t style it that way. The criteria for the flag is:
A paragraph element contains less than 50 characters and is either:
20 pixels or bigger, or
16 pixels or bigger and bold and/or italicized.
Warn against link (anchor) text that is the URL itself
The link text should not be just the URL itself. We now create a warning if the link text is the same as the URL.
E.g. www.grackledocs.com should be something like this instead GrackleDocs website
Screen readers will read all the characters of the URL instead of reading the text that describes the URL.
Accessibility Report in HTML
Click on the little circle to the right. Opens an HTML page in a new window.