Company
Accessibility
What this website does for accessibility, where it falls short, and how to tell us about a problem.
Our aim
SpoolSwift aims for this website to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This is an aim, not a claim that the site conforms.
What this site does
- A Skip to content link is the first thing the keyboard reaches on every page. It jumps past the header to the page itself.
- Links and buttons show a 2px outline when you reach them with the keyboard.
- Each page has one main heading.
- Every page is marked as English, so screen readers pronounce it as English.
- Pictures of SpoolSwift's screens, such as the example floor, queue and phone card, are described in words for screen readers.
- Nothing on the site animates, and its styles turn transitions and smooth scrolling off when your device asks for reduced motion.
- In the header, the Features button tells screen readers whether its menu is open, Escape closes the menu, and the link to the page you are on is marked as the current page.
- Questions in the FAQ lists open and close from the keyboard and work without JavaScript.
- On the demo printer, the printer's status is announced to screen readers when it changes, and when the card moves to its next step, the keyboard focus moves to that step's heading.
- On the homepage, the QR code for the demo printer is also a link, so the demo opens without a phone camera.
- Buttons, and links that stand on their own, are at least 44px tall in the header, the Features menu, the footer, the demo printer and the content of each page. A link inside a sentence is the height of the text around it.
Known limits
- This site has not had an independent accessibility audit.
- This page covers this website only. It does not describe the accessibility of the SpoolSwift app you sign in to.
- The site has a dark colour scheme only. It does not switch to light colours when your device is set to light mode.
Report a problem
If something on this site is hard to use, write to [email protected]. Tell us the page and what went wrong. If you can, say which browser you use and any assistive technology, such as a screen reader.