SkyKente is committed to providing an inclusive and accessible digital property experience for all users, including people with disabilities, older persons, users of assistive technologies, users with temporary impairments, and people accessing the Platform through different devices, browsers, network conditions, and input methods.

This Accessibility Statement explains the principles, practices, features, limitations, support options, and continuous improvement measures that apply to the SkyKente website, mobile applications, public property pages, agency dashboards, tenant services, forms, communications, documents, and related digital services collectively referred to as the "Platform".

We aim to make the Platform perceivable, operable, understandable, and robust so that users can search for property, submit enquiries, manage accounts, complete forms, access tenancy information, review payments, report maintenance issues, and obtain support without unnecessary barriers.

Accessibility is an ongoing responsibility rather than a one-time project. As SkyKente develops new features and improves existing services, we seek to review accessibility throughout design, development, testing, content creation, quality assurance, and customer support.

We recognise that no digital service is perfect. Some areas of the Platform, including older components, uploaded documents, third-party property content, maps, embedded tools, or external integrations, may not yet provide the same level of accessibility.

If an accessibility issue prevents you from completing an important task, please contact us. We will make reasonable efforts to provide support, offer an alternative method, or review the reported barrier.

1. Our Accessibility Commitment

SkyKente seeks to ensure that property information, Platform services, support channels, and essential account functions are accessible to the widest reasonable range of users.

Our accessibility approach is informed by recognised digital accessibility principles and guidance, including the Web Content Accessibility Guidelines, commonly referred to as WCAG.

We aim to work towards an appropriate level of conformance with WCAG 2.1 or later applicable guidance, particularly Level AA success criteria, where reasonably achievable and relevant to the Platform.

Reference to an accessibility standard does not mean that every page, document, integration, or third-party item is guaranteed to conform fully at all times.

Accessibility considerations may include visual, auditory, physical, speech, cognitive, language, learning, neurological, and temporary impairments.

We seek to avoid treating disability as a reason to deny access to property information, account services, support, communication, or other Platform features.

Where a user requires reasonable assistance to complete an essential Platform task, we encourage the user to contact our support team so that an appropriate alternative may be considered.

2. Accessibility Principles

Our accessibility work is guided by four broad principles.

Perceivable: Information and interface elements should be presented in ways that users can perceive, including through text, visual presentation, screen readers, zoom, captions, labels, and alternative descriptions where appropriate.

Operable: Users should be able to navigate and use important Platform features with different input methods, including a keyboard where technically supported.

Understandable: Content, labels, instructions, navigation, validation messages, and workflows should be reasonably clear, predictable, and consistent.

Robust: Platform components should use appropriate semantic structure and technologies so that content can be interpreted by supported browsers, devices, and assistive technologies.

3. Content Structure and Readability

We aim to organise public and account-based pages using logical headings, paragraphs, labels, sections, navigation landmarks, and descriptive content.

Page headings are intended to follow a meaningful hierarchy so that users can understand the relationship between sections and navigate using assistive technologies.

We seek to use concise labels, readable sentence structures, descriptive buttons, meaningful links, and instructions that explain the action a user is expected to take.

Link wording should, where reasonably possible, explain the destination or purpose of the link rather than relying only on vague phrases such as "click here".

We aim to avoid relying solely on colour, shape, position, sound, or visual appearance to communicate important meaning.

Important alerts, errors, payment statuses, application statuses, and maintenance updates should include text or another understandable indication in addition to colour where practicable.

Content may vary in readability where descriptions, documents, images, or other information are submitted directly by property agencies, owners, developers, tenants, contractors, or other users.

4. Keyboard Navigation

We aim to make essential interactive controls, including links, buttons, form fields, menus, modal windows, and account actions, available through keyboard navigation where the relevant technology supports it.

Users should generally be able to move through interactive elements using the Tab and Shift plus Tab keys and activate supported controls using Enter or Space.

We aim to provide visible focus indicators so that keyboard users can identify which element is currently active.

The intended focus order should follow the logical reading and interaction sequence of the page.

Where a modal, menu, dropdown, gallery, or interactive component opens, we seek to manage focus in a manner that helps users understand the change in context.

Some complex maps, third-party widgets, legacy controls, image galleries, or embedded services may not currently provide complete keyboard functionality.

If keyboard navigation prevents you from completing a property enquiry, application, payment review, maintenance request, or another essential action, contact our support team for assistance.

5. Screen Readers and Assistive Technologies

SkyKente aims to use semantic HTML, accessible labels, meaningful headings, form associations, navigation landmarks, status information, and other markup that supports commonly used assistive technologies.

Images that communicate important information should include meaningful alternative text where SkyKente controls the image and appropriate text can reasonably be provided.

Decorative images may use empty alternative text or other methods intended to prevent unnecessary announcements by screen readers.

Icons used as interactive controls should include accessible names or accompanying text where appropriate.

Form fields should, where possible, have labels that explain the information required rather than depending only on placeholder text.

Dynamic content, alerts, validation messages, changes in application status, and other updates may require additional improvements to ensure consistent announcement across different screen readers and browsers.

Assistive technology behaviour can vary according to the operating system, browser, application version, device settings, and technology configuration used.

6. Visual Presentation, Contrast and Zoom

We aim to use readable type sizes, spacing, visual hierarchy, and colour contrast that support users with low vision, colour-vision differences, reading difficulties, or other visual needs.

Important text and interactive controls should have sufficient contrast against their background where reasonably achievable.

Users may use browser zoom, operating-system magnification, text scaling, or device accessibility settings to enlarge Platform content.

We aim for important public pages and essential forms to remain usable when zoomed or displayed on smaller screens without requiring unnecessary horizontal scrolling.

Some tables, maps, large images, dashboards, charts, property galleries, or third-party components may require horizontal movement or an alternative view at high zoom levels.

Users may also use browser-level high-contrast modes, colour overrides, reader modes, or custom stylesheets, although the Platform may not fully support every configuration.

7. Mobile and Responsive Accessibility

SkyKente is designed to support desktop, tablet, and mobile access through responsive layouts.

We aim to ensure that important information, navigation, buttons, forms, property cards, account controls, and support options remain reasonably usable across supported screen sizes.

Interactive controls should be sufficiently separated and sized where practicable to help users with limited dexterity, motor impairments, tremors, or touch accuracy difficulties.

The Platform should not require a particular screen orientation unless the function reasonably depends on it.

Mobile accessibility may also depend on the accessibility features, text-size settings, screen reader, operating-system version, browser, and device used.

Some older devices or unsupported browsers may not display or operate all Platform features correctly.

8. Forms and User Input

SkyKente includes account registration, contact, property enquiry, property application, payment, maintenance, listing, reporting, support, and administrative forms.

We aim to provide labels, instructions, required field indicators, input types, examples, and validation messages that help users understand what information is required.

Where an error occurs, we seek to identify the relevant field and explain the issue in text rather than indicating the error through colour alone.

Users should, where technically possible, have an opportunity to review important information before completing a significant submission, application, payment, or account change.

Time limits should be avoided where they are not necessary. Where a session timeout is required for security, the Platform may provide a warning or an opportunity to continue the session where reasonably practical.

File-upload controls may be more difficult to use with some assistive technologies. Users who cannot upload a requested document should contact the relevant agency or SkyKente support to discuss an alternative method.

CAPTCHA, identity-verification, payment-provider, or anti-fraud tools supplied by third parties may have their own accessibility limitations.

9. Authentication and Account Access

Account security may require passwords, authentication codes, personal identification numbers, biometric features, email verification, device confirmation, or other methods.

We aim to make authentication instructions clear and to avoid unnecessary memory or cognitive burdens where secure alternatives are reasonably available.

Authentication codes may expire for security reasons. Users who require additional time or experience repeated difficulties should request a new code or contact support.

Biometric authentication depends on the user's device and operating-system accessibility features and may not be available on every device.

Users who cannot use a particular authentication method may contact support to determine whether another secure verification method is available.

Accessibility support will not remove the need to verify identity, protect account security, or prevent unauthorised disclosure of personal information.

10. Images, Galleries and Property Media

Property listings may include photographs, image galleries, floor plans, virtual tours, videos, maps, diagrams, brochures, and other visual media.

Where SkyKente directly creates or controls important visual content, we aim to provide appropriate text descriptions, captions, labels, or nearby explanatory content.

Many property images and descriptions are uploaded by agencies, landlords, owners, developers, and other third parties.

As a result, some images may not include complete alternative text or may rely on captions and listing descriptions supplied by the uploader.

Property images are intended to support, rather than replace, written information such as price, location, unit type, amenities, dimensions, availability, and contact details.

Users who cannot access important information shown only in an image, floor plan, virtual tour, or video may request a text explanation from the relevant listing party or SkyKente support.

11. Video, Audio and Time-Based Media

Where SkyKente publishes video or audio content containing important spoken information, we aim to provide captions, transcripts, summaries, or another accessible alternative where reasonably practicable.

Recorded property tours, promotional videos, webinars, support recordings, or media uploaded by third parties may not always include captions, audio description, or transcripts.

Videos should not automatically play audio where doing so would create unnecessary disruption.

Users should be able to pause, stop, mute, or control supported media where the media player provides those functions.

Content containing flashing or rapidly changing imagery should be avoided where it could create a foreseeable risk to users with photosensitive conditions.

Users may contact us to request a text alternative for important SkyKente-controlled media that is not otherwise accessible.

12. Animation and Reduced Motion

The Platform may use transitions, scrolling effects, loading indicators, carousels, modal windows, hover effects, and other animations.

We aim to avoid unnecessary motion that could distract users, create discomfort, interfere with concentration, or trigger vestibular symptoms.

Where technically supported, the Platform may respect operating-system or browser preferences requesting reduced motion.

Essential loading or status indicators may still use limited movement where necessary to communicate that an action is processing.

Automatically moving carousels or promotional content should provide suitable controls or stop movement where reasonably practicable.

Users who experience difficulties with motion may enable reduced-motion settings on their device or browser and report components that continue to create barriers.

13. Maps and Location-Based Features

SkyKente may use maps to display property locations, nearby services, directions, geographic search results, and other location information.

Interactive maps can present accessibility challenges for keyboard users, screen-reader users, users with low vision, and users with certain motor or cognitive impairments.

We aim to support maps with nearby textual information such as the property address, suburb, city, county, neighbourhood, location description, or contact details where available.

A map marker or geographic visualisation should not be the only means of identifying a property's location where useful text information can reasonably be provided.

Location information may be supplied by property owners, agencies, users, or third-party mapping providers and may not always be complete or exact.

Users who cannot operate a map may contact the listing party or SkyKente support for a textual description or alternative assistance.

14. Documents and Downloadable Files

The Platform may provide access to leases, invoices, receipts, reports, brochures, legal notices, application forms, inspection records, statements, and other downloadable documents.

We aim to create SkyKente-controlled documents with logical reading order, selectable text, meaningful headings, descriptive links, adequate contrast, and appropriately labelled information where reasonably practicable.

Some older documents, scanned copies, image-only files, third-party brochures, uploaded leases, property plans, or agency-generated reports may not be fully accessible.

A scanned document may require optical character recognition or a separately prepared accessible version before it can be read effectively by assistive technology.

Users who cannot access an important document may request the information in another reasonable format, such as accessible text, email, HTML, a readable PDF, or verbal assistance, subject to availability and legal requirements.

A request for an alternative format may require identity verification where the document contains confidential, tenancy, financial, or personal information.

15. Language and Cognitive Accessibility

We aim to use plain, direct, and understandable language for important public information, instructions, forms, error messages, and support content.

Legal, financial, technical, tenancy, and property-management information may sometimes require specialised terminology.

Where practical, specialised terms should be explained through nearby context, examples, support content, or help resources.

Consistent navigation, predictable layouts, clear calls to action, step-by-step processes, and visible status indicators may assist users with cognitive, learning, memory, attention, or language-related needs.

We aim to avoid unnecessarily complex instructions, unexpected navigation, ambiguous labels, and excessive information in a single step.

Users who do not understand a process may contact SkyKente or the relevant agency for assistance, but support information does not replace independent legal, financial, or professional advice.

16. Third-Party Content and Services

SkyKente may display content supplied by property agencies, landlords, owners, developers, contractors, advertisers, and other users.

It may also integrate with payment providers, mobile-money operators, banks, mapping services, social-media platforms, document tools, communication providers, analytics systems, identity-verification tools, and other external services.

Third-party content and services may follow their own accessibility standards, technical practices, support procedures, and legal responsibilities.

SkyKente may not be able to directly modify the accessibility of an external website, embedded component, payment page, map, document, or third-party application.

We encourage third parties using the Platform to provide accurate text descriptions, accessible documents, clear contact details, and reasonable alternative methods.

If a third-party component prevents you from completing an important SkyKente-related task, contact us and describe the affected service. We may be able to provide guidance, an alternative workflow, or information about the responsible provider.

17. Responsibilities of Agencies and Listing Providers

Agencies, landlords, owners, developers, and other listing providers are responsible for the property information, media, documents, and communications they submit to SkyKente.

Listing providers should use clear property titles, meaningful descriptions, accurate contact information, understandable prices, and relevant written details that do not depend entirely on photographs or visual presentation.

Where possible, important property features should be described in text, including floor access, lifts, stairs, parking, entrances, bathrooms, accessibility features, door widths, terrain, and other information that may affect a user's decision.

Property providers should avoid publishing image-only documents where an accessible electronic format can reasonably be supplied.

Agencies and landlords should provide reasonable communication alternatives for users who cannot access a particular enquiry form, document, application process, or viewing arrangement.

SkyKente may request corrections or improvements where uploaded content creates a material accessibility or usability barrier, although we cannot guarantee that every third-party item will be made accessible.

18. Accessible Customer Support

SkyKente aims to provide clear support paths for users who experience accessibility barriers.

Users may contact us by email, telephone, the Contact Us page, or available account support channels.

When contacting us, you may explain your preferred communication method and whether you require the response in a particular reasonable format.

Support staff may need to ask questions about the page, device, browser, assistive technology, account, action, or error involved so that the issue can be understood and reproduced.

Support personnel will not ask you to disclose your full password, mobile-money PIN, card PIN, or complete payment credentials.

Where support requires access to confidential account information, reasonable identity verification may be required before assistance is provided.

Accessibility support does not guarantee that SkyKente can complete a legal, contractual, payment, application, or property decision on behalf of the user.

19. Alternative Access and Reasonable Assistance

If an accessibility barrier prevents a user from accessing important information or completing an essential Platform action, SkyKente may consider a reasonable alternative method.

Alternatives may include providing information through email, telephone support, readable text, an alternative document, guided assistance, or referral to the relevant agency, landlord, property owner, or service provider.

The appropriate alternative will depend on the nature of the request, available technology, legal requirements, identity-verification needs, confidentiality obligations, security risks, and whether another organisation controls the relevant information.

An alternative access request should identify the information or task required, the barrier encountered, and the format or assistance that would be useful.

We will seek to avoid imposing an unnecessary additional charge solely because a user requests a reasonable accessible alternative for SkyKente-controlled information.

Where a request would fundamentally change the service, compromise security, disclose another person's information, conflict with law, or create a disproportionate burden, we may propose another reasonable option.

20. Known and Potential Limitations

Despite our efforts, some Platform areas may not yet meet the accessibility standard we are working towards.

Potential limitations may include interactive maps that are difficult to operate using certain screen readers or keyboard controls.

Some property images may not have complete alternative descriptions because they were uploaded by third-party listing providers.

Older documents, scanned leases, brochures, floor plans, invoices, and image-based files may not contain selectable text or an appropriate reading order.

Some dashboards, tables, charts, calendars, image galleries, modal windows, or complex administrative workflows may require additional keyboard, screen-reader, zoom, or focus improvements.

Third-party payment pages, identity-verification systems, embedded media, maps, CAPTCHAs, and external websites may not follow the same accessibility practices as SkyKente.

Automatically generated content, user-submitted descriptions, and imported records may contain unclear language, missing labels, inconsistent formatting, or other accessibility issues.

We use feedback, testing, development reviews, and reported issues to identify and prioritise improvements based on user impact, severity, frequency, legal obligations, technical feasibility, and available resources.

21. Accessibility Testing and Review

Accessibility may be reviewed through a combination of automated testing, manual inspection, keyboard testing, screen-reader checks, responsive testing, code review, design review, content review, and user feedback.

Automated tools can identify certain issues such as missing labels, contrast concerns, structural errors, or invalid markup, but they cannot detect every accessibility barrier.

Manual testing is important for evaluating focus order, keyboard interaction, understandable instructions, screen-reader announcements, modal behaviour, error handling, and practical task completion.

Testing results may differ according to browser, device, operating system, screen reader, magnification software, keyboard configuration, and other assistive technology.

New features may be reviewed before release, while existing features may be assessed during maintenance, redesign, bug fixing, or broader Platform improvements.

High-impact issues that block essential property, account, payment, maintenance, or support tasks may receive higher priority than minor visual or cosmetic issues.

22. Staff Awareness and Development Practices

Accessibility is relevant to product planning, design, software development, content creation, testing, customer support, procurement, and operational decision-making.

We aim to improve awareness among personnel responsible for building, reviewing, supporting, or maintaining the Platform.

Design and development practices may include reusable accessible components, semantic markup, keyboard interaction, descriptive labels, contrast checks, responsive layouts, and accessible error handling.

Content contributors should use meaningful headings, clear language, descriptive links, appropriate alternative text, and accessible documents where practicable.

Support teams may use accessibility reports to identify recurring barriers and communicate important issues to product and engineering teams.

Accessibility knowledge, standards, and technologies continue to evolve, and our internal practices may be updated over time.

23. Third-Party Procurement and Integrations

Accessibility may be considered when evaluating important third-party tools, software, components, templates, plugins, communication services, payment providers, document systems, and other technologies.

Assessment may consider the importance of the service, available accessibility information, known barriers, user impact, contractual flexibility, security, legal obligations, cost, and available alternatives.

Some essential third-party providers may not offer complete accessibility information or an equivalent accessible alternative.

Where a provider creates a material barrier, SkyKente may raise the issue with the provider, seek a workaround, provide an alternative path, replace the component when feasible, or document the known limitation.

Procurement decisions must also consider cybersecurity, privacy, reliability, compliance, technical compatibility, and operational needs.

24. Reporting an Accessibility Issue

Users are encouraged to report accessibility barriers, particularly where an issue prevents access to important property information or completion of an essential task.

A useful report should include the page address, property listing, form, dashboard section, document, or feature where the issue occurred.

Please describe the action you were attempting, what happened, what you expected to happen, and whether the issue completely blocked the task.

Where relevant, include your device, browser, operating system, screen size, zoom level, keyboard method, screen reader, voice-control software, magnification tool, or other assistive technology.

Screenshots, screen recordings, error messages, and step-by-step reproduction details may help us investigate, provided they do not expose passwords, authentication codes, full financial details, or another person's personal information.

If the issue concerns a time-sensitive property application, payment, notice, maintenance issue, or account-security matter, clearly identify the urgency in your report.

We may contact you for clarification or to confirm whether a proposed improvement resolves the issue.

25. How Accessibility Reports Are Handled

Accessibility reports may be reviewed by customer support, product, design, content, quality assurance, engineering, security, legal, or other relevant teams.

We may attempt to reproduce the issue, assess its impact, identify the responsible component, determine whether the issue is controlled by SkyKente or a third party, and evaluate possible alternatives.

Issues may be prioritised based on whether they block an essential task, affect multiple users, create a legal or safety concern, expose personal information, or significantly reduce independent access.

Some issues may be corrected quickly, while others may require redesign, replacement of a third-party component, broader technical work, or inclusion in a future development cycle.

We cannot guarantee that every reported issue will be resolved immediately or that every suggested solution will be implemented.

Where an immediate technical correction is not available, we may attempt to provide a reasonable alternative method for the affected task.

26. Accessibility Complaints

If you believe SkyKente has not responded appropriately to an accessibility barrier or reasonable support request, you may submit a formal complaint using our contact details.

The complaint should include your name, preferred contact method, the affected page or service, the barrier experienced, any previous report reference, and the outcome you are requesting.

We may request additional information needed to investigate the issue, reproduce the barrier, understand the requested adjustment, or confirm your authority to access protected information.

We aim to review accessibility complaints fairly, respectfully, and without discrimination.

Submitting a complaint will not ordinarily affect your right to use the Platform, submit a property enquiry, manage your account, or seek another remedy available under applicable law.

Nothing in this Statement limits any constitutional, statutory, consumer, disability, equality, or other right or remedy that cannot lawfully be limited.

27. Continuous Improvement

SkyKente treats accessibility as part of overall product quality, usability, security, privacy, reliability, and customer experience.

As the Platform grows, we aim to improve component behaviour, page structure, keyboard support, form clarity, document accessibility, mobile responsiveness, colour contrast, focus management, error handling, and support options.

We may review accessibility when introducing new designs, updating layouts, replacing third-party components, changing navigation, creating new public pages, or modifying account-based workflows.

User feedback is particularly valuable because automated tools and internal reviews may not identify every real-world barrier.

Accessibility priorities may be reviewed according to user impact, available resources, technical feasibility, legal developments, Platform risk, and the importance of the affected service.

This Statement may be updated as the Platform, accessibility standards, assistive technologies, legal obligations, and our practices evolve.

28. Changes to This Accessibility Statement

We may update this Accessibility Statement to reflect Platform changes, newly identified limitations, completed improvements, updated standards, user feedback, legal developments, or changes to support procedures.

The last updated date shown at the beginning of this page indicates when the current version became effective.

Material updates may be communicated through the Platform, account notifications, email, or another reasonable method where appropriate.

Users are encouraged to review this Statement periodically, particularly after significant Platform updates.

29. Accessibility Contact Information

Contact SkyKente if you need assistance with an inaccessible task, require information in an alternative format, want to report a barrier, or wish to submit an accessibility complaint.

Please provide enough detail for us to identify the affected page, feature, document, listing, account workflow, or service.

You may also tell us your preferred contact method and the type of assistance or alternative format that would be useful.

Do not include passwords, one-time authentication codes, mobile-money PINs, card PINs, private keys, or complete payment-card details in your accessibility report.

Email: skykente@skykente.com

Phone: +254 715 135 666

Address: Dam Estate, H233 off Langata Road, Nairobi, Kenya.

You may also reach us through the Contact Us page or through the support options available within your account.

Where an accessibility issue concerns a property listing, application, document, or service controlled by a particular agency, landlord, owner, developer, payment provider, or other third party, we may direct the issue to that party or assist you in identifying the appropriate contact.

30. Our Ongoing Responsibility

SkyKente acknowledges that accessible design benefits all users and supports fairer access to property information, services, communication, and digital participation.

We will continue working to identify barriers, improve important workflows, support affected users, and incorporate accessibility into the ongoing development of the Platform.

We welcome constructive feedback from people with disabilities, assistive-technology users, property seekers, tenants, agencies, property owners, service providers, and other members of the SkyKente community.