Accessibility and Official Communications Policy

6membership seeks to provide a reasonably equal opportunity for eligible persons to understand the service, submit an application, receive a decision, manage an approved membership and exercise applicable rights.

Equal participation does not always require every person to use the identical method where an appropriate alternative can achieve the same legitimate purpose.

Accessibility support should respect the individual’s dignity, independence, privacy and preferred method of participation where reasonably possible.

An applicant should not be required to rely on an unrelated person where the service can provide an effective direct alternative.

Known accessibility barriers should be corrected or reduced according to their impact, frequency, technical feasibility and effect on essential service functions.

A temporary workaround may be used while a permanent correction is developed, provided the workaround remains safe and reasonably effective.

New pages, forms, controls, documents and communication templates should be designed with accessibility requirements in mind from the beginning.

Accessibility should be reviewed before a material production release rather than relying solely on complaints after launch.

A person must not receive unjustified adverse treatment because of disability, assistive-technology use, communication needs or a reasonable accessibility request.

A legitimate eligibility or security requirement must be applied according to its actual purpose and not used as a disguised basis for exclusion.

The requested adjustment, the barrier, the affected function, available alternatives, security requirements and operational burden may be considered when selecting an appropriate response.

A refusal should not be based on inconvenience alone where a reasonable effective alternative is available.

The Acceptable Use Policy contains the broader non-discrimination standard.

The Privacy Notice governs personal information supplied with an accessibility request.

The Electronic Communications Consent governs electronic notices and records.

Accessibility considerations apply to public membership descriptions, pricing information, tier comparisons, legal policies, contact information and public verification pages.

Public information should not depend exclusively on visual decoration, animation, hover behaviour or colour interpretation.

Accessibility considerations apply to tier selection, eligibility checks, form completion, document upload, guardian participation, policy acceptance, payment handoff and final submission.

An applicant should be able to identify required fields, validation errors and the current stage of the application.

Accessibility considerations apply to membership status, cards, certificates, renewal information, correction requests and administrative support.

6membership is responsible for making its own payment explanations, amount, currency, tax treatment, refund wording and transaction status reasonably understandable.

Where payment-dependent value or application progression depends on Flutterwave, the authoritative 6membership status must be based on server-side verification of the expected transaction status, amount, currency, transaction reference and relevant payer or application relationship rather than a browser redirect, screenshot, debit alert or applicant statement.

Flutterwave controls the accessibility of its hosted payment interface, but 6membership should report a material provider barrier and consider an appropriate lawful alternative where available.

Accessibility considerations apply to application emails, incomplete requests, decisions, payment notices, refund updates, policy notices, security warnings, privacy responses and complaint outcomes.

Where 6membership publishes or issues a document, reasonable effort should be made to ensure that the information is available through accessible text, structured content or another suitable format.

An image-only document should not be the sole source of essential instructions where an accessible textual alternative can be provided.

Accessibility barriers arising within a provider service should be documented and raised with that provider where material.

6membership cannot represent that it controls every provider interface, but provider dependence does not remove the need to assist affected users reasonably.

6membership uses the current production-adopted Web Content Accessibility Guidelines version as an important design, development and testing reference.

The intended baseline for material public and application functions is WCAG 2.2 Level AA where reasonably applicable to the technology and content.

A target or development intention is not the same as verified conformance.

6membership must not claim that the complete service conforms to WCAG 2.2 Level AA until the relevant production scope has been tested sufficiently and unresolved exceptions are disclosed appropriately.

Accessibility techniques and standards may change as browsers, assistive technologies, devices and recognised guidance develop.

A technical update should be assessed before changing the published conformance position.

Automated accessibility tools may identify missing labels, contrast issues, structural defects and other common barriers.

Automated testing cannot establish complete accessibility by itself and should be combined with appropriate manual review.

Material user journeys should be tested through keyboard interaction, focus review, text enlargement, responsive layouts and representative assistive-technology checks.

Testing should concentrate on completing the real journey rather than checking isolated pages only.

Reports from people encountering real barriers are an important source of accessibility evidence.

A reported barrier should be reproducible and assessed rather than dismissed solely because an automated tool did not detect it.

A known material accessibility exception should be documented with its effect, available alternative, remediation priority and expected review position.

An exception must not remain hidden indefinitely where it prevents an essential application or membership action.

6membership will assess the service against applicable requirements arising under Nigeria’s Discrimination against Persons with Disabilities (Prohibition) Act 2018, the Persons with Disabilities (Accessibility) Regulations 2023 and other binding accessibility rules relevant to the service.

WCAG 2.2 Level AA is used as a technical production target and testing reference; this does not mean that every WCAG success criterion is represented as a direct statutory obligation under Nigerian law.

Where a binding rule requires a different or stronger accessibility measure, the binding requirement controls.

Meaningful images, icons and non-text controls should have an appropriate textual name or alternative where their purpose is not already clear from surrounding text.

Purely decorative images should not create unnecessary screen-reader output.

Colour must not be the only method used to communicate required fields, errors, selection, payment status, membership status or another essential meaning.

Text, icons, patterns or programmatic information should provide the same meaning.

Text, interactive controls, focus indicators and essential graphical information should use sufficient contrast against their background.

The premium monochrome visual system must not reduce readability by placing low-contrast grey text on similar grey surfaces.

Material content and controls should remain usable when text is enlarged and when the viewport is narrowed.

Users should not be required to scroll in two directions for ordinary text where responsive reflow can prevent it.

Prerecorded essential video should include captions or an equivalent textual alternative where speech or meaningful audio communicates required information.

Essential audio-only material should have an appropriate transcript or equivalent explanation.

The service should avoid content that flashes in a manner likely to create an avoidable seizure risk.

A decorative animation must not be necessary to understand or complete an application.

Important legal, payment and application information should be available as selectable or assistive-technology-readable text where reasonably possible.

A photograph or scan of text should not be the only version of essential 6membership instructions.

Material website and application functions should be operable through a keyboard without requiring a pointer-only action.

A user must not become trapped inside a modal, menu, form control or interactive region.

Keyboard focus should be visibly identifiable on links, buttons, form fields and other interactive controls.

Focus must not be hidden behind a sticky header, modal layer or decorative effect.

The keyboard and assistive-technology reading order should follow a logical sequence consistent with the visual and functional structure.

A user should not be moved unpredictably between unrelated sections.

Buttons, links, selectors and other touch controls should be large enough and separated sufficiently to reduce accidental activation.

A small decorative icon must not become the only way to perform an essential action.

Where a function uses a dragging movement, another single-pointer or keyboard method should be available where reasonably applicable.

Essential application information must not depend exclusively on drag-and-drop.

Decorative transitions, parallax effects and animated reveals should respect reduced-motion preferences where technically supported.

Disabling non-essential motion must not hide content or prevent completion of the journey.

A time-limited session or secure action should provide an appropriate warning and renewal opportunity where security permits.

Where a strict expiry is necessary for security, the user should receive clear instructions for requesting a new secure link or restarting the action.

Essential application, payment, refund and status information should use direct and reasonably understandable language.

Legal accuracy may require defined terminology, but the surrounding explanation should clarify the practical effect where possible.

Form controls should have clear visible labels and programmatic names.

Instructions should explain required formats, document types and material eligibility conditions before submission where practical.

A validation error should identify the affected field and explain what must be corrected.

An error must not be communicated only through colour, an unexplained icon or a generic statement that something went wrong.

Before a high-impact submission, the user should have an appropriate opportunity to review or confirm important information.

High-impact actions include final application submission, payment initiation, guardian approval, withdrawal and certain privacy or membership requests.

Repeated navigation, help and status controls should remain reasonably consistent across related pages.

The same label should not perform materially different actions without adequate explanation.

Information already supplied during the same application journey should not be requested repeatedly without a legitimate verification, correction or security reason.

Where repetition is required, the reason should be apparent or explained.

Authentication should avoid unnecessary cognitive barriers and should support password managers, copy-and-paste and appropriate alternative verification where secure and technically supported.

An accessibility alternative must not create an unauthorised bypass of identity or account security.

Pages should use appropriate headings, landmarks, lists, labels, tables and native controls so that structure can be interpreted programmatically.

A visual arrangement alone must not be the only source of document hierarchy.

Custom components should expose an appropriate accessible name, role, value and state.

A screen reader should be able to determine whether a control is selected, expanded, disabled, invalid or processing where that state is material.

Important asynchronous results such as upload completion, validation failure, payment verification and successful submission should be available to assistive technologies without requiring an unexpected focus change.

The website should remain usable across supported desktop and mobile viewports without hiding essential controls or instructions.

Orientation should not be restricted unless a particular function genuinely requires it.

Accessibility testing should use reasonably current supported browsers and representative assistive technologies.

6membership cannot guarantee identical behaviour in obsolete or materially unsupported software.

Essential information should remain available where a non-essential visual effect or enhancement fails.

A failure of animation, decorative imagery or analytics must not prevent access to the underlying legal or application content.

Embedded content and provider interfaces should be labelled and introduced clearly so the user understands that they are entering another service.

A material third-party accessibility defect should be documented and an alternative considered where available.

A person may request an accessibility adjustment by contacting the relevant official 6membership address.

The request should describe the barrier and the assistance or alternative that would help.

An ordinary communication adjustment should not require disclosure of a complete diagnosis, medical history or unrelated health records.

6membership may request limited supporting information where the requested adjustment is substantial, unclear or connected with a binding eligibility or identity issue.

6membership may discuss the barrier, requested outcome, available technology, security implications and suitable alternatives with the requester.

The service may offer a different adjustment where it addresses the barrier effectively and more safely or practically.

Depending on the circumstances, an adjustment may include clearer written instructions, an accessible text version, additional completion time, an alternative document format, assisted navigation or a different secure communication method.

The available adjustment depends on the affected function and production capability.

An adjustment must not require an applicant to disclose passwords, PINs, OTPs or complete payment credentials to an administrator.

Identity, guardian and payment requirements may be completed through a suitable alternative, but they must not be bypassed without lawful authority.

6membership should acknowledge and assess an accessibility request within a reasonable period considering the urgency of the associated application or notice.

Where the exact request cannot be provided, the response should explain the position and identify an available alternative where reasonably possible.

A requester’s preferred adjustment will be considered but may not be available where it would create a material security risk, remove an essential requirement, disclose another person’s information or impose a disproportionate technical burden.

The service should still consider another effective method rather than ending the process automatically.

The selected tier’s price, eligibility, predecessor requirement, duration options and principal limitations should be presented in a readable form before payment.

Essential tier information must not exist only inside decorative comparison graphics.

An applicant may use assistive technology or receive appropriate help from an authorised person when completing the application.

The applicant remains responsible for confirming the accuracy of information submitted in their name where they have legal capacity to do so.

A representative may assist with navigation, communication or document preparation where authorised.

Assistance does not automatically authorise the representative to accept terms, provide guardian consent, receive private records or redirect a refund.

Where an ordinary upload control creates a verified accessibility barrier, 6membership may provide another secure upload route supported by production systems.

Sensitive documents should not be sent through an insecure personal communication channel merely because the ordinary upload failed.

Reasonable additional time may be provided for an incomplete-information response or accessibility-related completion difficulty where the application remains capable of review.

A binding payment, secure-link, regulatory or security deadline may require a newly generated process rather than an indefinite extension.

An accessibility request must not be treated as evidence that the person lacks capacity, authenticity or eligibility.

A concern about legal capacity must be supported by the actual age, guardian or legal requirements rather than assumptions based on disability.

Providing an adjustment does not guarantee application approval.

The application remains subject to the same legitimate eligibility, verification, payment, compliance and conduct framework.

Information presented to an eligible younger applicant should be reasonably understandable for their age and role in the process.

The younger person should be told what information is requested, why guardian involvement is required and what the application means.

The younger applicant’s participation and the guardian’s legal approval should remain distinguishable.

An accessibility adjustment must not allow one person to impersonate the other or complete both actions secretly.

A disability does not automatically mean that a person lacks legal capacity or cannot understand the membership process.

Support should be tailored to the individual rather than based on a general assumption.

Where appropriate, information may be explained through a trusted supporter while preserving the younger person’s own views, privacy and safety.

The supporter must not coerce approval, payment or disclosure.

Where a guardian or representative is alleged to be exploiting, coercing or impersonating the younger person, 6membership may restrict the relevant process and assess appropriate protective action.

Guardian notices should identify the younger applicant, requested action, relevant policy version, secure expiry and consequences of approval or refusal.

The notice must not require the guardian to send passwords, payment PINs or OTPs to an administrator.

Eligibility, minimum age, guardian authority, assent and transition to adult control are governed by the Eligibility, Age and Guardian Consent Policy.

Official public website communications are provided through 6membership.com, www.6membership.com and any approved subdomain expressly identified by 6membership under its registered parent company, 6Clement Joshua.

A similar-looking domain, shortened link or copied page must not be assumed to be authentic.

Official email communications may use authorised addresses associated with the 6membership domain and may be transmitted through the configured transactional-email provider, currently Resend.

Current functional addresses include applications@6membership.com and admin@6membership.com, with specialist legal, privacy and security addresses used where configured and operational.

An email display name such as 6membership Applications can be copied by another sender.

Recipients should review the actual sending domain, requested action and destination before responding.

A social-media account may publish general information but should not be used as the sole route for sending private identity documents, payment credentials, legal process or sensitive application evidence.

An applicant should confirm that an account is official before relying on a private message.

6membership administrators must not ask a person to send a password, banking PIN, card security code or OTP through email, telephone, social media or messaging.

An OTP should be entered only through the authorised interface associated with the action.

An official payment communication must direct the payer through the authorised 6membership and Flutterwave process.

An administrator’s personal bank account, wallet or unofficial link is not an authorised membership-payment destination.

A person who receives an unexpected approval, payment, refund, identity or security message should verify it through the official website or published 6membership contact address.

The person should avoid replying with sensitive information until authenticity has been checked.

Application communications may include email verification, draft reminders, submission confirmation, incomplete requests, review notices, decisions and appeal information.

Payment communications may include checkout instructions, verified payment status, reconciliation requests, duplicate-payment notices and receipts.

A communication must distinguish internal status from the independent Flutterwave transaction record and must not describe payment as successful merely because checkout redirected, a screenshot was supplied, a debit alert appeared or an unauthenticated event was received.

Material Flutterwave webhook events should be authenticated and processed idempotently so retries or duplicate events do not create duplicate application progression, value or administrative actions.

Refund communications may include internal eligibility approval, submission to Flutterwave, provider processing and final succeeded or failed status, together with any reversal or corrective event that genuinely applies.

The wording must distinguish internal approval from submission to Flutterwave and must not state that a refund has been completed until the provider record supports the final completed status.

Membership communications may include approval, activation, card or certificate availability, status changes, expiry, renewal, suspension, restoration, cancellation and revocation.

Security communications may include unusual access, exposed credentials, phishing warnings, restricted access, secure-link replacement and incident information.

A security message should not expose additional sensitive information unnecessarily.

Legal and privacy communications may include policy changes, consent records, privacy-request acknowledgements, complaint outcomes and authority-request notices where lawful.

Optional promotional messages should remain distinguishable from necessary application, payment, security, membership and legal notices.

Withdrawing from optional marketing does not prevent necessary service communications supported by another lawful basis.

Email is a principal communication channel for application, payment, membership and policy notices.

Email content should use meaningful headings, readable structure, descriptive links and clear action wording.

Where a secure website or account status is available, it may provide the authoritative current application or membership record.

An email summary should not contradict the controlled server-side status.

A person may request a plain-text explanation where a formatted email or document cannot be used effectively with their technology.

The alternative must preserve essential legal, payment and status meaning.

Digital information should support ordinary browser and device text enlargement where technically possible.

Where a fixed document cannot be enlarged effectively, an accessible text alternative may be provided.

A request for audio, sign-language, Braille or another specialised format will be assessed according to the information, urgency, available providers, security and reasonable feasibility.

6membership must not claim that every specialised format is immediately available where it has not established that capability.

The principal contractual and legal language of the service is English unless another production language is expressly offered.

A clear explanation or translation assistance may be considered where reasonably available, while mandatory local-language rights remain preserved where applicable.

A machine or informal translation may assist understanding but can contain errors.

Where legal meaning is material, the person should be told which language version controls unless applicable law provides otherwise.

6membership may record internal generation and submission together with available Resend events such as sent, delivered, delivery delayed, bounced, failed, suppressed or complained about.

A Resend sent or delivered event concerns transmission to the provider or recipient mail server and does not by itself prove that the intended person personally opened, read, understood or acted on the message. Open or click telemetry, where enabled and lawfully used, must also not be treated as infallible proof of comprehension or legal notice receipt.

Applicants and members are responsible for providing and maintaining a reliable email address and other required contact information.

A person should report loss of access to the registered email promptly.

An official message may be delayed or moved by the recipient’s email provider, device or filtering settings.

Recipients should check relevant filtered folders when expecting a time-sensitive communication.

Where a message bounces or is rejected, 6membership may retry, use another authorised channel or mark the communication as undeliverable.

Repeated failed delivery may affect the ability to continue a time-sensitive application process.

A request to change a registered email address may require identity verification before private records or secure links are redirected.

6membership must not transfer an application or membership to a new address based solely on an unauthenticated message.

A deadline should identify the required action, date and consequence of no response.

Where an accessibility barrier prevented a timely response, the person may request reasonable reconsideration or an appropriate extension.

A delivery failure does not automatically approve an application, grant a refund or restore a membership.

The underlying record and available complaint or correction route still control.

Material application, payment, refund and membership messages should use centrally controlled templates that correspond with the authoritative production status.

The controlled workflow may include Approve, Decline, Flag incomplete, Request more information, Place under review, Confirm payment, Start eligible refund, Suspend and Restore where the action is available for the relevant record.

Required legal, payment and complaint wording must not be removed through an administrator’s custom message, and a custom observation must not create a payment, refund, approval or membership status that the backend has not recorded.

An authorised administrator may add a relevant custom observation alongside the standard message.

The observation should use clear, respectful language and identify the specific missing information, concern or next action where appropriate.

An administrator must not include insults, stereotypes, assumptions about capacity or unrelated comments about disability or communication needs.

Accessibility information should be included only where relevant to providing the adjustment or documenting the request.

An administrator must not direct an applicant to make a private payment, send an OTP, reveal a password or bypass the official application process.

A communication should describe the actual status in understandable terms and avoid internal codes that the recipient cannot interpret.

Where a code is included for reference, the practical meaning should also be stated.

An approved adjustment should be documented sufficiently for authorised staff to apply it consistently.

The record should avoid unnecessary health or disability details.

Material communications should record the template or category, recipient, related application or membership, authorised actor, reason where required, custom observation, previous and resulting status where applicable, time and delivery result. Repeated administrative requests or provider events should be handled so that duplicate execution does not create duplicate value or contradictory notices.

Information supplied with an accessibility request should be used to understand the barrier, assess the request, provide the adjustment and maintain necessary accountability records.

It must not be reused for unrelated marketing or curiosity.

6membership should request the minimum information needed to assess and provide the adjustment.

A person should usually be able to describe the functional barrier without supplying a complete medical record.

Health, disability and related information may be sensitive personal information and requires appropriate lawful, confidential and secure handling.

Accessibility-request information should be accessible only to authorised persons who need it for support, review, complaints, security or legal obligations.

An administrator should not receive detailed health information where only a preferred communication format is required.

A representative may receive information only within the verified scope of their authority.

Assisting with accessibility does not automatically authorise access to every application, payment or membership record.

Accessibility-request records should be retained only while necessary to provide continuing support, demonstrate the response, resolve a complaint or meet another lawful purpose.

Where Nigerian storage-limitation rules apply and the original purpose has been accomplished without another time-bound legal obligation or properly documented continuing basis, post-purpose retention must follow the limits and safeguards stated in the Data Retention, Deletion and Records Policy.

Unnecessary supporting medical material should be deleted, reduced or irreversibly de-identified sooner where appropriate.

Applicable access, correction, deletion, restriction, objection and complaint rights may apply to accessibility-related personal information.

6membership cannot guarantee that every page, device, browser, assistive technology, third-party service and document will operate without any accessibility barrier.

The service remains responsible for responding reasonably to known material barriers within its control.

A website, database, email, network or payment outage may temporarily interrupt an accessible journey or communication channel.

6membership should provide an appropriate status or alternative where practical and avoid misleading users about completion.

A provider may control an interface or technical feature that 6membership cannot modify directly.

6membership should document the issue, report it where material and identify a lawful alternative where reasonably available.

An accessibility method may be limited where it would expose private records, weaken authentication, permit impersonation or create a material security risk.

A safer alternative should be considered rather than refusing support without assessment.

An adjustment cannot require 6membership to disregard a binding law, court order, sanctions restriction, age requirement or lawful recordkeeping duty.

An adjustment need not remove an essential function of the membership process, such as confirming identity, guardian authority, payment or policy acceptance.

The essential function should be completed through an accessible alternative where one can preserve its integrity.

A temporary accessible alternative may remain available while a technical defect is corrected.

The temporary method should not require less privacy or security than reasonably necessary.

An accessibility report should identify the page or communication, action attempted, barrier encountered, device or assistive technology where relevant and the result expected.

The reporter should not include passwords, OTPs or unrelated identity information.

6membership should acknowledge a material accessibility report within a reasonable period and may request clarification needed to reproduce the issue.

Priority should reflect whether the barrier blocks payment, final submission, guardian approval, identity verification, a legal right, a security action or access to essential membership information.

A cosmetic issue may receive a different priority from a complete application blocker.

The reported barrier should be tested in the relevant production or safe test environment using the information supplied.

A failure to reproduce the issue immediately does not establish that the report is invalid.

Where immediate remediation is not possible, 6membership should consider a safe interim method that allows the person to complete the essential action.

A correction should be tested against the original barrier and checked for material regressions in related user journeys.

Closing the report should not rely solely on the fact that code was changed.

A person must not receive adverse treatment merely for reporting a genuine accessibility defect or requesting support.

Knowingly abusive or fraudulent conduct remains subject to the ordinary conduct rules.

A person may complain about an inaccessible page, ineffective alternative, refused adjustment, excessive information request, discriminatory treatment or unclear official communication.

The complaint should identify the barrier, request made, response received, practical effect and requested resolution.

Relevant screenshots or recordings may be included where they do not expose unnecessary private information.

The review should consider the barrier, requested adjustment, alternatives offered, essential requirements, privacy, security and proportionality.

Where practical, a material refusal should be reviewed by a person who did not make the original decision.

The complaint may result in a corrected page, alternative format, additional time, revised communication, approved adjustment, different adjustment, explanation or confirmation of the original decision.

An accessibility complaint does not automatically approve the underlying membership application.

Where the barrier affected fairness or completion, the application may be reopened, extended or returned for appropriate review.

Nothing in this Policy removes a mandatory right to contact the National Commission for Persons with Disabilities, a consumer authority, the Nigeria Data Protection Commission, a court or another competent body where that right applies.

The intake, review, appeal, remedy and dispute-resolution framework is governed further by the Complaints, Appeals and Dispute Resolution Policy.

General accessibility requests and reports may be sent to admin@6membership.com.

The request should identify the relevant page, communication, application or membership without including unnecessary sensitive information.

Accessibility support relating to an active application, incomplete request, guardian action or application decision may be sent to applications@6membership.com.

Concerns about disability information, health information, confidentiality, access, correction, deletion or disclosure may be sent to privacy@6membership.com.

A barrier involving authentication, secure links, exposed information, phishing or unauthorised access may be reported to security@6membership.com.

Records may include the requester, barrier, requested adjustment, assessment, response, approved alternative, implementation, complaint and remediation result.

The record should contain no more disability or health information than necessary.

Accessibility records may be retained while an adjustment remains active and afterward only for the period justified to demonstrate the response, resolve complaints, satisfy a time-bound legal obligation or maintain another documented lawful accountability purpose.

Where Nigerian storage-limitation rules apply after the original purpose is accomplished, retention must follow the post-purpose limits and safeguards in the Data Retention, Deletion and Records Policy rather than continuing indefinitely because the record may be useful.

Temporary supporting information should be deleted, reduced or irreversibly de-identified when no longer needed.

This Policy and the actual production service should be reviewed after material redesigns, new application journeys, provider changes, recurring reports and relevant legal or technical developments.

The review should distinguish completed production controls from future intentions.

This Policy may be updated to reflect new accessibility standards, communication channels, service providers, assistive-technology findings, legal requirements and remediation procedures.

A material change will be handled through the central policy-update framework.