Accessibility Statement
Last updated: May 2026
This statement applies to the Mapsoft PDF Hub web application at pdf.mapsoft.com, operated by Mapsoft Computer Services Limited ("we", "us", "our"). It does not cover content hosted on third-party domains or services we link to.
1. Our Commitment
We are committed to making PDF Hub accessible to as many people as possible, including users who rely on assistive technology, keyboard navigation, screen magnification, or reduced-motion settings. We aim to follow the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA and to keep improving the site as we identify gaps.
2. Conformance Status
PDF Hub is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully meet the standard. The known exceptions are listed under Known Limitations below.
The most recent self-assessment of the site against WCAG 2.1 AA was carried out in May 2026.
3. What We Have Done
We have taken the following concrete steps to make PDF Hub accessible:
- Semantic HTML and landmarks — every page uses
header,nav,main, andfooterlandmarks, with a logical heading hierarchy so screen-reader users can navigate by structure. - Keyboard support — navigation menus, dropdowns, forms, and dialogs are reachable and operable by keyboard alone.
- Skip link — a "Skip to content" link is the first focusable item on every page, allowing users to bypass the header and navigation.
- Visible focus indicators — all focusable elements display a clear focus ring when reached by keyboard or assistive technology.
- Labelled form controls — every form input has an associated label, required fields are marked with
aria-required, and validation errors are announced viarole="alert"live regions. - Live status announcements — processing overlays and result panels use
aria-liveso screen-reader users are notified when a PDF operation starts and completes. - Alt text on images — meaningful alternative text is provided for content images. Decorative images are marked so assistive technologies can skip them.
- Reduced-motion support — transitions and animations are minimised automatically for users who have enabled the
prefers-reduced-motionsetting in their operating system or browser. - Colour contrast — body text, links, and buttons aim to meet WCAG 2.1 AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI components).
- Colour is not the sole cue — form validation, links, and status messages use text or icons in addition to colour.
- Responsive and resizable — pages reflow at 400% zoom and on narrow mobile viewports without horizontal scrolling.
- Light and dark themes — signed-in users can choose a dark theme. The colour palettes are tuned to maintain contrast in both modes.
4. Known Limitations
We are aware of the following areas that do not yet fully meet WCAG 2.1 AA. We are working to address them:
- PDF tool result previews — some inline preview thumbnails of generated PDFs do not yet have descriptive alternative text. The download button beside each preview carries the file name as its accessible label.
- FastSpring checkout — the embedded subscription checkout is provided by our merchant of record, FastSpring. Its accessibility is governed by their own conformance.
- Documentation pages — our growing archive of help and FAQ pages has not been audited end-to-end. Heading structure may be inconsistent on a small number of pages.
- Third-party content — content embedded from external services (for example, YouTube videos and the FastSpring checkout) is governed by those providers' own accessibility standards and may differ from ours.
5. Accessibility Features in Your Browser
Your browser and operating system include built-in accessibility settings that work with PDF Hub:
- Text size — use your browser's zoom (Ctrl/Cmd + +) to enlarge the page up to 400% without losing content.
- Reduced motion — enable "Reduce motion" in your OS accessibility settings and our transitions will be minimised automatically.
- High contrast — Windows High Contrast mode and macOS Increase Contrast are supported by our colour scheme.
- Screen readers — the site has been tested with NVDA on Windows and is expected to work with VoiceOver on macOS/iOS, Narrator on Windows, and TalkBack on Android.
6. Reporting Accessibility Issues
If you encounter a barrier using PDF Hub, or if you need content in an alternative format, please let us know. We take all accessibility feedback seriously and aim to respond within five working days.
When reporting an issue, it helps us to know:
- The page URL where you encountered the problem.
- What you were trying to do.
- What happened (or didn't happen) that prevented you from doing it.
- The browser, operating system, and any assistive technology you were using.
Contact: support@mapsoft.com
7. Enforcement Procedure
If you contact us about an accessibility issue and are not satisfied with our response, you can escalate the matter to a regulator in your jurisdiction:
- United Kingdom — the Equality and Human Rights Commission (EHRC) enforces the Equality Act 2010.
- European Union — each member state has a designated enforcement body under the European Accessibility Act.
- United States — complaints relating to the ADA can be filed with the US Department of Justice.
8. Preparation of This Statement
This statement was prepared on . It is based on a self-assessment of the site against WCAG 2.1 Level AA using a combination of manual keyboard testing, screen-reader testing with NVDA, and automated scanning with axe-core and Lighthouse. We plan to review this statement at least annually, or whenever substantial changes are made to the site.