Accessibility Statement Version 1.0 Our commitment to making Propvora usable by as many people as possible, how accessible it is today, its known gaps, and how to get help or an alternative format. 1. About this statement This Accessibility Statement is published by Blackwellen Limited (Blackwellen, we, us), company number 16482166, registered office 61 Bridge Street, Kington, Herefordshire, HR5 3DJ, United Kingdom. It applies to Propvora, which includes the public website at propvora.com, the sign-in and registration pages, the Propvora application (including workspaces, supplier workspaces and customer homes), the portals we provide for tenants, landlords, owners and investors, applicants, guarantors, contractors and leaseholders, and the emails and documents the Service generates (together, the Service). We want as many people as possible to be able to use the Service. That includes our Customers and their teams, and also the tenants, applicants, contractors and others who use our portals or receive communications sent through Propvora, many of whom did not choose Propvora and should not be disadvantaged by it. For example, you should be able to: - change colours, contrast levels and fonts using browser or device settings; - zoom in up to 400% without the text spilling off the screen; - navigate most of the Service using just a keyboard; - navigate most of the Service using speech recognition software; - use most of the Service with a screen reader, including recent versions of NVDA, JAWS and VoiceOver; and - reduce or switch off non-essential animation. We have also tried to make the text as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability. 2. Our standard Our target is the Web Content Accessibility Guidelines version 2.2, level AA (WCAG 2.2 AA), published by the World Wide Web Consortium. WCAG 2.2 AA is the standard used by UK public sector bodies under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. Those regulations do not apply to Blackwellen as a private company, but we use the same standard and the same style of statement because it gives users a clear, recognised benchmark. As a service provider, we also have duties under the Equality Act 2010, including the duty to make reasonable adjustments so that disabled people are not placed at a substantial disadvantage. Our Customers, such as landlords and letting agents, have their own duties towards their tenants and clients, which section 15 (Making your own communications accessible) is intended to support. We apply WCAG 2.2 AA when we design and build new features, and we prioritise fixing accessibility issues reported by users. 3. Compliance status The Service is partially conformant with WCAG 2.2 AA. Partially conformant means that some parts of the Service do not yet fully meet the standard. This assessment is based on our own testing during development, described in section 19 (How we tested). We have not yet commissioned a full independent accessibility audit of the Service. We plan to do so, and we will update this statement, including the list of known limitations in section 14, once the audit is complete. We would rather tell you honestly that we are not yet fully conformant than claim a level of accessibility we have not verified. 4. Accessibility features The Service has been designed with the following features: - Keyboard navigation: interactive controls are designed to be reachable and usable with a keyboard, in a logical order, with a visible focus indicator. A Skip to content link at the top of pages lets keyboard users bypass repeated navigation. Menus, dialogs and drawers are designed to be opened, used and closed with the keyboard, and to return focus to a sensible place when closed. - Reduced motion: the Service respects the prefers-reduced-motion setting in your operating system. When it is turned on, decorative animations and scroll effects are reduced or removed. We do not use flashing content. - Zoom and reflow: layouts are responsive and are designed to reflow at widths down to 320 CSS pixels, equivalent to 400% zoom on a 1280-pixel-wide screen, without requiring horizontal scrolling for most content. Data tables and some complex views are exceptions, described in section 14. - Colour and contrast: our design system sets text colours to aim for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text and for interface components such as input borders and focus indicators. Status is not shown by colour alone; status chips also include text labels and, where appropriate, icons. - Structure: pages use headings, landmarks and lists so that assistive technologies can present their structure. Each page has a descriptive title. - Forms: form fields have visible labels, required fields are indicated in text as well as visually, and errors are described in words next to the field concerned, with guidance on how to fix them. - Text resizing: text uses relative sizes so that it scales with browser settings, and the interface avoids putting important text inside images. - Target size: buttons and other controls are designed to meet WCAG 2.2's minimum target size, so they are easier to use with a touch screen or for people with limited dexterity. 5. Supported browsers and assistive technologies The Service is designed to work with current versions of the following browsers, on desktop and mobile: - Google Chrome and Microsoft Edge; - Mozilla Firefox; and - Apple Safari on macOS and iOS. It is designed to be compatible with the following assistive technologies: - screen readers, including NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android; - browser and operating system zoom and magnification, including ZoomText and built-in magnifiers; - speech recognition software, such as Dragon and Voice Control; and - operating system settings for high contrast, forced colours, text size and reduced motion. The Service relies on HTML, WAI-ARIA, CSS and JavaScript. It does not work with JavaScript turned off. Older browsers and assistive technologies may work but are not something we test against. 6. Public website Our public website includes the home page, features, pricing, solutions, about, partner programme, contact and legal pages. These pages use a consistent layout with a header, main navigation and footer, and they are built with semantic headings and landmarks. - Navigation: the main menu and any expanded menus can be operated with a keyboard and close with the Escape key. On small screens, navigation moves into a menu button that announces whether it is open or closed. - Images: informative images have text alternatives. Decorative images and illustrations are hidden from screen readers. Product screenshots and illustrative interface mock-ups are described in the surrounding text or labelled with alternative text summarising what they show. - Animation: some sections reveal content with gentle animation as you scroll. These effects are reduced when prefers-reduced-motion is set, and content is never hidden permanently behind an animation. - Pricing: plan prices, limits and features are given as text, not only in images or icons, and comparison tables include header cells so screen readers can announce which plan and feature each cell relates to. - Legal pages: our legal documents, including this statement, are presented as structured HTML with numbered headings and a key-points summary, so they can be navigated by heading and read with assistive technology. 7. Sign-in, registration and account security We have designed sign-in and registration with WCAG 2.2's accessible authentication requirement in mind, so that you are not required to solve a puzzle, transcribe characters or remember information in order to sign in. - Password managers: password fields support browser and third-party password managers, and allow pasting, so you do not need to type or memorise a password. - Google sign-in: you can sign in with your Google account, which can reduce the need to type credentials. - Multi-factor codes: where you use multi-factor authentication, the code field is designed to accept pasted codes and one-time-code autofill where your device offers it. - Errors: sign-in and registration errors are shown in text and announced to screen readers, and they tell you how to put the problem right, without revealing information that would weaken security. - Time limits: sign-in links and codes expire for security reasons. If one expires, you can request a new one without losing information you have already entered elsewhere in the process. - Multi-step registration: steps are numbered with a progress indicator, and information you have already provided is carried forward rather than requested again. We do not use image-based CAPTCHA on sign-in. If we introduce bot protection in future, we will choose a method that does not depend on a cognitive function test, or provide an accessible alternative. 8. The Propvora application and workspaces The application includes a sidebar and top bar, dashboards, list and table views, board views, calendar and timeline views, detail pages with tabs, forms and wizards, and settings. Its density and number of views mean it is the part of the Service where accessibility is most demanding. - Consistent navigation: the sidebar, top bar, breadcrumbs and back buttons appear in the same places throughout, and help is found in a consistent place. - Tables and lists: tables use proper header cells. Sorting controls announce the current sort order. Most list views can also be shown as cards, which reflow better on narrow screens and at high zoom. - Board views: where records can be moved between columns by dragging, WCAG 2.2 requires a single-pointer alternative to dragging. Records can also be moved by editing their status in the record itself, without dragging. - Calendars and timelines: events shown on calendars, timelines and Gantt-style views are also available as lists or on the relevant record, so that the information does not depend on interpreting a visual layout. - Charts and dashboards: charts include text summaries or the key figures as text, and use patterns, labels or direct annotation rather than colour alone to distinguish series. - Dialogs and drawers: focus moves into a dialog when it opens, is kept within it while it is open, and returns to the triggering control when it closes. Destructive actions ask for confirmation in clear language. - Status messages: confirmations such as saved, sent or failed are announced to screen readers without moving focus. - Sessions: if your session expires, you are asked to sign in again; drafts are saved where the feature supports it, so that work is not lost. 9. Portals Portals let people outside a Customer's organisation, such as tenants, landlords, owners and investors, applicants, guarantors, contractors and leaseholders, view information shared with them and take simple actions, such as reporting a repair, uploading a document or updating a job. Because portal users did not choose Propvora and may use it rarely, we keep portals simpler than the main application: fewer options per page, plain language, large controls, and a mobile-first layout that works well on phones. Portal forms follow the same labelling and error-handling approach as the rest of the Service. - Repair reporting: you can describe a problem in text. Photos are optional unless the Customer has asked for them, and we encourage Customers not to make photo upload the only way to report a problem. - Uploads: upload controls can be used with a keyboard as well as by dragging and dropping, and tell you which file types and sizes are accepted. - Content from Customers: much of what appears in a portal, such as messages, notices and documents, is written by the landlord or agent, not by us. Its accessibility depends on how it is written; see section 15. If you use a portal and cannot do something because of an accessibility barrier, you can contact the landlord or agent who invited you, and you can also tell us directly using the details in section 17. 10. Documents and PDFs The Service stores documents that Customers upload, such as tenancy agreements, safety certificates, inspection reports and invoices, and it generates some documents itself, such as reports and exports. - Uploaded documents: we cannot control the accessibility of documents that Customers or third parties upload. Scanned certificates, for example, may be images with no text layer that a screen reader cannot read. Where you need such a document in an accessible format, ask the Customer who uploaded it. - Generated documents: where the Service generates PDFs, we aim to include a document title, a logical reading order and real text rather than images of text. Generated PDFs are not yet fully tagged for accessibility, which is listed as a known limitation in section 14. - Exports: where the Service offers data export, such as CSV, the exported file can be opened in spreadsheet software and used with assistive technology. - Previews: in-app document previews are a convenience. You can always download the original file and open it in a reader of your choice. 11. AI features The Propvora Agent (Beta) and other AI features can help some users, for example by summarising long records, explaining what is on a page, or drafting text in plain language. We aim to make the AI features themselves accessible: - the Agent panel can be opened, used and closed with a keyboard; - responses are added to the conversation as text that screen readers can read, and we aim to announce them when they are complete rather than word by word, to avoid excessive announcements; - AI-generated content is labelled in text, not only by an icon or colour; and - actions proposed by AI are presented for confirmation using standard buttons, in the same way as other actions in the Service. AI Outputs can be wrong. People who rely on assistive technology may find it harder to cross-check an Output against the source records, so we encourage Customers to review AI-drafted communications with particular care before sending them, and to offer recipients a way to ask a person. Our AI Disclaimer and AI Use Policy (/legal/ai-disclaimer) explains the limits of the AI features. You can also ask the Agent to rewrite a draft in plainer language or a simpler structure, which can help make communications easier to understand. 12. Emails We send transactional emails, such as sign-in links, invitations, notifications and billing receipts, and Customers send emails to their contacts through the Service. - Our email templates are designed to use a single-column layout, real text rather than images of text, sufficient colour contrast and descriptive link text. - Important information is included in the text of the email, not only in an image or attachment. - Buttons in emails are links with clear labels, and the destination address is shown where that helps people who cannot use the button. - We aim to include a plain-text version of our emails for email clients and assistive technologies that prefer it. How an email displays depends partly on the recipient's email client, which we do not control. The content of emails written by Customers is the Customer's responsibility (see section 15). 13. Third-party components Some parts of the Service are provided by third parties. We choose providers with accessibility in mind, but we do not control their interfaces. - Stripe Checkout and billing portal: payments and subscription management are handled on pages provided by Stripe. Stripe publishes its own information about accessibility. If you cannot complete a payment because of an accessibility barrier, contact us and we will help you find another way to pay or manage your subscription. - Maps: some pages show properties or jobs on an interactive map provided through MapTiler. Maps are a visual tool and can be hard to use with a keyboard or a screen reader. The same information, such as addresses and locations, is always available in text in list or detail views, so you do not need to use the map. - Google sign-in: the Google sign-in window is provided by Google. - Embedded content: where we embed content from other providers, such as videos, we aim to choose players that support keyboard use and captions. 14. Known limitations We know that some parts of the Service are not yet fully accessible. Based on our own testing, the following limitations apply at the date of this statement: - Dense data tables: some wide tables require horizontal scrolling at high zoom or on narrow screens, which may not meet the reflow criterion (WCAG 1.4.10). Card views and record pages provide an alternative for most of them. - Complex visual views: some board, calendar, timeline and chart views may not be fully operable or understandable with a screen reader alone. The same information is available in list or detail views. - Maps: interactive maps are not fully accessible to keyboard and screen reader users (see section 13). Text alternatives are provided. - Generated PDFs: PDFs generated by the Service are not yet fully tagged (WCAG 1.3.1 and 4.1.2 as applied to documents). - Third-party content: documents and messages uploaded or written by Customers and others may not be accessible (see sections 10 and 15). [Blackwellen to complete after audit: list of specific non-conformances identified by the full WCAG 2.2 AA audit, with the WCAG success criterion, the affected area of the Service, and the planned fix date for each.] We are working to fix these issues, starting with those that have the greatest impact on people's ability to complete key tasks, such as signing in, reporting a repair, reading a notice and paying a bill. 15. Making your own communications accessible If you are a landlord, agent or property manager using Propvora, much of what your tenants and other contacts see, such as messages, notices, letters, documents and portal content, is written or uploaded by you. You are responsible for that content, and you may have your own duties under the Equality Act 2010 to make reasonable adjustments for disabled tenants and applicants. These steps will help: 1. Write clearly. Use plain English, short sentences and headings. Put the most important information, such as what the person needs to do and by when, at the start. 2. Don't rely on attachments alone. Put the key information in the body of the message, and attach the formal document as well where one is required. 3. Use real text in documents. Upload documents created from a word processor rather than scans where you can. If you must upload a scan, run it through text recognition (OCR) first. 4. Make PDFs accessible. When you create a PDF, use your software's accessibility options: add a document title, use real headings, add alternative text to images and check the reading order. 5. Describe images. When sharing photos, for example of a repair, add a short text description of what the photo shows. 6. Write meaningful links. Use link text that describes where the link goes, such as 'View your tenancy agreement', rather than 'click here'. 7. Don't use colour alone. Don't rely on colour to show meaning, for example by marking overdue items only in red. 8. Offer alternatives. Tell people how they can ask for information in another format or by another method, and make sure someone in your team can respond. 9. Record adjustments. Where a contact has asked for an adjustment, such as large print, a phone call before visits, or communication through a named representative, record it on their contact record so that your whole team knows. 10. Check AI drafts. Review AI-drafted messages for clarity and tone before sending them, and ask the Agent to simplify the language if needed. Propvora is a tool to help you communicate. Using it does not transfer your legal responsibilities to tenants or applicants to us. 16. Requesting an alternative format If you need information about the Service, or any of our own documents, such as our Terms of Service (/legal/terms), Privacy Notice (/legal/privacy) or invoices, in a different format, such as large print, an accessible PDF, plain text, Easy Read or audio, email info@blackwellen.com (mailto:info@blackwellen.com) with the subject line "Accessibility request". Please tell us: - the web address or name of the document or page; - the format you need; and - the email address or postal address where you would like to receive it. We will tell you how long it will take to provide the format you have asked for. If we cannot provide that format, we will explain why and offer the most suitable alternative. If the information you need is held in a Customer's workspace, such as your tenancy agreement or a notice from your landlord, please ask the landlord or agent who provided it, as they are responsible for the content. If they are unable to help, you can contact us and we will do what we reasonably can to support them. 17. Feedback and contact We welcome feedback about the accessibility of the Service, including problems not listed in this statement, and suggestions for improvement. - Email: info@blackwellen.com (mailto:info@blackwellen.com), with the subject line "Accessibility". - Post: Accessibility, Blackwellen Limited, 61 Bridge Street, Kington, Herefordshire, HR5 3DJ, United Kingdom. When you contact us, it helps to tell us the page or feature concerned, what you were trying to do, the device, browser and any assistive technology you were using, and what happened. We aim to acknowledge accessibility feedback within 5 working days, and to respond fully, or tell you what we are doing and by when, within 20 working days. Where a barrier stops you from completing an essential task, such as accessing your account, paying a bill or reporting an urgent repair, please say so and we will prioritise it and help you find another way to complete the task in the meantime. If you are not satisfied with our response, you can make a complaint under our Complaints Procedure (/legal/complaints). 18. Enforcement The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010 in England, Scotland and Wales. In Northern Ireland, the Equality Commission for Northern Ireland has that role under the equivalent legislation. If you have contacted us and you are not happy with how we responded, you can contact the Equality Advisory and Support Service (EASS) for free advice about your rights under the Equality Act 2010. In Northern Ireland, you can contact the Equality Commission for Northern Ireland. Making a complaint to us does not prevent you from taking any other action available to you under the law. 19. How we tested Our current assessment is a self-assessment by our own team during development, using methods such as: - automated accessibility checks of key pages using browser-based tools, such as Lighthouse; - manual keyboard-only testing of key journeys, including signing up, signing in, creating records, and using portals; - checks of colour contrast in our design system; - testing layouts at 320 CSS pixels wide and at increased zoom; and - testing with the prefers-reduced-motion setting turned on. Automated tools find only some accessibility issues, and our own team is not a substitute for testing by disabled users or an independent specialist. That is why we describe the Service as partially conformant and plan a full audit (see section 3). 20. Preparation of this statement This statement was prepared on 3 October 2026. It is based on a self-assessment by Blackwellen, as described in section 19. We will review this statement at least once a year, after any full or partial audit, and whenever we make significant changes to the Service. The next review is planned for the full WCAG 2.2 AA audit, within 12 months of the date this statement was last updated, when we will replace the general list of limitations in section 14 with the specific findings of that audit.