You can ask for one item at a time, plain text instead of a table, explicit names instead of “the former,” or complete link labels. These are requests about the answer's presentation, not proof that ChatGPT or an exported document meets an accessibility standard.
Describe the barrier you need removed
“Make this accessible” leaves the actual problem unspecified. Try “I read this linearly with a screen reader; replace the table with a heading and labeled fields for each journey.” Or say “Keep one step per numbered item and wait before giving the next group.” Choose the request that fits you; there is no single format that serves every reader.
OpenAI's prompting instructions, checked October 24, 2026, support explaining the task, audience and desired output. W3C's content structure guidance explains how meaningful structure helps assistive technologies. A requested structure still needs inspection in the actual app or document where you will read it.
Preserve the exception while changing the layout
Consider this original fictional transport notice:
North route: departs 8:10 a.m., Bay 3. South route: departs 8:25 a.m., Bay 6. On Friday only, the South route leaves from Bay 2. Arrive ten minutes before your route's departure.
A useful linear reading copy is:
North route
Departure: 8:10 a.m. Boarding bay: 3. Arrive by: 8:00 a.m.
South route
Departure: 8:25 a.m. Boarding bay: 6, except on Friday. Friday boarding bay: 2. Arrive by: 8:15 a.m.
The arrival times are derived from the supplied ten-minute instruction. The Friday exception belongs to South only. Neither the source nor the reading copy says that North moves to Bay 2. This is an authored example, not an actual transit notice or observed ChatGPT result.
Copy a request that keeps meaning intact
Restate the source below for my reading setup.
Reading setup and barrier: [DESCRIBE]
Preferred format: [E.G., PLAIN TEXT, HEADING FOR EACH ITEM,
LABELED FIELDS, ONE NUMBERED ACTION PER STEP, NO WIDE TABLE]
Preserve all names, numbers, dates, negative instructions,
conditions and exceptions. Keep each condition beside the item
it applies to. Replace unclear references with the supplied name.
Do not use color, position, symbols or images as the only way to
communicate meaning. Keep meaningful link text with its destination.
Do not invent missing information. Identify any ambiguity separately.
If you calculate a derived value, label it and show the calculation.
Return the reading copy, followed by a short list of changes I
should compare against the source. Do not claim standards compliance.
Source: [PASTE PERMITTED TEXT]
Read the revised copy using the tool you normally use. Check whether headings identify the items, labels stay with their values and the reading order remains understandable. If a field is still awkward, request a specific change rather than repeatedly asking for a generally simpler answer.
Check the information separately from its appearance
For the notice, compare both departures, both ordinary bays and the Friday exception. Verify the two arrival calculations: 8:10 minus ten minutes is 8:00; 8:25 minus ten minutes is 8:15. A concise answer that drops the exception fails the task even if its typography is comfortable.
For a real notice, keep the original source available and confirm consequential details with its issuer. If you need audio playback of an existing answer, Read aloud is a separate control. If navigating the desktop app is the obstacle, use the keyboard command guide for commands and focus conflicts.
When moving the reading copy into another document, check it there too. Headings pasted as bold text may look similar while behaving differently for navigation. Keep the version that works with your own reading setup and still preserves the source's instructions.