Birthday invitations for people with limited mobility

It's the week of your dad's 70th and your phone keeps buzzing. Not with replies — with questions. What time is the cake, is the side entrance open, can I bring my sister. If you're sending birthday invitations for people with limited mobility, this is the part that goes wrong: the card arrives, and then the work starts. One guest uses a wheelchair and reads everything on her phone with the text turned right up. Another never opened the envelope at all, because he does everything on his phone.

None of it happens when the invitation is a link. It opens in the browser on any phone, the replies land in one list, and if the time or the place changes you edit the thing you already sent. No app to download first, no phone call to say yes.

Birthday invitations for people with limited mobility

The invitation itself should have no steps. Share it as a link, a QR code or a message and it opens straight in the browser — no app, no account. It looks the same on a phone, a tablet and a laptop, so a guest who reads better on a bigger screen can open it on the desktop at home. There's no envelope to lose and no small print on the back. The message stays in the chat, and they can reopen it the night before to check the time.

• Write the access into the venue scene: "step-free entrance on Mill Lane, lift to the second floor."
• Put the map inside the invitation, not in a separate file guests have to open in another program.
• Keep the RSVP questions short and positive: "How many of you are coming?" rather than a long form.
• Set the RSVP deadline in the text, with the local time of the event, so nobody has to ask.

RSVPs without chasing anyone on WhatsApp

Replies come in inside the invitation, in one ordered list. You see who's coming and how many people they're bringing, instead of counting messages scattered across three chats. Guests answer on their phone in a couple of taps. You set the questions in the RSVP form, so it asks only what you'll actually use when you're laying the table.

Write the questions so they work for people with different needs. An open field — "anything we should know about your access to the venue?" — covers more ground than five yes/no boxes and lets each guest tell you what they need. Ask for the exact number too: "how many of you are coming?" saves you adding plus-ones by hand the week of the party.

An invitation with no steps of its own: one link, no app, no phone call to say yes.

Change the time without resending anything

If the venue moves or the cake slips an hour, you edit the invitation you already published and the link stays the same. Nobody gets a new message and nobody has to scroll back for the old one. Adding the map or changing the dress code doesn't mean reprinting anything or tracking down half the guest list.

Say the side entrance is closed for building work and everyone has to come round the back. You fix it in the venue scene and whoever opens the link sees today's version. That's the whole reason to send a web page instead of a card.

Paper, only for the people who keep it

The invitation is digital: nothing gets printed or posted. If someone in the family wants a copy for the memory box, the sensible combination is the link for everyone plus a handful of printed copies for the people who'll actually keep them. And be straight about the practical bit — guests need a phone, a tablet or a computer with a connection. Saying it plainly in the text heads off confusion on the day.

Pick a design, edit the cover in test mode without paying, and publish once the access details, the time and the RSVP questions read clearly. It's 29.99 EUR per invitation, a one-off payment, and the link stays the same even if you change something the week of the birthday.