QUILL Lite Tutorials
Welcome. There are 54 short lessons here, about 306 minutes in all, and you can take them in any order. Each one is a few small steps, and each step tells you what to press and what you should hear.
This page is the lessons written out, so you can read them anywhere. If you would rather be walked through, open Help > Tutorials… (Ctrl+Alt+F1) in QUILL Lite. It does a step for you when you ask, and moves on by itself once it hears you have done one.
The keys here are the ones QUILL Lite comes with. If you have changed a key, the lessons inside the app use your key; this page cannot know about the change.
Contents
- Your first documents: Start here. Open a file and
save it back unchanged, find out where the facts about it live and what
kind of document you are in, and move between the documents you have
open.
- Open a file, and give it back unchanged (5 minutes)
- Four kinds of document, and how to say which (4 minutes)
- Your documents are numbered (3 minutes)
- What to press when you are lost (3 minutes)
- Working in a document: Once you are comfortable:
select more than a few words, find your way back to where you were, skim
something long, fix spelling without a red squiggle, ask a question
about the document in front of you, and write by talking or transcribe a
recording.
- Selecting more than a few words (6 minutes)
- Finding your way back (5 minutes)
- Skimming something long (5 minutes)
- Spelling, without a red squiggle (5 minutes)
- Asking a question about a document (6 minutes)
- Write by talking (6 minutes)
- Punctuation and symbols by voice (5 minutes)
- Fix a word by voice (5 minutes)
- Snippets and clips by voice (4 minutes)
- Switch to Spanish and back (3 minutes)
- Make a live transcript (4 minutes)
- Transcribe a recording (5 minutes)
- WordPress: If you look after a WordPress site:
connect it, write and publish a post, fix a page you found by its
address, pictures with alternative text, the check before you publish,
earlier versions, and comments.
- Connect your WordPress site (5 minutes)
- Write a post and publish it (6 minutes)
- Open a page by its address and fix a sentence (5 minutes)
- Pictures with alternative text (6 minutes)
- Check Before Publishing (5 minutes)
- Go back to a previous version (5 minutes)
- Answer comments (5 minutes)
- Your first week with a site: For a new site owner:
one short lesson a day for seven days, on your own site, each ending
with something real – and nothing happens that you did not choose.
- Day 1: Connect your site (5 minutes)
- Day 2: Save a draft on your site (6 minutes)
- Day 3: Describe one picture (6 minutes)
- Day 4: Fix one thing the check finds (8 minutes)
- Day 5: Answer your comments (6 minutes)
- Day 6: Look after your menu (6 minutes)
- Day 7: Publish when you are ready (7 minutes)
- The WordPress Workbench, on the Practice Site:
Start a WordPress site on this computer, change a post there, read
Change History, undo, and reset the site – all with nothing real at
stake.
- Start the Practice Site (6 minutes)
- Change a practice post, then undo it (6 minutes)
- Reset the Practice Site (4 minutes)
- Look after a site (10 minutes)
- Change a menu, then put it back (7 minutes)
- Add a person and choose their role (7 minutes)
- Update plugins safely (8 minutes)
- Spam, real comments, and challenges (7 minutes)
- Custom types and their fields (7 minutes)
- From staging to live, without surprises (8 minutes)
- Across sites with a Site Set (6 minutes)
- Break It on Purpose, on the Practice Site: Four
problems put on the Practice Site on purpose – a missing alt text, a
broken link, a plugin conflict and a wrong address – and how the
Workbench finds and fixes each one.
- Set up the broken Practice Site (4 minutes)
- Fix a picture with no alt text (5 minutes)
- Fix a broken link (7 minutes)
- Fix a plugin conflict (6 minutes)
- Fix a wrong address (6 minutes)
- Forms: Start a form from a template, add questions
and a rule, check it, fill it in yourself, save it in large print or
braille, and publish it to your site and read the responses.
- Start a form from a template (5 minutes)
- Add questions (5 minutes)
- Add a rule and hear it as a sentence (5 minutes)
- Check This Form (4 minutes)
- Fill It In Yourself (5 minutes)
- Save it as large print or braille-ready text (4 minutes)
- Publish it and read the responses (7 minutes)
- Coding, in the Developer profile: Work on a folder
of code with an AI: ask for a change, review every edit, allow the
commands it runs, hear the test results, and undo a whole turn.
- Your first project task (12 minutes)
Your first documents
Start here. Open a file and save it back unchanged, find out where the facts about it live and what kind of document you are in, and move between the documents you have open.
Open a file, and give it back unchanged
Start here. You open a file you already have, hear the three things QUILL Lite remembers about it, and save it back exactly as it was.
5 steps, about 5 minutes.
Open something you already have. Pick any text file you already have. An older one is a good test. QUILL Lite opens plain text, Markdown, HTML and rich text, so whatever you choose will be fine.
- Keys: Ctrl+O
- You should hear: The file’s name, and the first line of it.
Look at what it remembered. Now go to the status bar. It is a row of cells, and you move along it with the arrow keys. Listen for three of them: Encoding is how the letters are stored, Line Endings is how each line finishes, and Format is the kind of document. QUILL Lite keeps all three just as it found them.
- Keys: F6
- You should hear: Each cell’s name and its value as you arrow along.
- Worth knowing: Press Escape to go back to your document. Looking around is safe: nothing changes unless you press Enter on a cell and answer the question it asks.
Save it without changing anything. Save the file straight back without typing anything. If you like, compare it with a copy of the original afterwards. You will find they are the same, byte for byte.
- Keys: Ctrl+S
- You should hear: “Saved” and the file’s name.
Find it again later. QUILL Lite remembers what you open. Open the Recent Documents window and your file is at the top of the list. Next time, press Enter on it instead of hunting for it with Open. Alt Shift 1 reopens the newest one without opening the window at all.
- Keys: Alt+Shift+0
- You should hear: The Recent Documents window, on your file’s name and its folder.
- Worth knowing: Press Escape to close the window. Pin, in the same window, keeps a file you use often at the top for good.
Type a character the file cannot hold. This one is optional. If your file uses an older encoding, type an em dash or an emoji and save again. QUILL Lite stops and asks you first: save as UTF-8 and keep the character, save as it was and lose it, or cancel. You decide.
- You should hear: A question counting the characters, naming the encoding, and offering Yes, No and Cancel.
- Worth knowing: Not sure which encoding your file uses? The Encoding cell in the status bar tells you.
That is the heart of QUILL Lite. Your file comes back the way you left it, and everything else is built on top of that.
Next: Four kinds of document, and how to say which.
Four kinds of document, and how to say which
Plain text, Markdown, HTML and rich text: what each one means for you, and the one key that moves between them.
4 steps, about 4 minutes.
Find out what you are in. Go to the status bar and arrow to the Format cell. It tells you which kind of document this is. QUILL Lite guesses from the file’s name, and you can always change its mind.
- Keys: F6
- You should hear: The Format cell, reading “Markdown”, “HTML”, “Plain text” or “Rich text”.
Ring through the four. One key steps through all four kinds, and each one says its name as you land on it. Keep pressing until you hear the one you want. Moving between plain text, Markdown and HTML does not touch your words. It only changes what the formatting keys type from now on.
- Keys: Alt+Shift+F
- You should hear: Each kind naming itself as you land on it.
Go into rich text, and come back. Rich text is the one stop that really converts. Going in turns Markdown into real bold, headings and lists. Coming back out turns them into Markdown again, and QUILL Lite asks you first, naming anything it cannot carry across.
- You should hear: A question before it converts, then “Rich text mode” or “Plain text mode”.
- Worth knowing: Your file keeps its name. A rich document cannot be saved over a .txt file, so the next Ctrl+S offers you the right ending already filled in.
Say otherwise, for this window only. Sometimes you want to write HTML in a scratch .txt file, and that is fine. Document Language lets you pick the kind yourself, and tells you what each choice will do before you choose. Your choice lasts as long as this window is open.
- Keys: Ctrl+Alt+F6
- You should hear: Each option described, and the one the file name would have chosen marked.
Now you know what kind of document you are in, and how to change it when QUILL Lite guessed wrong.
Next: Your documents are numbered.
Your documents are numbered
Instead of tabs, every open document gets a number. Here are the ways to get to the one you want.
3 steps, about 3 minutes.
Open a second file. It opens inside the same window, as document 2. A number is easy to remember and easy to say: “document 3” is much clearer than “the other Untitled”.
- Keys: Ctrl+O
- You should hear: The new document’s number and name, in its title.
Walk between them. Ctrl+Tab is what most people press, and Ctrl+F6 is the key Windows uses for this. Both work. The Window menu lists them too.
- Keys: Ctrl+Tab
- You should hear: The document you arrive at, announcing its number and name.
Go straight to one. Hold Alt and press a document’s number to go straight to it. Once you have more than two open, this is the quickest way around, and it is why they have numbers.
- Keys: Alt+1, Alt+2, Alt+3
- You should hear: The document you asked for.
- Worth knowing: Your documents all live inside one QUILL Lite window, so they do not appear in Alt+Tab. Use the keys in this lesson to move between them instead.
Open as many as you like. Each one has a number, and Alt with that number takes you straight there.
What to press when you are lost
Three keys that tell you where you are, what something does, and what QUILL Lite can do.
3 steps, about 3 minutes.
Ask what you are standing on. F1 works everywhere: in your document, on a button, in any window. It tells you what the window is for, and then what the thing you are on does.
- Keys: F1
- You should hear: The window’s purpose, then the control’s.
Ask what the facts are. The status bar holds everything QUILL Lite knows about your document, plus the last thing it said. Missed a message? It is waiting in the last cell, Status Message. Press End to jump there.
- Keys: F6
- You should hear: “Status bar” and the cell you land on, then each fact as you arrow.
Ask what exists. The Keyboard Shortcuts window lists every key QUILL Lite has. It shows your keys, including any you have changed, and you can type part of a name to find one.
- Keys: Ctrl+F1
- You should hear: A searchable list of every command and its key.
Whenever you are unsure, one of these three keys will explain where you are.
Working in a document
Once you are comfortable: select more than a few words, find your way back to where you were, skim something long, fix spelling without a red squiggle, ask a question about the document in front of you, and write by talking or transcribe a recording.
Selecting more than a few words
Three different ways to select a stretch of text without seeing it, and when each one is the easiest.
6 steps, about 6 minutes.
Take a whole thing in one key. If what you want is a whole word, line, sentence, paragraph or block, there is a key for it. You do not need to find where it starts. Try it now on the paragraph you are in.
- Keys: Ctrl+Shift+H
- You should hear: “Selected paragraph”, and how many words that was.
Grow and shrink. Starting from whatever you have, you can grow the selection one step at a time: word, line, sentence, paragraph, block, then everything. You can shrink it back the same way. Each step tells you what it took.
- Keys: Ctrl+Shift+X
- You should hear: The new scope, and its word count.
Mark a spot and walk to the end of it. For anything that is not a neat word, line or paragraph. Drop a marker where the selection should start. Then move any way you like, with the arrows, Find, Go To Line or a bookmark. You do not have to hold any key down while you go.
- Keys: F8
- You should hear: The line and column where the marker went down.
Finish it, and hear how far it reached. When you reach the end, finish the selection. Everything between the marker and where you are now is selected. You can even use Find on the way, and it will not spoil it.
- Keys: Shift+F8
- You should hear: How many words, and the lines it ran between.
- Worth knowing: Hearing the line numbers is a quick way to check you caught the stretch you meant.
Or hold the Shift down without holding it. Here is a third way. Turn on Extend Selection Mode, and every arrow key selects as it moves, just as if you were holding Shift. Your screen reader does not say “selected” on every press, either. Turn it off the same way when you are done.
- Keys: Alt+Shift+F9
- You should hear: “Extend selection mode on”, and where it started.
Check what you have before you replace it. Before you type over a selection, it is worth checking it is the one you meant, because the next key you type replaces it. Say Selection reads it back to you. A long one is summed up instead of read in full.
- Keys: Ctrl+Shift+Y
- You should hear: The selection, or a summary of it with its size.
Lost a selection by accident? Reselect Last Selection puts it back, however you made it.
Next: Finding your way back.
Finding your way back
Bookmarks, marks and Go Back. They sound alike, but each one helps you in a different moment.
4 steps, about 5 minutes.
Keep a place you mean to come back to. You have nine numbered bookmarks in every file, and they are still there tomorrow. A bookmark stays with its words, so if you add three paragraphs above it, it is still on the right line.
- Keys: Ctrl+Shift+1
- You should hear: The bookmark’s number, and the line it went on.
Drop a pin you will forget. A mark is quicker and lighter. It just remembers where you were before you went to look something up. There is no number and no list. Pop Mark takes you back and then forgets it.
- Keys: Ctrl+Shift+M
- You should hear: The line, and how many marks you now have.
Go and look something up, then come back. Move a long way off. Ctrl+End, the end of the document, will do. Now pop the mark, and you are back where you were.
- Keys: Ctrl+M
- You should hear: The line you came back to, and how many marks are left.
Undo the jump. Go Back works like the Back button in a web browser. Every jump in QUILL Lite can be undone with it: bookmarks, marks, headings, Go To and search results. So you can always get back to where you were.
- Keys: Alt+Left
- You should hear: Where you were before the jump.
- Worth knowing: This is handy after following a heading. One key brings you back to the paragraph you were writing.
Bookmarks are for places you will come back to tomorrow. A mark is for right now. Go Back is for any jump you did not mean.
Next: Skimming something long.
Skimming something long
Get a feel for a long document the way a sighted reader does by scrolling, using its headings instead.
5 steps, about 5 minutes.
Ask for the shape. The headings list shows every heading in the document, in order. Each one tells you its level and its words. Press Enter on one to go there.
- Keys: Ctrl+Alt+L
- You should hear: Each heading, with its level.
Walk it instead. Next Heading and Previous Heading move from heading to heading instead of line by line. Each time you arrive, you hear the level and the words.
- Keys: Ctrl+Alt+H
- You should hear: “Heading 2”, and the heading’s words.
Skim by section. Moving by section tells you the heading, whether it is folded, and how many lines are under it. That last part is your glance. It tells you a section is huge without reading any of it.
- Keys: Ctrl+Alt+Shift+Down
- You should hear: The heading, its state, and its size in lines.
Mark one as dealt with. Folding a section is a note to yourself that you are done with it. Nothing is hidden: your cursor still goes in and Find still finds things there. You just hear that it is folded as you pass.
- Keys: Ctrl+Shift+F9
- You should hear: How many lines went with it.
Rearrange it, if the shape is wrong. The Heading Organizer shows every heading as one list. Tab makes a heading one level lower, Shift+Tab one level higher, and Move Up and Move Down carry the heading along with everything under it.
- Keys: Alt+Shift+O
- You should hear: Each heading as you arrow, with a preview of its section.
- Worth knowing: Nothing changes until you press Apply, and one Ctrl+Z puts it all back.
With headings, a long document becomes something you can move around in quickly, a section at a time.
Spelling, without a red squiggle
How QUILL Lite lets you know a word looks wrong without breaking into your sentence, and the one key that fixes it.
4 steps, about 5 minutes.
Type something wrong, and keep going. Type a word wrong on purpose and carry on. A moment after you finish the word, the status bar notes that it may be misspelled. Nothing is spoken over your typing, so you can finish your thought first.
- You should hear: Nothing, unless you asked for a sound or a sentence in Preferences.
Fix the word you are standing in. The Applications key is your red squiggle. Put the cursor in the word and press it. The first Down arrow lands on a suggestion. Press Enter to use it. Your cursor stays put and no dialog opens.
- Keys: Applications, Shift+F10
- You should hear: The suggestions, in order, as you arrow.
- Worth knowing: Everything else you can do with the word, like ignore it, add it, or go to the next or previous one, is in the same menu just below the suggestions.
Teach it a word. You can add a word to your own dictionary, and it is known for good. Or add it to the document’s dictionary, which travels with that file, so anyone who opens it gets the word too. That suits a product name better than your surname.
- You should hear: Which of the two it was added to, by name.
Check the whole thing. F7 goes through the document one word at a time. It starts where your cursor is, and when it reaches the end it offers to carry on from the beginning.
- Keys: F7
- You should hear: Each word, its suggestions, and a summary of what changed at the end.
One more thing: spelling stays quiet in program code and settings files, whatever your settings say, so you are not told about every made-up name in them.
Asking a question about a document
AI help is the one feature that sends anything off your computer. Here is how to turn it on, what is sent when you use it, and what it will not do.
5 steps, about 6 minutes.
Turn it on, and agree to it separately. AI help stays off until two things are true: the feature is switched on, and you have said yes to the privacy agreement. These are two separate steps, so nothing is ever sent just because a profile, a settings file or someone else switched the feature on. Only your own yes counts.
- Keys: Ctrl+Alt+Shift+K
- You should hear: The agreement, read out in full before you are asked.
- Worth knowing: You can reach the agreement three ways: this command, a check box in Preferences, or switching AI help on in Customize Features. You can always open it to read it, whether or not you have agreed.
Connect this computer, once. There is no account, no password and no email address. You are given an eight-character code. Open the web page on anything with a browser, this computer or your phone, and type the code in. Asking for the code is the first moment anything is sent.
- Keys: Ctrl+Alt+Shift+F10
- You should hear: The code, character by character, and the window confirming in place rather than opening another one.
- Worth knowing: Each computer connects on its own. Signing one out leaves the others connected.
Ask about what is in front of you. Type a question about the open document, like ‘what does this say about the deadline’. The answer comes back along with the part of the document it came from, so you can go and read that part yourself.
- Keys: Ctrl+Alt+Z
- You should hear: The passages it chose, before anything is sent, and then the answer.
- Worth knowing: Long documents are fine. It does not send the whole file. It picks the three passages most likely to answer you and sends only those.
Or hand it a job. The AI pad has five rows. Four of them work on what you have selected, or on the paragraph or section you pick with Send this much: summarize it, rewrite it clearer and shorter, proofread it, or explain a tricky passage. The fifth is the question you just asked. Nothing changes in your document by itself. The answer comes with Replace My Selection, Insert Below and Copy underneath, and you choose.
- Keys: Ctrl+Alt+G
- You should hear: What is about to be sent, before it goes.
Know what you have left. The service is free, so it has limits. One question can carry about two thousand two hundred and fifty words of your document, and you get a hundred requests a month. If what you asked about is too big, you are told in plain words before anything is sent, so you can select less and try again.
- Keys: Ctrl+Alt+Shift+F9
- You should hear: What you have used and what is left.
- Worth knowing: The limits can change from time to time. Usage always shows the numbers that apply to you right now.
What is kept is how many requests you made and how big they were. What you wrote, and what came back, is not kept.
Write by talking
Dictate a few sentences into a document, take one back, turn it off, and find the settings. Everything stays on your computer.
6 steps, about 6 minutes.
Start dictation. Put the cursor where the words should go, and turn dictation on. The first time, it takes a second or two to get ready.
- Keys: Ctrl+F11
- You should hear: Two rising tones, and “Dictation on”.
Say a sentence, and pause. Talk the way you would to a friend, then stop for a moment. You do not need to say the punctuation: full stops, commas and capitals are put in for you.
- You should hear: A soft tone, then the words that were written, read back with their punctuation said.
Take a phrase back. Say scratch that, on its own, after a pause. Only the last phrase you said goes; anything you typed is left alone.
- You should hear: “Scratched:” and the words that went.
Turn it off with the same key. Press the dictation key again to turn it off. One press starts dictation and the next stops it, and stopping never cuts off a sentence you are still finishing.
- Keys: Ctrl+F11
- You should hear: Two falling tones, and “Dictation off”.
See the phrases you said. Recent Phrases lists what you dictated this session, newest first. Enter writes one at the cursor again, which rescues a scratch that that went one too far.
- Keys: Shift+F11
- You should hear: Recent Phrases, on the newest phrase.
Find the settings. Dictation Settings has the speech engine, the microphone and what you hear after each phrase. Moonshine, the engine it starts with, needs nothing downloaded. Better Accuracy: Speech Models offers larger models and recommends one for this computer. More Dictation Settings, inside it, lets you hold the key to talk if you prefer, and has the words heard while you speak and talking to the AI.
- Keys: Alt+Shift+F6
- You should hear: Dictation Settings, on Speech engine.
- Worth knowing: Nothing you say leaves the computer unless you choose OpenAI with your own key, or a speech provider you set up with your own account in Speech Providers, and agree to it.
You can now write by talking, take back a phrase, and turn dictation on and off with one key. Say what can I say while dictating to hear everything it understands; the user guide’s dictation chapter has the rest.
Punctuation and symbols by voice
Say punctuation, start a bulleted list and a heading, and spell a web address, and hear every mark read back so you know it went in.
4 steps, about 5 minutes.
Start dictation. Open a new document, so nothing you care about is in the way, and turn dictation on.
- Keys: Ctrl+F11
- You should hear: Two rising tones, and “Dictation on”.
Say a sentence with its punctuation. Say: dear Sam comma thank you for the letter period. Then pause. Saying a mark always wins over the one the engine would add.
- You should hear: Dear Sam comma thank you for the letter period.
- Worth knowing: The marks are read back by name whatever your screen reader’s punctuation level is. Say punctuation marks in the read-back, in More Dictation Settings turns that off.
Start a heading and a list. Say heading two, then the heading’s words, and pause. Then say bullet and an item. These marks count only at the start of what you say, so ordinary sentences are never turned into lists.
- You should hear: Hash sign hash sign, then your heading; hyphen, then your item.
Spell a web address. Say spell, then the letters with dot and at sign between them: spell sierra alpha mike at sign echo dot charlie oscar. Spelling writes punctuation with no spaces.
- You should hear: The address, read back with its marks.
Say what can I say at any time for every mark and symbol, including the Markdown ones: backtick, vertical bar and block quote.
Fix a word by voice
Find words you said earlier, select them or put the cursor beside them, and correct them without touching the keyboard.
4 steps, about 5 minutes.
Dictate a couple of sentences. Turn dictation on and say two short sentences, pausing after each, so there are words to find.
- Keys: Ctrl+F11
- You should hear: Each sentence read back.
Select a word you said. Say select, then a word from the first sentence. The nearest one before the cursor is found first, because that is usually the one you are fixing.
- You should hear: “Selected:” and the words.
Say the right word. Just say the word you meant. What you say next replaces the selection, in one step that Undo or scratch that takes back.
- You should hear: The new word read back.
Correct and spell a name. Say correct and a name the engine got wrong, then spell it, or say spell that straight after dictating it: the letters you say next replace it.
- You should hear: “Correcting” and the words, then the spelled word.
- Worth knowing: If the words are not in the document, what you said is written as text and you hear Not found, written as text. Scratch that removes it.
Go to and go after put the cursor beside words instead of selecting them, and select again moves on to the next place the words appear.
Snippets and clips by voice
Copy the whole document, paste a Copy Tray slot and put in a snippet, all by saying so.
3 steps, about 4 minutes.
Copy the whole document. With dictation on, say copy all. Nothing is selected, so nothing can be typed over by accident.
- Keys: Ctrl+F11
- You should hear: “Copied the whole document” and how many characters.
Paste a slot from the Copy Tray. Say paste clip and a slot number, like paste clip one. It goes in as one phrase, so scratch that takes it out again.
- You should hear: “Pasted slot 1”, or that the slot is empty.
Put in a snippet by name. Say insert snippet and its name. If more than one snippet matches you hear how many, and the list opens so you can choose.
- You should hear: “Snippet” and its name.
Say show clips or show snippets to open either list by voice.
Switch to Spanish and back
Move between English and Spanish dictation without opening a window.
2 steps, about 3 minutes.
Switch the language. Use Switch Dictation Language. The choice is remembered, so the next time you dictate it starts in the language you used last.
- Keys: Ctrl+Shift+F11
- You should hear: “Español”.
Come back by voice. While dictating in Spanish, say cambiar a inglés. In English, say switch to Spanish to go the other way.
- You should hear: “English”.
- Worth knowing: The first switch can take a moment while the Spanish model loads; after that it stays ready for the session.
Dictation Status tells you which language and engine are in use.
Make a live transcript
Write down a talk or a meeting as it happens, in its own document, while you keep working.
3 steps, about 4 minutes.
Start a live transcript. A new document opens and everything the microphone hears is written into it, quietly. Please record other people only when they have agreed.
- Keys: Ctrl+Alt+Shift+PageDown
- You should hear: “Live transcript on, in a new document”.
Ask how it is going. Use Dictation Status at any time; the status bar and a braille display show the same thing.
- Keys: Alt+F9
- You should hear: How many minutes and how many words.
Stop and save. Use the same command again to stop. The document stays open, unsaved, for you to name.
- Keys: Ctrl+Alt+Shift+PageDown
- You should hear: “Live transcript stopped” and the number of words.
Time stamps in live transcripts, in More Dictation Settings, puts the time at the start of each paragraph.
Transcribe a recording
Turn an audio recording into text in the background, then open its saved transcript when you are ready.
5 steps, about 5 minutes.
Open the recording transcriber. Transcribe a Recording opens a separate window for choosing the audio file and how to transcribe it.
- Keys: Shift+F5
- You should hear: Transcribe a Recording, with focus in Recording.
Choose the recording. Type a file path, browse for one or more supported audio files, or drop them on the window. The window reports the recording’s length and estimates how long the chosen model should take.
- You should hear: The file path, followed by its length and estimated time.
Choose the language and speech model. Choose English or Spanish and a model that knows that language. The most accurate available local model starts selected. Local models keep the recording on this computer; an OpenAI model uses your own key and asks before sending the recording.
- You should hear: The selected language and model, and the estimate for this recording.
Start it and carry on. Press Enter to start. Transcription runs in the background, so the document you were editing stays untouched while you work.
- Keys: Enter
- You should hear: That the recording is being transcribed in the background.
Open the result when it is ready. A completion notice appears in Notifications with a privately saved transcript. Activate the notice to open the transcript in a document; it is never inserted into the document you had open. Save the document normally if you want a separate file.
- You should hear: The completed transcript in its own document.
The recording and your current document stay separate, and the result is waiting in Notifications when you are ready for it.
WordPress
If you look after a WordPress site: connect it, write and publish a post, fix a page you found by its address, pictures with alternative text, the check before you publish, earlier versions, and comments.
Connect your WordPress site
Connect QUILL Lite to a WordPress site with an application password, hear which role you have there, and learn the WordPress keys.
7 steps, about 5 minutes.
Know what you need first. You need three things: the site’s address, your WordPress username, and an application password. An application password is a separate password WordPress makes for one app. It is not the password you sign in with, and you can take it away again at any time.
- Worth knowing: These lessons use the QUILL WordPress Test Site, at https://lp.csedesigns.com/wordpress/, as the example. On your own site, use your own pages wherever a lesson names one.
Open Connect a Site. In the File menu, open WordPress and choose Connect a Site. It is a short form, and nothing is saved until the site has said yes.
- Keys: Ctrl+Alt+Shift+Grave, A
- You should hear: The Connect a WordPress Site dialog, on Kind of site.
Type the site’s address. Leave Kind of site on My own WordPress site. Tab to Site address and type it, for example https://lp.csedesigns.com/wordpress/. QUILL Lite only connects over HTTPS, so your password never travels in the clear.
- You should hear: Site address, edit, and the letters as you type them.
Get the password with your browser. Press Get Password with My Browser. Your browser opens the site’s own approval page. Sign in there if it asks, then choose Approve. On a newer site the password comes back to QUILL Lite by itself.
- You should hear: “Connected to QUILL WordPress Test Site as” and your role, such as Editor.
- Worth knowing: On an older site, WordPress shows you the password instead. Copy it, come back, and paste it into the box that is waiting for it.
Or paste one from your profile. If you would rather do it by hand, make an application password in your WordPress profile, under Application Passwords, and copy it. Type your username, paste the password into Application password, and press Connect.
- You should hear: “Connected to QUILL WordPress Test Site as” and your role.
- Worth knowing: Your password is kept in Windows’ own Credential Manager, never in a settings file. Never paste it into an email or a chat.
Choose which site comes first. With more than one site, Switch Site, in File, WordPress, chooses your default. New and Open start there, and a document always stays with the site it came from.
- Keys: Ctrl+Alt+Shift+Grave, S
- You should hear: “Default site:” and its name, or that it is your only site.
Learn the WordPress keys. The WordPress key layer gives the commands one letter each. Press the layer key, let go, then press a letter. The six you will use most are O for Open Page or Post, P for Publish or Update, M for Media Library, S for Switch Site, W for Open by Web Address, or D for Save Draft to Site. Escape leaves the layer without doing anything.
- Keys: Ctrl+Alt+Shift+Grave, then a letter
- You should hear: Whatever the letter runs. After Escape, nothing at all.
- Worth knowing: The whole layer: G New Page, N New Post, O Open Page or Post, W Open by Web Address, L Open Local Draft, D Save Draft to Site, P Publish or Update, E Schedule Publish, I Open on Site, Y Copy Address, R Properties, V Previous Versions, C Compare with Site, T Move to Trash, S Switch Site, Shift+S Sites, A Connect a Site, M Media Library, B WordPress Blocks, K Check Before Publishing, U Upload Files, X Alt Text Review, H Open WordPress Workbench, Shift+H This Post in the Workbench. Every WordPress command is also in the Command Palette: type WordPress, or part of the command’s name.
You are connected, and the site has told you what your account may do. Next, write something and send it.
Next: Write a post and publish it.
Write a post and publish it
Start a new post, write it in the editor you already know, keep it on your computer, send it as a draft, and then publish it.
6 steps, about 6 minutes.
Start a new post. In the File menu, open WordPress and choose New Post. A post is a dated article, the kind that goes in a blog or a news list. A page is the lasting kind, like About or Contact.
- Keys: Ctrl+Alt+Shift+Grave, N
- You should hear: The New Post dialog, on Site, with your default site chosen.
Give it a title and a format. Tab to Title and type one. The slug, which is the end of the web address, fills itself in as you type. Choose Markdown or HTML under Write in, check a category or two, and press Create.
- You should hear: “New post for” the site, and that nothing is sent until you choose Save Draft to Site or Publish.
- Worth knowing: Markdown is the easier one to write by ear. The format cannot change later.
Write, and save on this computer. Write a few sentences the way you write anything else. Find, spelling and dictation all work here. Save as you always do: it keeps the post on this computer and sends nothing.
- Keys: Ctrl+S
- You should hear: The usual saved message. The site has not changed.
Send it as a draft. Save Draft to Site, in File, WordPress, puts your post on the site where only you and your editors can see it. It is the safe way to see how it looks before anybody else does.
- Keys: Ctrl+Alt+Shift+Grave, D
- You should hear: “Draft saved to QUILL WordPress Test Site. It is not public.”
Publish it. Choose Publish or Update. Before anything goes, a question names the post and the site, and says what Check Before Publishing found. Press Publish if you are happy, or Escape to stop.
- Keys: Ctrl+Alt+Shift+Grave, P
- You should hear: “Publish on” the site, the title, and “Ready to publish: no problems found”, or how many things there are to look at.
- Worth knowing: If your role cannot publish, the same command sends the post for review instead, and says so.
Hear where it went. Once it is published, the post’s web address is put on the clipboard, ready to paste into an email. Open on Site, in File, WordPress, opens it in your browser if you want to hear it the way a visitor will.
- Keys: Ctrl+Alt+Shift+Grave, I
- You should hear: “Published on QUILL WordPress Test Site. The address is on the clipboard.”
Saving keeps it here, Save Draft to Site sends it quietly, and Publish asks first. Closing a document never publishes anything.
Next: Open a page by its address and fix a sentence; Check Before Publishing.
Open a page by its address and fix a sentence
Open a post you found in your browser straight from its web address, change one sentence, and send the change back.
5 steps, about 5 minutes.
Copy the address. In your browser, copy the address of the post you want to change. On the test site, use the welcome post, at https://lp.csedesigns.com/wordpress/welcome/. Copy it from the address bar.
- You should hear: Your browser’s own word that the address was copied, if it says one.
Open it by its address. Choose Open by Web Address, in File, WordPress. When there is an address on the clipboard it is used straight away; when there is not, a box asks you for one.
- Keys: Ctrl+Alt+Shift+Grave, W
- You should hear: Open Welcome to the test site, and the Open as list.
Open it as Markdown. Choose Markdown. It reads more easily than HTML, and anything Markdown cannot show is kept exactly on a short line of its own, so nothing on the page is lost.
- You should hear: “Opened Welcome to the test site from QUILL WordPress Test Site.”
Fix one sentence. Find the sentence that says Open me by web address, and rewrite it in your own words. Arrow over it first if you like; this is an ordinary document now.
- You should hear: Your new sentence, read back as you arrow over it.
Send the change. Choose Publish or Update. A post that is already public is updated rather than published again, and the question says Update. Press Update.
- Keys: Ctrl+Alt+Shift+Grave, P
- You should hear: “Update on QUILL WordPress Test Site”, then “Published on QUILL WordPress Test Site.”
- Worth knowing: If somebody changed the post on the site after you opened it, nothing is sent. You are told what changed, and offered Compare the two, Open the site’s copy, or Send mine anyway.
Any address on one of your sites opens this way. Next time, try Open Page or Post for a page you know by name rather than by address.
Next: Go back to a previous version.
Pictures with alternative text
Put a picture from the site’s Media Library into a post with good alternative text, and fix a picture in the library that has none.
7 steps, about 6 minutes.
Open a post to put a picture in. Choose Open Page or Post and pick Posts. Type part of a title in Find by title or status and press Enter, then Enter again on the one you want. The post you wrote earlier is a good one.
- Keys: Ctrl+Alt+Shift+Grave, O
- You should hear: Each row’s title, its status, and when it last changed.
Choose a picture from the library. Put the cursor where the picture should go. In the Insert menu, choose Picture from the Media Library, and pick photo-volunteers from the list.
- You should hear: Insert from Media Library, and the Files list, newest first.
Listen to the alternative text. A picture dialog opens on Alternative text. That is what a screen reader says in place of the picture, so it should say what the picture shows and why it is there. This one already has some, from the library.
- You should hear: Alternative text, “Volunteers sorting donations at the spring fair”.
- Worth knowing: Suggest Alternative Text asks your chosen AI for a first try. Check the Decorative box for a picture that adds nothing a visitor needs, like a divider.
Insert it. Change the text if you can say it better for this post, then press Insert. The text belongs to this placement, so the same picture can say something different in another post.
- You should hear: “Picture inserted:” and its alternative text.
Find a picture with none. Open the Media Library, in Tools, WordPress. Type banner in Find and press Enter. The wide-banner picture has no alternative text, and its row says so.
- Keys: Ctrl+Alt+Shift+Grave, M
- You should hear: Each file’s title, type, size, alternative text and date.
Give it alternative text. With wide-banner selected, press Edit Alternative Text, write a short description, and press OK. This changes the library’s own text, which new placements start from.
- You should hear: “Alternative text saved on QUILL WordPress Test Site.”
Review every picture in the post. Back in your post, Alt Text Review, in Tools, WordPress, lists every picture with its text, so the empty ones and the weak ones are easy to find and fix.
- Keys: Ctrl+Alt+Shift+Grave, X
- You should hear: How many pictures there are, and how many to look at.
Every picture now says something to somebody who cannot see it. Check Before Publishing finds any you missed.
Next: Check Before Publishing.
Check Before Publishing
Have a post checked for the problems that trip up visitors, go to each one, and fix it before anybody else meets it.
5 steps, about 5 minutes.
Open the post with problems. Choose Open Page or Post and pick Posts. Type draft in Find by title or status and press Enter. On the test site, open Things to check before publishing. It was made with one problem of each kind.
- Keys: Ctrl+Alt+Shift+Grave, O
- You should hear: Things to check before publishing, Draft, and when it last changed.
Run the check. In the Tools menu, open WordPress and choose Check Before Publishing. It reads the whole post the way a careful visitor would, and nothing on the site changes.
- Keys: Ctrl+Alt+Shift+Grave, K
- You should hear: How many things there are to look at, with the problems and the things to check counted separately.
Listen to the list. Arrow down Things to look at. Each one says what to look at and why: a heading 1 in the body, a skipped heading level, link text that does not say where it goes, a picture with no alternative text, a table with no header row, and a few more.
- You should hear: One finding a line, each with its reason.
Go to one. Press Go to It on the finding you want to fix. The list closes and the cursor lands on that place in the post, so you can fix it there and then.
- You should hear: The line of the post the finding is about.
Fix it, and check again. Make the fix, then run Check Before Publishing again. Work down the list until it is empty, or until what is left is something you chose on purpose.
- Keys: Ctrl+Alt+Shift+Grave, K
- You should hear: One fewer each time, and at the end, “Ready to publish: no problems found”.
- Worth knowing: None of the findings stops you publishing. Publish runs the same check and reads you the summary in its question.
The check is the second pair of eyes a sighted editor has by default. Run it before every publish; it costs a few seconds.
Next: Go back to a previous version.
Go back to a previous version
Hear the earlier versions of a post, the ones kept on this computer and the site’s own history, read one, and put it back.
5 steps, about 5 minutes.
Open a post with a history. Open the welcome post again with Open by Web Address. The test site changed it three times when it was set up, so it has a history to look through.
- Keys: Ctrl+Alt+Shift+Grave, W
- You should hear: Opened Welcome to the test site, or your working copy of it.
Open Previous Versions. In the File menu, open WordPress and choose Previous Versions. It lists the versions QUILL Lite kept, newest first, and then the site’s own history.
- Keys: Ctrl+Alt+Shift+Grave, V
- You should hear: Each row’s date, title, and why it was kept, such as On the site.
Read one before choosing. Select a version and press View. The whole text opens in a window of its own, where you can read it or copy a paragraph out of it. Escape brings you back to the list.
- You should hear: The Version window, with the title and then the text.
Put it back. Press Restore on the version you want. It goes into the editor in place of your text, and nothing is sent to the site until you choose to.
- You should hear: “Version put in the editor. Nothing was sent; your text before is in Previous Versions.”
Hear what is different. Compare with Site, in File, WordPress, lists the differences between the site’s copy and yours, a line at a time. It is the check worth making before you send a restored version.
- Keys: Ctrl+Alt+Shift+Grave, C
- You should hear: A count of lines added and removed, then each change: Removed for the site’s line, Added for yours.
- Worth knowing: Changed your mind? Your text from before the restore is the newest row in Previous Versions, marked Before restore.
Nothing you send is ever lost: the site’s copy is kept before every update. Restore is the way back, and it never publishes.
Next: Answer comments.
Answer comments
Hear the comments waiting for you, reply to one, approve it, and deal with the spam.
5 steps, about 5 minutes.
Open Comments. In the Tools menu, open WordPress and choose Comments. It starts with the ones waiting for you, because those are the ones nobody else can see yet.
- You should hear: Comments: Waiting, and the site’s name, then the list. On the test site, Alex asks when the next session starts.
Read the whole comment. Each row says who wrote it, on which post, when, and its first words. Tab to Details to read the whole comment before you decide what to do.
- You should hear: The comment’s full text.
Reply to it. Tab back to the list and press Reply. Write your answer and press OK. It is published under your name, under the comment it answers.
- You should hear: “Reply to Alex published on QUILL WordPress Test Site.”
Approve it. Press Approve on the comment. It goes on the site for everybody to read, and leaves this list of waiting ones.
- You should hear: “Comment from Alex approved.”
- Worth knowing: Spam and Trash are beside Approve, for the comments that should never be seen.
Look in the spam. Press Show and choose Spam. WordPress catches most junk by itself, but now and then a real comment lands here, and Not Spam sends it back to Waiting.
- You should hear: Comments: Spam, and the comments in it.
Waiting Count on First Use, in the same window, has the number of waiting comments said to you the first time you use the site in a session, so they never pile up unnoticed.
Your first week with a site
For a new site owner: one short lesson a day for seven days, on your own site, each ending with something real – and nothing happens that you did not choose.
Day 1: Connect your site
Connect QUILL Lite to your own site and hear the role you have there. By the end your site is one of your sites.
3 steps, about 5 minutes.
Open Connect a Site. Connect a Site asks for your site’s address and gets an application password through your browser, so you never type your own password into QUILL Lite.
- Keys: Ctrl+Alt+Shift+Grave, A
- You should hear: The Connect a WordPress Site dialog, on Kind of site.
- Worth knowing: The WordPress track’s first lesson walks through this form in full.
Approve it in your browser. Press Get Password with My Browser, sign in on your site if it asks, and choose Approve. You can take the password away again on your site at any time.
- Keys: Enter
- You should hear: Connected to your site as, and your role.
Hear it in your sites. Sites lists every site you have connected, with your role on each. Your role decides what every later day can do.
- Keys: Ctrl+Alt+Shift+Grave, Shift+S
- You should hear: Your site’s name, its address and your role.
Your site is connected. Tomorrow, write something on it that nobody sees yet.
Next: Day 2: Save a draft on your site.
Day 2: Save a draft on your site
Write a short post and save it to your site as a draft: it is on the site, and nobody but you can see it.
3 steps, about 6 minutes.
Start a new post. New Post asks for a title and opens an empty document for the post. Call it something you would really publish, such as News for this month.
- Keys: Ctrl+Alt+Shift+Grave, N
- You should hear: New post, and the title box.
Write a paragraph. Write two or three sentences, the way you would in any document. Headings and lists come across to WordPress as blocks by themselves.
- You should hear: Your words, as you type them.
Save it to your site as a draft. Save Draft to Site sends the post as a draft. A draft is saved on the site and is not public until you publish it, which is a separate choice.
- Keys: Ctrl+Alt+Shift+Grave, D
- You should hear: Saved the draft to your site.
There is a draft on your site. On day 7 you can choose to publish it.
Next: Day 3: Describe one picture.
Day 3: Describe one picture
Hear which pictures on your site have no alternative text, and describe one you know, so a screen reader can say what it shows.
3 steps, about 6 minutes.
Open Alt Text Review. Alt Text Review lists pictures and what each one’s alternative text says, starting with the ones that have none. Nothing changes until you write something.
- Keys: Ctrl+Alt+Shift+Grave, X
- You should hear: Alt Text Review, and the first picture without alt text.
Choose one you know. Arrow through the list to a picture you can describe: one you took or chose yourself. Skip any you are unsure of; there is no need to do them all today.
- Keys: Down
- You should hear: Each picture’s name and where it is used.
Write what it shows. Type one plain sentence about what the picture shows and why it is there, then save. Only that picture changes.
- Keys: Enter
- You should hear: Saved the alt text, and the next picture.
One picture on your site can now be heard as well as seen.
Next: Day 4: Fix one thing the check finds.
Day 4: Fix one thing the check finds
Check the whole site for problems, read what was found, and fix one finding you understand, knowing it can be undone.
4 steps, about 8 minutes.
Check the whole site. Check the Whole Site reads your pages and posts and lists what it found: missing alt text, skipped headings, links that go nowhere. Reading changes nothing.
- You should hear: How many pages were checked, then each finding.
Pick one finding. Arrow through the findings and pick one you understand, such as a skipped heading level. Each finding says which page and what is wrong.
- Keys: Down
- You should hear: Each finding, with its page.
Fix that one. Where a finding offers a fix, choose it for that one only. You see the change before it is sent, and nothing else on the site is touched.
- Keys: Enter
- You should hear: What will change, then the fix said in words.
Know how to take it back. Undo Site Fix lists the fixes made from the check and puts any of them back as it was. You do not need it today; it is good to know where it is.
- You should hear: Undo Site Fix, and the fix you just made.
One real problem fewer on your site, and a way back if you ever need one.
Next: Day 5: Answer your comments.
Day 5: Answer your comments
Hear the comments waiting on your site, and approve or answer one you choose. Nothing is deleted.
3 steps, about 6 minutes.
Open Comments. Comments lists the comments on your site, waiting ones first, with who wrote them and on which post. If none are waiting, that is a good day.
- You should hear: Each comment’s author, its post, and whether it is waiting.
Approve one you are happy with. On a waiting comment you want visitors to see, choose Approve. It goes on the site under its post. Leave any you are unsure of where they are.
- Keys: Enter
- You should hear: Approved, and the author’s name.
Answer one. On a comment that asks something, choose Reply and write your answer. It appears under theirs, as you, when you send it.
- You should hear: Reply, and the box for your answer.
- Worth knowing: Spam can wait for another day; marking it spam is never urgent.
Somebody who wrote to your site has heard back from you.
Next: Day 6: Look after your menu.
Day 6: Look after your menu
Hear your site’s menu as a visitor meets it, add one page to it if you want to, and learn where its earlier versions are.
3 steps, about 6 minutes.
Open Menus. Menus lists your site’s menus and each one’s items in order: the first thing a visitor meets on every page.
- You should hear: Each menu, and its items in order.
Add a page if one is missing. If an important page, such as Contact, is not in the menu, add it and put it where it belongs. If the menu is right as it is, leave it.
- Keys: Enter
- You should hear: What will change, then the menu again.
Know where its earlier versions are. Menu History keeps the menu as it was before each change, so any version can be put back. That is why trying a change here is safe.
- You should hear: Menu History, newest first.
Your menu is the way you want it, and it can always go back.
Next: Day 7: Publish when you are ready.
Day 7: Publish when you are ready
Open the draft from day 2, check it, and publish it, schedule it, or keep it as a draft: the choice is yours.
3 steps, about 7 minutes.
Open your draft. Open Page or Post lists your site’s pages and posts, drafts included. Choose the draft you saved on day 2.
- Keys: Ctrl+Alt+Shift+Grave, O
- You should hear: Your draft’s title, in the editor.
Check it before publishing. Check Before Publishing reads the post the way a careful editor would: headings, link text, pictures without alt text. Fix what it finds first.
- Keys: Ctrl+Alt+Shift+Grave, K
- You should hear: What the check found, or that it found nothing.
Publish it, or not yet. Publish or Update asks before anything goes public. Say yes if you are ready; say no and it stays a draft. Nothing is lost either way.
- Keys: Ctrl+Alt+Shift+Grave, P
- You should hear: Publish this post, and the question.
- Worth knowing: Schedule Publish is the other answer: it goes public by itself later.
That is your first week: a site you have connected, written on, described, checked, answered and arranged. The WordPress track goes further.
The WordPress Workbench, on the Practice Site
Start a WordPress site on this computer, change a post there, read Change History, undo, and reset the site – all with nothing real at stake.
Start the Practice Site
Start a WordPress site on this computer and connect the Workbench to it, so the next lessons have somewhere safe to work.
5 steps, about 6 minutes.
Know where you will be working. The Practice Site is a whole WordPress that runs on this computer only, at http://127.0.0.1:9400. Nobody else can see it, and nothing you do there reaches any of your real sites. Every lesson in this track works there and nowhere else.
- Worth knowing: The Workbench labels it as practice wherever its name appears, and asks you by name before anything from it could go to a real site.
Open the WordPress Workbench. The Workbench is the window for everything on your WordPress sites. Open it from the editor’s WordPress menu.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Open Practice Site. In the Workbench’s Tools menu, choose Practice Site. It is one short list of what you can do with the site right now.
- Keys: Ctrl+Alt+P
- You should hear: Practice Site, and Start the Practice Site.
Start it. Choose Start the Practice Site and press Enter. The first start builds a fresh WordPress with a welcome page, a first post and a draft, so give it two or three minutes. Later starts take under a minute.
- Keys: Enter
- You should hear: The Practice Site is running at http://127.0.0.1:9400. Connect it in a moment.
- Worth knowing: If something else on this computer is using its port, it says so and does not start. Stop the other copy first.
Connect it. Open Practice Site again and choose Connect It as Practice Site. The site made a one-time password for QUILL when it started; the Workbench keeps it in Windows Credential Manager, so you type nothing.
- Keys: Ctrl+Alt+P
- You should hear: Practice Site is connected. It is under Sites.
The Practice Site is now one of your sites in the tree. It stays there, with everything you do to it, until you reset it.
Next: Change a practice post, then undo it.
Change a practice post, then undo it
Open a post on the Practice Site, change its title, find the change in Change History, and put it back.
6 steps, about 6 minutes.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. Doing this first makes the Practice Site the current site, so every later step works there.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Go to its posts. Go to Posts lists the current site’s posts in the list beside the tree. Because you moved to the Practice Site, these are its posts.
- Keys: Ctrl+Shift+1
- You should hear: A First Practice Post, Hello world, and My Next Practice Story.
Open A First Practice Post’s Properties. Arrow to A First Practice Post and open Properties. Everything about the post is on one sheet, one field at a time.
- Keys: Alt+Enter
- You should hear: A First Practice Post Properties, on its title.
Change the title. Add the word Practised to the end of the title and choose OK. The Workbench shows you what it is about to send, and sends it only when you say yes.
- Keys: End, Enter
- You should hear: What will change, then the list again with the new title.
Read Change History. Change History lists every change made in the Workbench this session, newest first, and says which ones can be undone.
- Keys: Ctrl+Shift+H
- You should hear: Change History, with your title change first.
Undo it. Close Change History and, from the list, undo the last WordPress change. The Workbench puts the old title back on the site.
- Keys: Ctrl+Z
- You should hear: The undo said in words, and the list with the old title.
- Worth knowing: Undo works in the list, not in the filter box, where it edits the text.
That is the whole loop the Workbench uses everywhere: look, change with a preview, find it in Change History, and undo it if you need to.
Next: Reset the Practice Site.
Reset the Practice Site
Stop the Practice Site and put it back as new, knowing exactly what a reset removes and what it leaves alone.
3 steps, about 4 minutes.
Stop it. Open Practice Site and choose Stop the Practice Site. Stopping keeps everything on it for next time; it only ends the server.
- Keys: Ctrl+Alt+P
- You should hear: The practice site has stopped.
Choose Reset. Open Practice Site again and choose Reset the Practice Site. Read the question to the end before answering: it lists what is removed.
- Keys: Ctrl+Alt+P
- You should hear: Reset the Practice Site, and that it permanently deletes everything on it and cannot be undone.
- Worth knowing: Reset removes the posts, pages, uploads and settings on the Practice Site, its connection, and its stored password. Your real sites are not touched.
Answer Reset. Choose Reset. The default answer is Cancel, so pressing Enter by habit does nothing.
- You should hear: The practice site is new again. Start it to use it.
Start it again whenever you want a clean site to practise on; the first lesson in this track walks you through it.
Look after a site
Read how the site is doing, bring back a lost menu item, check its people, its health, its fonts and its widgets, and move big files and Word documents in and out, all on the Practice Site.
8 steps, about 10 minutes.
Open the WordPress Workbench. Open the Workbench and move to the Practice Site under Sites. Everything in this lesson happens there.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Read At a Glance. Open Overview with Right Arrow, then At a Glance. Each row is one sentence: posts and pages by status, comments waiting, the people, WordPress’s version and the theme.
- Keys: Right
- You should hear: Posts, then how many are published, drafts and scheduled.
- Worth knowing: A count your role may not see is left out rather than said as zero.
Find what is only in wp-admin. Open wp-admin Screens, under Overview. Each row is a wp-admin screen, the place in the Workbench nearest to it, and how much of it the Workbench does. Enter says why and opens it in your browser.
- Keys: Enter
- You should hear: Settings > Permalinks, Only in wp-admin.
Bring back a menu item. Open Menus and Navigation and choose a menu. Its context menu, Shift+F10, has Earlier Versions, which brings back items removed since QUILL first read the menu, after a preview. Ctrl+Z takes them out again.
- Keys: Shift+F10
- You should hear: Earlier Versions of the menu, newest first.
Check the people and the site’s health. Open People, then Users, to hear each person and their role; then Site Health, where WordPress’s own checks are listed worst first.
- You should hear: Each person’s name, username and role.
Hear the fonts and the widgets. Under Appearance, Fonts lists the fonts the site has installed, and Widgets and Sidebars lists each widget area. On an area, Shift+F10 has Add a Widget, which offers every kind of widget the site has, and Preview Widgets, the area as a visitor sees it.
- Keys: Shift+F10
- You should hear: Each widget, then what a visitor sees of it.
- Worth knowing: A block theme has no widget areas; its header and footer are templates.
Upload a big file. Back in the editor, Upload a Large File first says how much space the site already uses beside the file’s size, then asks for its title, caption and description once it is there.
- You should hear: Upload, the file’s size, and what the site already uses.
Download your writing as Word. Download My Writing asks whether each page and post should be a Markdown file or a Word document. Send a Folder as Drafts reads Word documents too, so a folder can go back as drafts.
- You should hear: Save each page and post as: Markdown files, or Word documents.
You can now look after a site the way wp-admin does, and know where wp-admin is still the place. Reset the Practice Site whenever you want to start fresh.
Change a menu, then put it back
Find the Practice Site’s menu, add the welcome page to it, put its items in order, and bring the menu back as it was.
7 steps, about 7 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Go to Appearance. Go to Appearance opens the part of the tree for how the site looks: themes, templates, patterns, widgets, and menus.
- Keys: Ctrl+Shift+7
- You should hear: Appearance, and the themes the site has.
Open Menus and Navigation. Arrow down the tree to Menus and Navigation. Each row is one menu, and the details say where on the site it shows.
- Keys: Down
- You should hear: Practice Menu, and how many items it has.
- Worth knowing: This lesson uses the lesson material: Tools > Practice Site, Set Up the Lesson Material. The first Break It on Purpose lesson walks you through it.
Add a menu item. On Practice Menu, press Shift+F10 and choose Add Menu Item. Pick the page called Welcome to Your Practice Site. The Workbench shows what it is about to add and adds it only when you say yes.
- Keys: Shift+F10
- You should hear: What will change, then the menu with one more item.
Put the items in order. Shift+F10 again has Arrange Items, a list of the menu’s items with Move Up and Move Down. Move the welcome page to the top, the place a visitor meets first.
- Keys: Shift+F10
- You should hear: Arrange Items, then each item with its place in the menu.
Bring the menu back as it was. Earlier Versions, on the same context menu, lists the menu as QUILL first read it and since. Choose the oldest to put it back, after a preview. Ctrl+Z in the list does the same for the last change.
- Keys: Shift+F10
- You should hear: Earlier Versions of Practice Menu, newest first.
A menu is one of the few things a visitor sees on every page, so it is worth knowing it can always be put back.
Next: Add a person and choose their role.
Add a person and choose their role
Hear what each role may do, add a person to the Practice Site as an Author, change their role, and see the site as they would.
7 steps, about 7 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Go to Users. Go to Users lists the people on the current site, each with their username and role. On a fresh Practice Site that is only admin.
- Keys: Ctrl+Shift+5
- You should hear: admin, Administrator.
Hear what the roles may do. Roles and What They May Do says each role in plain words before you give one to anybody: a Contributor writes but cannot publish, an Author publishes their own, an Editor publishes anyone’s.
- Keys: Ctrl+Alt+R
- You should hear: Subscriber, then what a subscriber may do.
Add a person. In Users, New Here opens Add a Person. Give a username such as practice-helper and an email address, and set Role to Author. The role starts at Subscriber, the one that can do least.
- Keys: Ctrl+N
- You should hear: Add a Person, Practice Site, on Username.
- Worth knowing: Nobody is emailed: the Practice Site cannot send mail.
Change their role. Arrow to practice-helper, press Shift+F10 and choose Change Role. Choose Editor. The Workbench refuses any change that would lock you out of your own site, and says why.
- Keys: Shift+F10
- You should hear: Change Role, then practice-helper, Editor.
See the site as they would. View As Role shows the Workbench as an Editor would see it: the lists and commands an Editor has, and nothing else. Choose your own role again to come back.
- Keys: Ctrl+Alt+V
- You should hear: Viewing as Editor, and the lists an Editor has.
Give the smallest role that lets somebody do their job. You can always raise it later, and the Workbench says plainly what each one allows.
Next: Update plugins safely.
Update plugins safely
Take a snapshot first, find what is waiting to update, read what changed, run the update, and check the site’s health afterwards.
7 steps, about 8 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Take a snapshot first. Take a Snapshot saves the site’s posts, pages, patterns and terms on this computer before you change anything, so there is something to go back to.
- Keys: Ctrl+Alt+S
- You should hear: Snapshot taken, and where it is kept.
Find what is waiting. Go to Needs My Attention, then arrow to Updates. It lists WordPress, plugins, themes and translations with an update waiting, on every site you have, with the installed and the new version.
- Keys: Ctrl+1, Down
- You should hear: Updates, and each one with its site and its two versions.
- Worth knowing: A fresh Practice Site may have none waiting. The steps are the same on your own site.
Read what changed. On an update, Shift+F10 has Check for Updates on WordPress.org, which reads the plugin’s own page: listen for security fixes, breaking changes and database updates before you go on.
- Keys: Shift+F10
- You should hear: The plugin, its newest version, and what that version changed.
Run the update in wp-admin. Press Enter on the update. WordPress does not let any app run updates from outside, so this opens Dashboard, Updates in your browser, where you choose it and update.
- Keys: Enter
- You should hear: Your browser, on WordPress Updates.
Check the site’s health afterwards. Back in the Workbench, Go to Site Health and press F5. A problem that was not there before the update is the first thing to look at.
- Keys: Ctrl+Shift+9, F5
- You should hear: Site Health, worst first, and Up to date.
- Worth knowing: If an update broke something, Go to Plugins has Activate or Deactivate on each plugin’s context menu.
Snapshot, read, update, check: four steps, every time, and an update is rarely a surprise.
Next: Spam, real comments, and challenges.
Spam, real comments, and challenges
Tell a held spam comment from a real question, approve and answer the real one, and hear where the challenges for forms are kept.
8 steps, about 7 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Open Held as Spam. Go to Needs My Attention, then arrow to Held as Spam. It gathers the comments and form entries every site doubted, with who sent them.
- Keys: Ctrl+1, Down
- You should hear: Held as Spam, and Cheap Watches Today, Practice Site.
- Worth knowing: This lesson uses the lesson material: Tools > Practice Site, Set Up the Lesson Material. The first Break It on Purpose lesson walks you through it.
Read why it was held. Next Pane moves to the details, which say what the comment says and why the site held it. This one is spam: leave it where it is.
- Keys: F6
- You should hear: Cheap Watches Today, and the comment in full.
- Worth knowing: Ctrl+Shift+A on a held comment means Not Spam, and lets it through. Not Spam, and Allow This Sender, lets that person’s next ones through too.
Find the real question. Go to Comments lists the current site’s comments, waiting ones first. Sam Rivera is asking when the bake sale is, a real question from a real visitor.
- Keys: Ctrl+Shift+4
- You should hear: Sam Rivera, waiting, on A First Practice Post.
Approve it. Approve puts the comment on the site where everybody can read it. Unapprove sends it back to waiting if you change your mind.
- Keys: Ctrl+Shift+A
- You should hear: Approved, Sam Rivera.
Answer it. Reply opens a box for your answer, written as you, under Sam’s comment. Say Saturday, and send it.
- Keys: Ctrl+Shift+M
- You should hear: Reply to Sam Rivera, on the box for your answer.
Hear where the challenges are. On a site in the Sites list, Shift+F10 has Form Spam Questions: the short questions visitors answer before a form is sent, and how many entries each week were held.
- Keys: Shift+F10
- You should hear: Form Spam Questions, or that this site has no forms plugin.
- Worth knowing: The Practice Site has no forms plugin, so it says so. On a site with QUILL Accessible Forms the questions are listed.
Spam waits for you in one place across every site, and a real comment gets an answer in two keys.
Custom types and their fields
Hear what kinds of content the Practice Site has beyond posts and pages, open an event, and change its Event date field.
7 steps, about 7 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Open the Content Model. Under the Practice Site, arrow to Content Model. Each row is one kind of content or one field, who registered it, and whether QUILL can reach it.
- Keys: Down
- You should hear: Practice Events, post type, and the plugin that registered it.
- Worth knowing: This lesson uses the lesson material: Tools > Practice Site, Set Up the Lesson Material. The first Break It on Purpose lesson walks you through it.
Open Practice Events. Arrow up to More Content Types and then into Practice Events. A custom type gets a list of its own, like Posts and Pages.
- Keys: Up, Right
- You should hear: Winter Concert, published.
Open the event’s Properties. Properties on Winter Concert has its title and status like any post, and its own fields on a page of their own, among them Event date.
- Keys: Alt+Enter
- You should hear: Winter Concert Properties, on its title.
Change Event date. Move to the fields page, find Event date, and change it to 2026-12-06 19:00. Choose OK; the Workbench shows what it will send and sends it when you say yes.
- Keys: Ctrl+Tab, Enter
- You should hear: What will change: Event date, then the list again.
Find it in Change History. Change History has the field change like any other, and Undo puts the old date back. A field is no harder to undo than a title.
- Keys: Ctrl+Shift+H
- You should hear: Change History, with the Event date change first.
Every content type a plugin adds, and every field it exposes, works the same way as a post: a list, Properties, a preview, and undo.
Next: From staging to live, without surprises.
From staging to live, without surprises
Treat the Practice Site as your staging copy: change a page there, compare it with your real site, and take a snapshot before anything is copied.
7 steps, about 8 minutes.
Know what staging is. Staging is a copy of a site where changes are tried first; live is the site visitors see. Here the Practice Site is staging, and one of your connected sites is live.
- You should hear: Nothing yet: this step is the idea.
- Worth knowing: If you have only the Practice Site connected, you can follow every step but Compare Sites, which needs a second site.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Change a page on staging. Go to Pages, open Properties on Welcome to Your Practice Site, and add the word Updated to its title. This is the change you will compare.
- Keys: Ctrl+Shift+2, Alt+Enter
- You should hear: Welcome to Your Practice Site Properties, then the list again.
Compare staging with live. Compare Sites asks for the other site and then lists what differs: pages, posts, plugins, themes and settings, each with what it is on each side. Nothing is changed by comparing.
- Keys: Ctrl+Alt+K
- You should hear: What differs between Practice Site and your other site.
Take a snapshot of live first. Move to your live site under Sites and Take a Snapshot. It reads the site and saves it on this computer, so if a copy goes wrong Put Back from a Snapshot can undo it.
- Keys: Ctrl+Alt+S, Up, Down
- You should hear: Snapshot taken, and where it is kept.
Know how the copy asks. Copy to Site, on an item’s context menu, is how a change goes from staging to live. From the Practice Site it always asks first, naming both sites, with No as the answer Enter gives.
- You should hear: Nothing yet: this lesson stops here, with live untouched.
- Worth knowing: When you do copy for real, read the preview to the end: it lists every item that will change on the live site.
Change on staging, compare, snapshot, then copy with your eyes open: live only changes when you have said its name.
Next: Across sites with a Site Set.
Across sites with a Site Set
Name a set of your sites, point Across Sites at it, read the same list on every site in the set at once, and remove the set again.
6 steps, about 6 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Make a Site Set. Site Sets asks for a name, then for the sites in it. Call it Practising and check Practice Site. A set is kept on this computer and changes nothing on any site.
- Keys: Ctrl+Alt+T
- You should hear: Practising: 1 sites.
Point Across Sites at the set. Across Sites Scope chooses whether Across Sites covers every site or one set. Choose Practising, so what you read next is only the sites in it.
- Keys: Ctrl+Alt+Y
- You should hear: Across Sites covers Practising.
Read across the set. Go to Across Sites lists the same name on every site in scope: a plugin, a person, a category. Arrow into Plugins to hear each plugin and the sites it is on.
- Keys: Ctrl+0, Right
- You should hear: Across Sites, and the kinds it can compare.
Go back to every site. Across Sites Scope again, and choose Every site. A set you are not using costs nothing, and Every site is what Needs My Attention always uses.
- Keys: Ctrl+Alt+Y
- You should hear: Across Sites covers every site.
Remove the set. Site Sets with the same name, Practising, and every site unchecked removes the set. Nothing on any site changes.
- Keys: Ctrl+Alt+T
- You should hear: Removed Practising.
A Site Set is a name for some of your sites. Make one for the sites you look after together, such as a client’s three.
Break It on Purpose, on the Practice Site
Four problems put on the Practice Site on purpose – a missing alt text, a broken link, a plugin conflict and a wrong address – and how the Workbench finds and fixes each one.
Set up the broken Practice Site
Put four problems on the Practice Site on purpose, after hearing exactly what will be added, and learn how to take them away again.
5 steps, about 4 minutes.
Know what is about to happen. These lessons need something wrong to find. The Practice Site lesson material adds it to the WordPress on this computer only, never to a real site, and lists every piece before it adds any.
- You should hear: Nothing yet: this step is what comes next.
- Worth knowing: Start the Practice Site first; the Practice Site track shows how.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Open Practice Site. In the Workbench’s Tools menu, choose Practice Site. Once the site has been started at least once, the list ends with Set Up the Lesson Material.
- Keys: Ctrl+Alt+P
- You should hear: Practice Site, and what you can do with it now.
Choose Set Up the Lesson Material. Arrow to Set Up the Lesson Material and press Enter. Read the question to the end: it names the picture, the posts, the page, the plugins, the comments and the event it adds.
- Keys: Down, Enter
- You should hear: Set up the lesson material on the Practice Site, and the list.
Answer Set Up. Choose Set Up. The default answer is Cancel, so Enter by habit does nothing. If the site is running the material is there at once; if not, it arrives when you next start it.
- You should hear: The lesson material is on the Practice Site, and what it holds.
- Worth knowing: Practice Site, Take Away the Lesson Material, removes exactly what was added, and Ctrl+Z in the list does the same. Reset removes everything.
Now there is something to fix. Start with the picture.
Next: Fix a picture with no alt text.
Fix a picture with no alt text
Find the picture nobody described, using Needs My Attention, and give it alternative text a screen reader can say.
5 steps, about 5 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Open Accessibility. Go to Needs My Attention, then arrow to Accessibility. It lists every picture without alternative text, on every site. A screen reader says only image for each of them.
- Keys: Ctrl+1, Down
- You should hear: Accessibility, and Bake sale table, Practice Site.
Open the picture’s Properties. On Bake sale table, open Properties. Its second page is Alt Text and Caption; Ctrl+Tab moves there.
- Keys: Alt+Enter, Ctrl+Tab
- You should hear: Bake sale table Properties, then Alt Text and Caption.
Write the alt text. In Alt text, say what the picture shows to somebody who cannot see it: a folding table of cakes under a striped awning. Choose OK, and yes to the preview.
- Keys: Enter
- You should hear: What will change: Alt text, then the list again.
Hear that it has gone. Refresh reads Accessibility from the site again. Bake sale table is no longer in it, because it now has alternative text.
- Keys: F5
- You should hear: Accessibility, without Bake sale table.
- Worth knowing: In the editor, Tools > WordPress > Alt Text Review does the same for the pictures in the page you are writing.
One picture, one sentence, and somebody who cannot see it now knows it.
Next: Fix a broken link.
Fix a broken link
Find a link that goes nowhere, open the post it is in, point it at a page that exists, and send the post back.
8 steps, about 7 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Open Broken Links. Go to Needs My Attention, then arrow to Broken Links. The Workbench follows the links in the newest published posts and pages and lists the ones the site could not reach.
- Keys: Ctrl+1, Down
- You should hear: Broken link, Where to Find Us, and the address it could not reach.
- Worth knowing: If it says the site does not offer link checking, Check This Page in the editor finds the same link in the next steps.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Open the post in the editor. Go to Posts, arrow to Where to Find Us and press Enter. Writing happens in the editor, so that is where the post opens.
- Keys: Ctrl+Shift+1, Enter
- You should hear: Where to Find Us, in the editor.
Hear where the link goes. Move to the words our address page and use Hear Where a Link Goes. It says the address and whether the page is there.
- You should hear: Our address page goes to our-old-address, which is not there.
Point it at a real page. Select the words our address page, then use Link to a Page on This Site and choose Contact Us. The words stay; only where they lead changes.
- You should hear: The pages on this site, then the document again.
Send the post back. Publish or Update sends the corrected post to the Practice Site. It is already published, so this is an update, and it says so.
- Keys: Ctrl+Alt+Shift+Grave, P
- You should hear: Updated Where to Find Us on Practice Site.
Check the page. Check This Page follows every link in the post and says which go nowhere. None should now; Broken Links agrees after F5.
- You should hear: All the links reach their pages.
A dead link costs a visitor a trip; finding it costs you one list.
Next: Fix a plugin conflict.
Fix a plugin conflict
Hear Site Health name a conflict between two plugins, switch one of them off, and hear the problem go.
7 steps, about 6 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Read Site Health. Go to Site Health lists WordPress’s own checks for the current site, worst first. The first one is new: two plugins both answer the countdown shortcode.
- Keys: Ctrl+Shift+9
- You should hear: Two plugins both answer the countdown shortcode, critical.
Read what it means. Next Pane moves to the details: which two plugins, what a visitor sees on a page that uses the shortcode, and the fix, which is to switch one off.
- Keys: F6
- You should hear: Practice Countdown and Practice Countdown Plus are both on.
Go to Plugins. Go to Plugins lists the plugins on the current site, each with whether it is on. Arrow to Practice Countdown Plus, the newer of the two.
- Keys: Ctrl+Shift+6
- You should hear: Practice Countdown Plus, active.
Switch it off. Press Shift+F10 and choose Deactivate. The Workbench asks first and says what depends on the plugin; answer Deactivate.
- Keys: Shift+F10
- You should hear: Practice Countdown Plus, inactive.
Hear the problem go. Go to Site Health again and press F5. The conflict is no longer listed, because only one plugin answers the shortcode now.
- Keys: Ctrl+Shift+9, F5
- You should hear: Site Health, without the countdown problem.
When something breaks after a plugin goes on, switching the newest one off is the first thing to try, and it is undone as easily.
Next: Fix a wrong address.
Fix a wrong address
Hear a page’s misspelt address, correct its slug in Properties, and take the lesson material away when you are done.
7 steps, about 6 minutes.
Open the WordPress Workbench. Open the Workbench from the editor’s Tools menu, under WordPress. It is one window for everything on your sites, and every step here happens in it.
- Keys: Ctrl+Alt+Shift+Grave, H
- You should hear: WordPress Workbench, and the tree of your sites.
Move to the Practice Site. In the tree, arrow to Sites and then to Practice Site. That makes it the current site, so every Go key in this lesson lands on its lists and no other.
- Keys: Up, Down
- You should hear: Practice Site, and the tree level it is on.
Go to Pages. Go to Pages lists the current site’s pages. Arrow to Contact Us; the details pane says its address, which ends contcat-us.
- Keys: Ctrl+Shift+2
- You should hear: Contact Us, published.
Open its Properties. Properties on Contact Us opens on General, where Slug is the last part of the address: the words after the site’s name.
- Keys: Alt+Enter
- You should hear: Contact Us Properties, on its title.
Correct the slug. Tab to Slug, replace contcat-us with contact-us, and choose OK. The preview shows the old and new address before anything is sent.
- Keys: Tab, Enter
- You should hear: What will change: Slug, then the list again.
Copy the new address. Copy Link puts the page’s address on the clipboard, so you can paste it anywhere and hear that it now ends contact-us.
- Keys: Ctrl+Shift+C
- You should hear: Copied the address of Contact Us.
Take the lesson material away. Practice Site, then Take Away the Lesson Material, removes every piece the material added, fixed or not, and the two practice plugins. Anything else you made stays.
- Keys: Ctrl+Alt+P
- You should hear: Take away the lesson material, and what it removes.
Those are the four problems people most often meet on a site, and you have found and fixed each one without leaving the keyboard.
Forms
Start a form from a template, add questions and a rule, check it, fill it in yourself, save it in large print or braille, and publish it to your site and read the responses.
Start a form from a template
Start a contact form from a template, save it, and read it through, first as text and then as an outline of its questions.
6 steps, about 5 minutes.
Know what a form is here. A form in QUILL Lite is a short plain text document: a title, some questions, their choices and a few rules, written in the QAF form language. You never have to learn the language, because the Forms commands write it for you.
- You should hear: Nothing yet. This step is the idea the rest build on.
- Worth knowing: Forms is on in every feature profile except Essential. If there is no New Form in the File menu, switch Forms on in Profiles and Features.
Open New Form. In the File menu, choose New Form. It sits with the other New commands. Nothing is written anywhere until you have chosen where to save it.
- You should hear: The New Form dialog, on Title.
- Worth knowing: No Forms command has a shortcut key, because you will not write forms every day. The Command Palette finds every one of them: type form.
Give it a title and a template. Type Ask us anything in Title. That is the name your visitors will see. Tab to Template and arrow down to Contact form. There are seven templates, and each one is a few questions you can change.
- You should hear: Template, and Contact form: Name, email address and a message.
Save the new form. Press Next. The ordinary Save As window opens with a file name made from your title, Ask us anything.qaf. Choose a folder you will find again and press Save. The new form opens straight away.
- You should hear: “Saved Ask us anything.qaf, a contact form with 3 questions.”
- Worth knowing: A form file ends in .qaf. It is ordinary text, so you can open it in any text editor too.
Read it through as text. Arrow down through the form from the top. Each question starts on a line of its own: its kind, its id after a number sign, and its label in quotes. The indented lines under it are its settings, such as required.
- You should hear: “text #name”, then “Your name” in quotes, then “@required”.
- Worth knowing: Because it is text, Find, spelling, copy and paste all work here, and you can type a question yourself if you would rather.
Hear it as an outline. In the View menu, choose Form Outline. It lists every page and question in order, each one read like a sentence, so you can hear the shape of the form without the form language.
- You should hear: “Page 1, 3 questions”, then “Your name, text field, required, with an autofill hint, page 1”.
- Worth knowing: Enter takes you to the selected question in the document. Escape closes the outline.
You have a real form, saved on this computer, and you have heard it two ways. Next, give it a question of your own.
Next: Add questions.
Add questions
Add a choose-one question and a phone number question to your form, each from a short window that asks only what that kind needs.
6 steps, about 5 minutes.
Put the cursor where it goes. Move to the line that says Your message. A new question goes in straight after the one your cursor is on, so this one will come last in the form.
- You should hear: “textarea #message”, then “Your message” in quotes.
Open Form Field. In the Insert menu, choose Form Field. A list of every kind of question opens, each row saying what a visitor meets. Section and Page break are at the top.
- You should hear: The Insert Form Field dialog, and the Kind of question list.
Find the kind you want. Tab to Search, type choose, and press Enter to narrow the list. Arrow to Choose one and press Enter. A visitor meets it as a group of buttons, and picks only one.
- You should hear: Choose one: Choose one from a group of buttons.
Write the question and its choices. In the next window, type Best way to reply in Label. Tab to Choices, one per line, and type Email, press Enter, then type Phone. Press Insert.
- You should hear: “Inserted Best way to reply, choose one.”
- Worth knowing: Help text is a sentence a screen reader reads with the question. Leave Id empty and the id is made from the label.
Add a phone number question. With the cursor still on Best way to reply, choose Form Field again. This time pick Phone number, type Phone number in Label, and press Insert. Leave Required unchecked: only some people will want a call.
- You should hear: “Inserted Phone number, phone number.”
Save your work. Save as you always do. A form saves like any other document, on this computer, and nothing is sent anywhere. Each insert is also one step that Undo takes back.
- Keys: Ctrl+S
- You should hear: The usual saved message.
The form now asks five questions. The phone number is asked of everybody, which is not quite right. A rule fixes that.
Next: Add a rule and hear it as a sentence.
Add a rule and hear it as a sentence
Make the phone number appear only for somebody who asked to be phoned, built from three choices and read back to you as a sentence.
5 steps, about 5 minutes.
Open Form Rules. In the Format menu, choose Form Rules. It lists every rule in the form as a sentence. This form has none yet, so the list is empty.
- You should hear: The Form Rules window, and the Rules list.
Say which question it listens to. Press Add Rule. In When this question, choose Best way to reply. Leave Is on is. In This answer, type Phone, the choice’s own words; capitals do not matter.
- You should hear: When this question, and Best way to reply.
- Worth knowing: A choice is stored as its words in small letters, with a hyphen for each space: Large print is large-print. QUILL turns what you type into that, so the rule matches however you write it.
Say what it does. Tab to Then and leave it on Show. In To this question or page, choose Phone number. Read that back to yourself: when Best way to reply is Phone, show Phone number.
- You should hear: To this question or page, and Phone number.
- Worth knowing: Then can also hide, require, make optional, enable, disable, or skip to a page.
Add it, and hear the sentence. Press Add Rule. The rule is written into the form for you, and QUILL Lite reads it back as the sentence it is, so you can hear whether it says what you meant.
- You should hear: “Show Phone number when Best way to reply is Phone.”
- Worth knowing: If you know the form language, Or write the condition yourself takes a whole condition instead. It is checked before anything is written, and you are told what is wrong if it does not read.
Find it in the form. The new rule is in the Rules list. Press Go to It to close the window and land on Phone number. The line under it, starting @when, is your rule in the form language.
- You should hear: “phone #phone”, then “Phone number” in quotes.
- Worth knowing: Edit changes a rule’s condition, and Remove takes one out after asking. Undo in the document takes back either.
Rules are the part of a form that is hardest to see on a web page. Here every one is a sentence you can read. Next, let the form be checked.
Next: Check This Form.
Check This Form
Find what would make the form hard to fill in, go straight to it, fix it, and check again.
5 steps, about 4 minutes.
Run the check. In the Tools menu, open Forms and choose Check This Form. It looks for anything that would make the form hard to fill in, such as a question with no label, and lists the most serious first.
- You should hear: “Phone number has no autofill hint, so the browser cannot fill it in. The hint is tel.”
- Worth knowing: An autofill hint lets a visitor’s browser fill in their own phone number, which saves typing and mistakes.
Know the On the site today lines. Arrow down the Findings list. A line that starts On the site today is not a mistake in your form. It says where the forms plugin on a website reads your form differently today, so you know before you publish.
- You should hear: Lines starting “On the site today”, if there are any.
Go to the finding. Arrow back to the autofill finding and press Go to It. The window closes and your cursor is on the Phone number question, ready to fix.
- You should hear: “phone #phone”, then “Phone number” in quotes.
Fix it. Go to the end of the last indented line under Phone number and press Enter. Type two spaces, then @autocomplete “tel”, with the quotes. That is the hint the finding asked for.
- You should hear: Your new line read back: “@autocomplete”, then “tel” in quotes.
- Worth knowing: Suggest Autofill Hints, in Tools, Forms, asks your chosen AI to suggest them all at once. It says what it sends first.
Check again. Choose Check This Form once more, in Tools, Forms. The autofill finding has gone. When there is nothing to fix at all, there is no list, just one sentence.
- You should hear: Only On the site today lines, or, with none of those, “Check This Form found nothing to fix.”
Check This Form is worth running every time you change a form, and always before you publish one. Next, fill it in yourself.
Next: Fill It In Yourself.
Fill It In Yourself
Open your form as a real window and fill it in with your screen reader, the way a visitor will, before anybody else sees it.
6 steps, about 5 minutes.
Open the form as a visitor meets it. In the Tools menu, open Forms and choose Fill It In Yourself. QUILL Lite builds a real window from the same text, with ordinary edit boxes, buttons and lists, so you meet what a visitor meets.
- You should hear: Fill It In Yourself: Ask us anything, and the first question.
Tab through the questions. Press Tab to move from question to question. Listen for each label, and for the word required on the ones that must be answered. Type a name and an email address as you go.
- You should hear: Your name (required), edit. Then Email address (required), edit.
- Worth knowing: If a question is hard to understand by ear here, it will be hard on the website too. That is the point of this window.
Watch the rule work. Tab to the Best way to reply group and arrow to Phone. Your rule runs as you answer, and you are told about the question it brings in, because nothing else would say so.
- You should hear: “Phone number appears.”
Change your mind. Arrow back to Email. The phone number question goes away again, exactly as it will for a visitor who chooses Email on the site.
- You should hear: “Phone number is hidden.”
Submit, which sends nothing. Press Submit. Nothing is sent anywhere. Instead, a window shows what would have been sent, one question and its answer to a line, and anything that still needs an answer.
- You should hear: What Would Be Sent: “Nothing was sent. This is what the form would send:”, then each question and your answer.
- Worth knowing: On a form with more than one page, Next first checks this page and names any required question still empty, then puts you on it.
Close it. Press Escape to close What Would Be Sent, and Escape again to close the form. Nothing you typed is kept, so you can try it as many times as you like.
- You should hear: Your form document again, where you left it.
You have filled in your own form the way your visitors will. Next, make a copy for people who would rather have it on paper or in braille.
Next: Save it as large print or braille-ready text.
Save it as large print or braille-ready text
Make a large-print copy and a braille-ready copy of your form, from the same text, without a website.
4 steps, about 4 minutes.
Know why there are other copies. Not everybody fills in a form on a website. Some people want it on paper in large print, and some want it in braille. Every copy comes from the same form, so it always asks the same questions.
- You should hear: Nothing yet. This step is the reason for the next two.
- Worth knowing: These work without a site and even in Safe Mode. If the form has a problem it cannot be read past, you are told to run Check This Form first, and nothing is saved.
Save a large-print copy. In the Tools menu, open Forms and choose Save As Large Print. The ordinary Save As window opens with a name ending in large print. Choose a folder and press Save.
- You should hear: “Saved Ask us anything large print.docx, a large-print Word document, 18 point and up, with 5 questions, lines to write on and boxes to check.”
Save a braille-ready copy. Choose Save As Braille-Ready Text, in Tools, Forms. It writes one question to a block, with the choices lettered a, b, c, 40 cells to a line, ready to emboss or read on a display.
- You should hear: “Saved Ask us anything.txt, braille-ready text with 5 questions, one a block.”
- Worth knowing: With the braille pack installed, you are first asked whether to save it as it is or as a braille file in UEB contracted braille.
Read the braille copy back. Open the .txt file you just saved, as you open any document. Arrow through it to hear one question to a block, so you know what the person reading it will find.
- You should hear: The form’s title, then each question, numbered, with its choices lettered.
- Worth knowing: Save As Web Page and Save As Word Document, beside these in Tools, Forms, make the other two copies the same way.
One form, and a copy for whoever needs one. The last lesson puts the form on your website.
Next: Publish it and read the responses.
Publish it and read the responses
Publish your form to a WordPress site running QUILL Accessible Forms, put it on a page, try it there, and read what people send.
6 steps, about 7 minutes.
Know what the site needs. Publishing needs a WordPress site you have connected, with the QUILL Accessible Forms plugin installed and switched on. The WordPress lessons show how to connect a site.
- You should hear: Nothing yet. This step is what the rest need.
- Worth knowing: Without the plugin you hear that the command needs QUILL Accessible Forms on the site, and to install and activate it there. Publishing and Responses are off in Safe Mode.
Publish the form. With Ask us anything in front, open Forms in the Tools menu and choose Publish Form. With more than one site, you choose which one first.
- You should hear: Publish Form, and Publish as, on Live.
Choose live or draft, then say yes. Live means people can fill it in wherever it is placed. Draft puts it on the site where nobody can use it yet. Press Enter on Live, and then on Publish when the question asks.
- You should hear: “Published Ask us anything on” your site, its form number, “live. Insert Form Into Page puts it on a page.”
- Worth knowing: Publishing again later updates the same form. If somebody changed it on the site since, you are asked first, and the site’s copy is kept on this computer.
Put it on a page. Open a page with Open Page or Post, in File, WordPress, and put the cursor where the form goes. Choose Insert Form Into Page in Tools, Forms, pick your form, then Publish or Update the page.
- You should hear: “Inserted the Ask us anything form”, and that it shows on the page once the page is sent.
Try it on the site. Back in your form, choose Test on Site, in Tools, Forms. It opens the page that shows your form in your web browser, so you can fill it in for real and send yourself a response.
- You should hear: “Opened” the page’s name “on” your site, “where the form is.”
Read what people sent. Choose Responses, in Tools, Forms. With your published form in front it goes straight to that form’s responses, newest first. Press Enter on one to read it, a question and its answer a line.
- Keys: Ctrl+Alt+Shift+Grave, F
- You should hear: Responses to Ask us anything, and each response: its number, when it was sent, and who sent it.
- Worth knowing: Responses are people’s personal details. They are read only while this window is open and saved only where you choose, with Export to CSV or Export to Word.
Your form is live, and you can hear every answer it brings in. The first time you use a site in a session, you are also told how many new responses are waiting.
Coding, in the Developer profile
Work on a folder of code with an AI: ask for a change, review every edit, allow the commands it runs, hear the test results, and undo a whole turn.
Your first project task
Open a small project, ask for one change, review it, let the agent run the tests, hear the result, and put everything back with one command.
8 steps, about 12 minutes.
Make a practice folder. Make an empty folder and put one small file of code in it, such as a Python file with a function that has a mistake in it. A project is just a folder; nothing in it is changed until you say.
- Worth knowing: Use a copy, not your real work, the first time. Undo Last Turn puts files back, but practising on a copy costs nothing.
Open the folder as a project. Open Project Folder is in the File menu. Choose Browse for a Folder and pick your practice folder. The status bar’s Project cell now names it.
- You should hear: Project, and the folder’s name, is open.
Ask for one small change. Press the task command. With a project open it starts a project task rather than a document task. Type one plain request, such as fix the add function and run the tests, and press Enter.
- Keys: Ctrl+3
- You should hear: Nothing at first; then “The plan is ready”, with the number of steps.
- Worth knowing: The first time, QUILL may ask whether to use the project’s notes for AI agents, if it has any. Read Them First shows them.
Read the plan. Press Alt+P in the task window to put the cursor on the plan, and read it with the arrow keys. Nothing has changed yet.
- Keys: Alt+P
Review the change. When the agent has an edit, Review Changes opens on a list of files. Press Enter on a file, read the change with its line numbers, and Accept or Reject it. Apply Accepted Changes writes what you accepted; Reject All writes nothing.
- You should hear: The window’s own title and the first file’s row.
Allow the test command. Run This Command? shows the exact command. Arrow through it, then Allow once. A warning line appears only when QUILL sees a risk, such as reaching the internet.
- You should hear: The result in one sentence, such as “Tests: 3 passed.”
Undo the whole turn. Undo Last Agent Turn, in Edit under Agent Work, puts every file the turn changed back as it was and removes files it made.
- You should hear: “Undid turn 1”, and which files are back.
- Worth knowing: If you edited one of those files yourself since, undo refuses and offers to show you the file as it was, so nothing of yours is lost.
Try coach mode. Check Coach mode (Alt+A) in the task window and ask how to fix the mistake yourself. The agent explains and points to a file and line; you make the change in the editor.
- Keys: Alt+A
- Worth knowing: Stop Agent stops a task from any window: Edit, Agent Work, Stop Agent.
That is the whole loop. Every change is reviewed before it is written, every command asks first, and one command undoes a turn.