Ally Module Report
The Ally Module Report refers to the issues that Ally can identify. The table below provides guidance and tips on how these issues can be resolved.
The Ally support site also contains additional helpful guidance on how to tackle the issues identified by Ally.
Issue | Severity of Issue | Additional Information/Possible Remedial Action & Tips | Web Accessibility Guidance |
---|---|---|---|
Langage not specified on number of items | Minor Issue | Number of items that don’t have a language specified. Ally picks up the dominant language and will flag here if it does not match the language set for the document (a flag here may be ignored for bilingual docs). Language detection is usually on by default – if Ally suggests it’s the wrong language (and you agree), you can select the text and then select the correct language as described in Microsoft's automatic language guidance. Turn on automatic language detection on Microsoft's support site | |
Incorrect language set on number of items | Minor Issue | Ally picks up the dominant language and will flag here if it does not match the language set for the document (a flag here may be ignored for bilingual docs). Language detection is usually on by default – if Ally suggests it’s the wrong language (and you agree), you can select the text and then select the correct language as described in Microsoft's automatic language guidance. Turn on automatic language detection on Microsoft's support site | |
Empty headings in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Headings and labels WCAG 2.1 |
Form elements without labels in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
No headings in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Headings and labels WCAG 2.1 |
Object tags without alternative text in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Poor colour contrast in HTML and WYSIWYG content | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Contrast minimum WCAG 2.1 |
Table columns without proper header in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Info and relationships WCAG 2.1 |
HTML content and files that have table columns without proper a proper header | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Recommended H6 levels exceeded in PDF or presentation or document | Minor Issue | Number of PDFs, presentations, and documents that exceed the recommended H6 level of headings. HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Using H1 - H6 to identify headings WCAG 2.1 |
No title in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Headings not used in logical sequence in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
HTML content and files not properly defined with labels and p | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Language presence not identified in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Links are not descriptive in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Lists not properly formed in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Same alternative text as other images in HTML content and files | Minor Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
PDFs that are scanned and have been OCRed | Major Issue | OCR is ‘optical character recognition’ - whilst better than a scanned PDF, screen readers will not pick up on document structure. | |
Items that have tables without headers | Major Issue | Add Headers to Document Data Tables on Ally's support site | |
H1 not used as first heading in PDF or document | Minor Issue | Number of PDFs and documents that don’t have an H1 heading as the first heading. See. Add Headings to a Word Document on Ally's support site | Using H1 - H6 to identify headings WCAG 2.1 |
Headings not in logical sequence in PDF or documents | Minor Issue | Add Headings to a Word Document on Ally's support site | Organising a page using headings WCAG 2.1 |
No headings in PDF or presentations or documents | Major Issue | See Add Headings to a Word Document on Ally's support site. For PPT files there is a known issue. Ally flags there should be headings – in fact slide titles likely need to be added. In the title a slide guidance on Microsoft support site, refer to how to use the accessibility ribbon to title a slide can help. | Headings and labels WCAG 2.1 |
PDFs that are not tagged | Major Issue | How to tag a PDF on Ally's support site | |
Images that contain text | Minor Issue | The text would need to be entered in the alt description field to be accessible. | |
Images that are not marked as decorative | Major Issue | This relates to images directly uploaded to Minerva rather than in a doc/ppt etc. Ally advise that these are the same issue i.e. an image does not have an alt description AND is not marked as decorative (it should have one or the other). Therefore you only need to check one of these columns. See, Add Image Descriptions on Ally's support site | |
Images with poor contrast | Major Issue | This relates to images directly uploaded to Minerva rather than in a doc/ppt etc. Improving contrast may not always be possible to change e.g. photos of art. Where you are constructing images, aim for the starkest contrast possible. Sites such as Colour Contrast Checker can be used to show which combinations pass accessibility standards (aim for Pass across the AA/AAA Large/Normal categories). | Contrast ratio WCAG 2.1 |
Items without a title | Minor Issue | This relates to PDFs. If you have the source document, the title can be added there. See, Microsoft's guidance on adding a title by viewing or changing the properties of a file. | |
Items that can be improved by library references | Guidance | This is not an accessibility issue but flags items that could be improved by the use of an Ally tool called Library Reference. Note: Ally acknowledge this report counts all file types but you can only add library reference information to a PDF. See, How to add a library reference on Ally's support site | |
Appropriate H heading not used first in HTML content and files | Major Issue | Number of HTML content and files that don’t have the appropriate H heading as the first heading. HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Using H1 - H6 to identify headings WCAG 2.1 |
No captions on YouTube videos in content and files | Major Issue | Number of HTML content and files that have YouTube videos without captions. HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | Captions pre-recorded WCAG 2.1 |
Alt text not used | Major Issue | Number of images that don't have an alternative description. This relates to images directly uploaded to Minerva rather than in a doc/ppt etc. Ally advise that these are the same issue i.e. an image does not have an alt description AND is not marked as decorative (it should have one or the other). Therefore you only need to check one of these columns. See, Add Image Descriptions on Ally's support site | |
At least one image with no alternative text in PDF or presentation or document | Major Issue | Add Image Descriptions on Ally's support site | Apply text alternatives WCAG 2.1 |
At least one image without alternative text in HTML content and files | Major Issue | HTML issues can only be resolved with someone comfortable with HTML. HTML users can find support for HTML coding on the w3schools website | |
Contrast issues in PDF or presentation or document | Major Issue | Aim for the starkest contrast possible. Sites such as Colour Contrast Checker can be used to show which combinations pass accessibility standards (aim for Pass across the AA/AAA Large/Normal categories). | Contrast minimum WCAG 2.1 |
Broken links in pages in a domain | Major Issue | ||
Items that are malformed and may not open | Severe Issue | Number of items may be malformed or corrupted and students may not be able to open them. A corrupt file will likely need to be recreated. | |
Images that can cause seizures | Severe Issue | These will need to be removed. | Seizures and physical reactions WCAG 2.1 |
Items that require a password | Severe Issue | Files should not require a password to open. | |
PDFs that are scanned and have been OCRed | Severe Issue | See the Ally Support Site for advice on Scanned PDFs. | OCR on a scanned PDF WCAG 2.1 |