Forum Discussion
Articulate Rise to Accessible PDF
Hi SibaPrasadPadhi​ my advice would be to create your own document using Microsoft Word and then converting to PDF. In my experience, PDF is not the most accessible format for digital content. By far the most accessible for assistive technology is HTML. The next best I have experienced is MS Word.
With PDF I have experienced many problems when testing my clients documents, and also when attempting to assist in creating accessible PDF documents using Acrobat Professional.
In my experience, Rise produces accessible courses. Some things do get double announced, but that can depend on the screen reader (JAWS, NVDA, Win Narrator, TalkBack, VoiceOver) you use.
When building accessible content in Rise ensure that you refer to the Rise accessibility documentation, as it will inform you which blocks are fully accessible and which are not.
If you are reporting issues with accessibility, you need to be very specific with the issue(s) you have faced, as sometimes, it can come down to the author/testers inexperience with assistive technology and the behaviour experienced may be expected behaviour.
Here's the kind of information you should include in any (un-documented) accessibility issue that you have experienced:
- Operating System (iOS, Win, MacOS, Android)
- Browser vendor and version
- Assistive technology tested with (if applicable)
- Rise block type
- Expected outcome
- Outcome experienced
- Can it be replicated
- Screen recording if possible
This kind of information helps the developers quickly test and replicate issues you have experienced and will go a long way to getting issues corrected.
Thanks,
Sam