Overview
YuJa Panorama helps identify accessibility issues in current or future courses for available content. Tool functionality stops after the course end date. The tool guides users through certain remediation tasks, and provides alternative formats for supported course content. However, automated accessibility tools may sometimes produce unexpected results or require additional manual steps for full remediation.
Important: An accessibility score is a useful indicator, but it does not confirm that a document, course, or web page is fully accessible. Automated results should be combined with manual review and testing.
Contents
Highlighted content does not match the issue
YuJa Panorama may identify an accessibility issue without highlighting the exact word, character, object, or location that is causing the problem. In other cases, only part of the affected content may be highlighted.
This can occur when the issue involves:
- Text boxes, grouped objects, or layered content
- Formatting or structural information that is not visually apparent
- Dynamic or partially rendered HTML content
- A problem that applies to a larger section than the highlighted text indicates
Recommended action
- Review the issue description in the accessibility report.
- Inspect the surrounding paragraph, text box, image, table, or slide rather than changing only the highlighted character or word.
- Open the original document and run its built-in accessibility checker, such as the Accessibility Assistant in Microsoft Word or PowerPoint.
- Confirm the result manually whenever possible.
If the highlighted location does not appear related to the reported problem, do not make an arbitrary change solely to improve the score. When possible open the HTML view to identify the actual flagged code and apply remediation steps as expected. The HTML or source-code view may contain useful information for experienced users, but changing HTML without understanding the code can introduce new accessibility or display problems.
Return to contents
Scores differ between reports or accessibility tools
The accessibility score shown in YuJa Panorama may differ from the results shown in Microsoft Office, Adobe Acrobat, the Brightspace Accessibility Checker, or another Panorama report.
Differences may occur because the tools:
For example, an accessibility report opened from the Brightspace Rich Text Editor may not produce the same score as a report generated after the completed page is rendered and scanned in the course.
Recommended action
- Use the report to identify potential barriers rather than treating the score as a certification of accessibility.
- Confirm that each tool is reviewing the same version of the document or page.
- Review the specific issues reported instead of comparing only the overall percentages.
- Use the accessibility checker built into the authoring application before uploading a document.
- Complete manual checks for items such as keyboard access, reading order, link purpose, meaningful alternative text, and the clarity of instructions.
A higher score generally indicates progress, but a score of 100 percent does not guarantee that students will encounter no accessibility barriers.
Return to contents
Files replaced through Manage Files are not rescanned
When a document is replaced directly in Brightspace through Manage Files, Panorama may not receive a notification that the source file has changed. The accessibility report may continue to display the score and findings from the previous version.
Recommended action
- Select the Panorama Alternative Formats icon next to the affected file.
- Open the options menu.
- Select Reprocess Source File.
- Allow time for processing to finish.
- Open the accessibility report and verify that the score and issue list reflect the updated document.
When possible, replace the file through the course Content area or through the Panorama accessibility report to process the file without this additional step.
Return to contents
An issue returns after remediation
An issue may appear to be corrected but return when Panorama scans the file again. This can happen when an automated correction changes one element without resolving the underlying design problem.
For example, text placed over a gradient PowerPoint background may pass the contrast check at one location but fail after rescanning because the contrast changes across the background.
Recommended action
- Open and correct the original source document whenever possible.
- Use a solid background instead of placing text over a gradient, photograph, or patterned image.
- Move the text to an area where sufficient contrast is maintained behind the entire text element.
- Confirm color contrast with an appropriate contrast-testing tool.
- Upload the corrected source document and reprocess it.
- Attempt the automated remediation steps several times to fully resolve the issue.
If the same issue continues to return, save screenshots of the report before and after remediation and provide the source file to YuJa support team for additional insights on why the attempted resolution is failing.
Return to contents
Large files do not process correctly
Large or complex files may take longer to process or may fail to receive an accessibility score. Files larger than approximately 20 MB have been reported as particularly likely to experience processing problems.
Recommended action
- Compress high-resolution images before inserting them into Word or PowerPoint.
- Use the Compress Pictures feature in Microsoft Office.
- Remove cropped image data when it is no longer needed.
- Delete unused slide masters, embedded media, or duplicate images.
- Consider dividing an unusually long document or presentation into smaller, logically organized files.
- Reprocess the file after reducing its size.
Reducing the file size can improve Panorama processing and make the content easier for students to download, open, and use on slower connections or mobile devices.
Return to contents
Brightspace replace strings are replaced during remediation
Brightspace replace strings dynamically insert information such as a student's first name into course content. Panorama may receive the value associated with its own service account instead of retaining the original replace string.
For example, content intended to display a student's first name may display “YuJa” after automated remediation.
Recommended action
- Review remediated announcements, pages, and messages that previously contained replace strings.
- Open the content in the Brightspace editor.
- Replace the generated value with the appropriate Brightspace replace string.
- Save the content.
- Use the Brightspace preview or student view to confirm that the replace string works as expected.
Keep a copy of the original replace string before using automated remediation on content that includes personalized or dynamically generated information.
Return to contents
Accessibility reports obscure content in the Rich Text Editor
When the Panorama accessibility report is opened from the Brightspace Rich Text Editor, the report panel may cover part of the content being reviewed. The available options for resizing or repositioning the panel may be limited.
Recommended action
- Move the report between the right and left sides of the editor when that option is available.
- Close individual report sections that are not currently needed.
- Use browser zoom levels to create additional working space.
- Save the page and review the completed content outside the editor when the issue is easier to understand in the fully rendered page.
- Use the Brightspace Accessibility Checker as an additional check within the editor.
Return to contents
Understanding alternative formats
Panorama can generate alternative versions of supported course materials. Depending on the source file, available options may include:
- Tagged PDF
- Text file
- Enhanced HTML
- EPUB
- Audio
- Optical character recognition, or OCR
- Math formats
- Language translations
- Electronic braille formats
- Immersive Reader
YuJa's replace file with Alternative formats do not replace source-file remediation. The quality and usefulness of a generated format depend on the structure and accessibility of the original document. This feature is limited to converting Office source-files into PDF format, other alternative formats can not be selected.
Alternative formats are not guaranteed to be accessible alternatives, for example, generating a tagged PDF does not necessarily correct issues with the reading order, alternative text, tables, or document organization. OCR can make text in a scanned document searchable, but OCR alone does not create a fully accessible PDF.
Recommended action
- Select the format that best fits your immediate access need.
- Review generated formats before relying on them for instruction or accommodation.
- Correct the original source document when the issue can be addressed in Word, PowerPoint, or another authoring application.
- Do not allow alternative formats to delay or replace approved disability-related accommodations.
Return to contents
When requesting assistance
When reporting a problem, include:
- The specific content location
- The file name and file type
- The approximate file size
- The issue identified by Panorama
- The steps already attempted
- Screenshots, or screencast of the issue you are reporting
- The original source file, when appropriate
Providing this information will help support staff determine whether the issue involves the source document, the learning management system, or a product behavior that should be reported to YuJa.
Return to contents