At present, the only way to include images in Ultra documents is by uploading a file or including an image via URL. These images appear as full-width in the document, with a grey background, and act as links to a lightbox'ed version of the image.
There are several problems with this:
- There are many cases where images should be used inline as part of the text. Examples:
- one lecturer wants to have icons next to each heading, similar to " This week's movie", but using custom images rather than emoji.
- before and after images should be side-by-side, but should shift to above and below on a narrow screen (accessibility). No way to do this in the current interface.
- instructions such as numbered lists often include small images as part of the list.
- It's not possible to add a caption to the image/figure, which is standard and mandatory practice in all forms of academic writing, which also makes it difficult to refer to the image from within the text (such as "refer to figure 5"). It could be included as part of the image, but then that's not considered text and can't be found with Ctrl-F or read by a screen-reader.
- Clicking on the image opens it in a lightbox, which is often unnecessary (especially if the image is already shown at full size) and somewhat confusing (users think it is a link to somewhere).
- There is no way to link the image to something useful - for example, a screenshot of website that the lecturer would like students to visit.
- There is no option to browse the content collection for the image. We have an institutional library of images in our /institution directory within the content collection, but currently the only way to use it is to distribute a list of permalink URLs to people who wish to use them.
- There is no option to resize the image or edit it in any way.
All of these features are possible in Original, and they are staple parts of any web experience. While I understand that the Bb Markup Language is deliberately simplified to allow it to be presented in different ways (eg: Mobile App), the current limitations are, in my opinion, overly onerous, and in many cases substantially reduce accessibility and flexibility (1.b. and 1.c.).
|Product Version (if applicable):|