Make your Instagram freebie easier to read on a phone

You made a useful guide, posted the keyword, and sent the link. Then you open it on your own phone: the cover fills the screen, the instructions are tiny, and reading the next line means dragging the page sideways.

Before you promote the resource again, give it a reading pass. Keep the design you love, but make the task easy to finish. A workshop prep sheet, packing checklist, or short tutorial should help someone do the thing your post promised.

This is about the resource after the tap. For hosting permissions and DM delivery, start with the file-sharing guide.

A printable worksheet needs space to write. A phone reader needs instructions they can follow without chasing text across a wide page. Those are different uses; you can support both.

For a short guide, consider a web page with the main instructions and an optional printable PDF. W3C's reflow guidance explains how content can adapt to a narrower view when people enlarge it. A well-built reading page can support that; check the page you actually publish, since being a web page alone does not make it accessible.

If a PDF is the right format, keep the reading path simple: a clear title, a short introduction, and one main column of instructions. Keep a detailed chart or worksheet when it serves the task, and explain its key information in text nearby.

Imagine a fictional pottery studio sharing a first-class prep guide. Instead of a cover, a long founder story, and then the instructions, open with What to bring, Before you arrive, and Where to find us. Put each instruction under the heading where a reader would look for it.

In your editor, apply actual heading styles and list tools. Making a sentence bold does not necessarily give it a heading's structure. W3C's page structure tutorial explains how meaningful headings help people navigate sections, including with a screen reader.

• BeforePlease ensure you have made the necessary arrangements regarding the provision of an appropriate garment for the session.
• AfterBring an apron or wear clothes you don't mind getting clay on.

Keep the welcome, credits, and story where they help. Ask a friend to find one answer, such as what to bring, without coaching them. Their hesitation is a useful editing note.

A screenshot of your instructions may look fine while making the words difficult to search, select, or read with assistive technology. W3C's guidance on scanned PDFs recommends actual text rather than images of text. If all you have is a scan, optical character recognition can recover text, but the result still needs checking and document structure.

Keep the original editable document. After export, try selecting a sentence and searching for a word. These are quick checks for text, not proof that the PDF is accessible.

For a photo that teaches a step, describe the detail someone needs to understand it. For example, replace Follow the arrows in the picture with the actual action in the instructions. Add appropriate image descriptions in the publishing tool too. W3C's writing guidance explains how text alternatives should convey an image's information or function.

Replace repeated Click here links with labels such as Read the prep guide, Print the checklist, or View studio directions. W3C's writing guidance recommends link text that describes the destination. Use the same names in the resource and the DM so the reader knows which version they are opening.

In DM Spark, add the reading page and hosted printable as link buttons. Use this example only if both versions exist and cover what the message promises. A link button does not create the document or fix its layout.

Run your authoring tool's accessibility checker where available, and use its tagged-PDF export option if it supports one. Tags carry document structure. W3C's PDF reading-order guidance explains that complex layouts can export in an unexpected sequence even when they look correct.

Review the exported file with a screen reader and the tool's reading-order view where available. Check whether headings, instructions, and image descriptions come in a sensible sequence. Use the keyboard to move through links and confirm their order. A read-aloud feature can reveal awkward sequencing, but it does not replace a screen-reader and structure check.

Finally, open the real DM link on a phone while signed out of the hosting service. Read a complete section, enlarge the text, and use each link. Look for text that disappears, columns that overlap, or instructions that require repeated side-to-side dragging. Test the printable separately. Neither a visual pass nor an automated checker covers every accessibility need, but each can reveal a fix you can make before sharing.

Resource and version date:
The task this resource helps someone finish:
Reading version opens without an account:
Main steps are readable on a phone:
Headings and lists use the editor's structure tools:
Text can be selected and searched:
Images have useful descriptions where needed:
Links describe their destination:
PDF reading order checked after export:
DM buttons match the reading and print versions:
One confusing step to fix before sharing:

Start with the resource people request most often. Fix the first obstacle you find, export again, and test that version. A clear guide earns its place in the DM by being useful when someone opens it.