Making your practice website easier for everyone to use
Website accessibility means people with disabilities can use your website, including people who read with a screen reader, use a keyboard instead of a mouse…
The Kay & Co. resource library
Accessibility & mobile use
Make your website easier to read and use, including on phones and with tools that help people with disabilities.
Find an answer
Search a question, a task or a few words.
Search results
Matching resources
A useful starting point
Start here
Make page headings useful for people who listen to the website
Large bold text can look like a heading while accessibility tools treat it as an ordinary paragraph. Visitors navigating by headings then miss major sections.
Keep the answer visible above the phone keyboard
Opening a phone keyboard can cover the field being edited or the instruction explaining it. Visitors type without seeing the result and may not know how to…
The complete list
All accessibility & mobile use resources
Showing 1–24 of 81 resources, ordered by title.
Avoid reading hidden phone and desktop menus twice
Some websites include separate desktop and mobile copies of navigation or content. A visually hidden copy may remain available to screen readers or keyboard…
Choose fonts that make patient information comfortable to read
A distinctive font can work well in a logo and poorly in a long appointment instruction. Choose typefaces by trying the actual content people need to read,…
Distinguish a request being sent from a button waiting for information
A submitted button can fade to the same appearance as a permanently disabled button. Visitors cannot tell whether the system is working, awaiting more input…
Explain status labels in words as well as colours
Green, amber and red badges can convey different things to different visitors. Without readable state labels, a request list may be impossible to interpret…
Explain what makes an unavailable button usable
A faded button can tell visitors that an action cannot be used without explaining what would make it available. The missing step may be somewhere outside…
Explain what Select all includes before a grouped action
A selection checkbox above a table can mean the visible rows, the current page or all filtered records. Visitors may trigger a much broader action than they…
Give maps, booking tools and other embedded tasks clear names
Several embedded frames can appear as unnamed regions to accessibility tools. Visitors cannot distinguish a booking widget from a map or document viewer…
Give moving carousels a reliable pause control
A rotating carousel can replace a card while someone is reading it or move a link just before activation. The timing is particularly difficult for slower…
Give repeated Read more links a recognisable destination
A collection of cards may end with identical Read more links. In a screen reader's links list, visitors cannot distinguish which service or resource each…
Give staff colour combinations they can use confidently
A palette of attractive colours does not tell staff which combinations work for text, buttons or notices. Ask your designer to supply tested pairings and…
Give visitors a clear route to the page's main information
A page may identify the header, several cards and the footer as separate main regions, or expose none at all. Assistive navigation then offers no reliable…
Give visitors a useful alternative when video will not play
A failed media embed can leave a blank rectangle, a permanent spinner or a generic provider error. Visitors cannot tell whether waiting will help or where…
Keep button words readable when people point to or select them
A button may pass a visual review in its default state but change to a pale combination on hover or focus. Interaction makes the action harder to read.
Keep captions visible while video controls are shown
Captions can sit beneath playback controls, branding or a persistent call-to-action overlay. The visitor enables them but cannot read complete lines at the…
Keep controls visible in the phone or computer's contrast settings
Custom icons, check marks and focus rings can disappear when a user enables system contrast settings. The page retains text but loses the cues needed to…
Keep decorative icons from interrupting spoken reading
Repeated arrows, ticks and ornamental symbols can be announced as unexplained characters or file names. Visitors hear noise between otherwise useful labels…
Keep expanded table details tied to the item they describe
A table row can reveal an extra panel without making clear which record it belongs to. After sorting or expanding several rows, details may appear attached…
Keep fixed contact buttons clear of phone edges and gestures
A fixed action bar can sit against a phone's gesture area or curved screen edge. Its lower controls may be hard to press or partly hidden by device furniture.
Keep form answers when a phone rotates
Changing orientation can reload an embedded form or reset a custom control. Visitors who rotate their phone for easier reading may unexpectedly lose…
Keep form buttons reachable when text is enlarged
A form's buttons can sit inside a fixed-height panel that becomes too short when text enlarges. Visitors can read the questions but cannot reach Continue or…
Keep keyboard-selected controls visible beneath fixed banners
A fixed announcement or cookie banner may cover the control receiving keyboard focus. Visitors can keep pressing Tab without knowing where the next action…
Keep labels when a mobile table becomes cards
A table can transform into stacked cards on small screens while losing the column headings. Visitors see several values without knowing which is a location,…
Keep long page headings readable on phones
Large headings can break into isolated fragments or overflow on small screens. A word split into individual letters makes the page harder to recognise and…
Keep people oriented after removing a file or filter
Removing a selected filter or attachment can delete the control that currently has focus. The next keyboard action may restart at the page top or affect an…