Last updated: October 22, 2026
Luxury-Rehabs.com aims to make its rehab directory and educational articles usable by people with different access needs. Accessibility includes readable text, meaningful headings and links, keyboard access, clear focus indicators and alternatives for informative images.
This statement describes that aim and provides a practical way to explain a barrier. People may use the website with a keyboard, touch input, magnification, a screen reader, voice input, or another method. The useful question is whether the information and controls let a person complete the task they came to do. A page that appears readable in one setting may still be difficult to use in another.
Current approach
Accessibility is an ongoing part of improving the website. This statement is not a certification that every page meets an accessibility standard. Third-party content, older articles and complex interactive features may present barriers.
The W3C guidance on accessibility statements distinguishes a useful statement for visitors from a technical assessment or declaration of conformance. In that spirit, this page explains the contact route and the kinds of information that can help describe a problem. It does not claim a completed audit of every page, compatibility with every assistive technology, or a particular conformance level.
An isolated check or improvement cannot establish that every task works for every visitor. Reading an article, navigating a long provider profile, selecting a filter, and following an external contact link involve different interactions. If one works and another does not, the distinction is useful to include in a report. It helps identify the part of the experience that needs attention without treating the entire website as one undifferentiated problem.
Finding and reading directory information
A common task is moving from a broad directory category to a particular provider. If the difficulty occurs while selecting a category, opening a result, or moving between pages, describe the step that prevents you from continuing. Include the category or provider name if you can. A report such as being unable to open a filter with a keyboard is more specific than saying that a page is difficult to navigate.
Another common task is finding a provider’s location, service description, or contact details within a longer page. If the heading structure, link wording, or order of information makes that task difficult, identify what you were trying to find. You do not need to diagnose the technical cause. Describing where you expected the information and what you encountered instead can make the practical impact clear.
Directory labels also have limits unrelated to technical access. An accessibility-related feature recorded for a provider does not establish that its building, program, or admissions process will meet a person’s needs. Use the listing to identify questions and then ask the provider about the actual location and service. This website’s accessibility statement concerns access to the directory itself, rather than access to every facility it lists.
Text size, layout, and reading preferences
The W3C guide to changing text size and colors explains browser zoom, text settings, and reader views. These browser features may help some people read web content in a preferred format. Their availability and behavior depend on the browser and page. Using them should not be treated as proof that a page is accessible, and a problem that remains is still relevant to report.
If text becomes clipped, overlaps another element, or requires difficult scrolling after enlargement, describe that behavior and the approximate zoom level if known. If a fixed element covers content or a control, identify what is obscured. You do not need to send a full-screen image containing unrelated tabs or personal information. A short description of the visible problem can be enough to explain the issue.
Some people find long sentences, dense layouts, unexplained abbreviations, or unclear instructions difficult to follow. Accessibility feedback can concern those aspects too. Identify the passage or task and explain what would make it clearer, such as a more direct instruction or a distinction between similar program terms. A request for clearer wording is useful even when the text is technically visible and the page opens successfully.
Keyboard, focus, and other ways of interacting
The W3C accessibility principles describe the importance of information people can perceive, controls they can operate, understandable content, and compatibility with different ways of using the web. These are broad principles for evaluating an experience. A visitor does not need to know the name of a technical requirement to report that a button cannot be reached, a menu cannot be closed, or a link’s purpose is unclear.
For a keyboard-related issue, useful details include the control you were trying to reach and what happened when you moved through the page. For example, focus may become difficult to see, move in an unexpected order, or appear to remain inside one component. Describe the last successful step and the point at which progress stopped. Include the key or action used if that information is easy to provide.
For touch or voice-input difficulties, describe the control and the intended action. A target may be hard to select, two controls may be difficult to distinguish, or a spoken label may not match what appears on screen. These examples explain the kind of detail that can help with a report; they are not a claim that a particular problem occurs on every page or that all input methods have been tested.
Screen readers, images, and meaningful links
If you use a screen reader, a report can describe what was announced and what information or action was missing. For example, several links may sound identical even though they lead to different destinations, or a control may be announced without a useful name. The page address and the nearby heading or provider name can help identify the element. A technical recording is optional; a plain explanation is welcome.
Images can also affect access when they contain meaningful information without a useful text alternative. Identify the image or its position and explain what you need to understand from it. A provider photograph, logo, diagram, and image containing written instructions serve different purposes. If essential text appears only inside an image and is difficult to read, describe the missing information rather than assuming that enlarging the picture will resolve the problem.
Third-party content and external destinations
Some information or media may be supplied through an external service, and provider contact links can lead away from this website. If a problem begins after following a link, include the destination address when available. That distinction helps separate a directory navigation problem from a barrier on another organization’s website. External content can have its own design, controls, privacy practices, and accessibility information.
If embedded media or another external component is the barrier, identify the page and what information you were trying to obtain. A request might concern readable text, a description of the relevant information, or an explanation of a control. State the alternative that would be useful. This identifies the need without assuming that a particular format already exists or that the directory controls the external service’s interface.
Report a barrier or request an alternative
Email info@luxuryrehabs.com with the page URL, the task you were trying to complete and a description of the problem. If useful, include your browser or assistive technology. You do not need to disclose a diagnosis. Tell us what alternative format or assistance would help.
A concise report can explain three things in ordinary language: where you were, what you wanted to do, and what prevented it. You can also say whether the issue affected one page or several and whether it appeared consistently. These details are helpful when known, but the absence of technical information should not stop you from explaining the barrier and its impact on your task.
Include only information relevant to the website issue. Medical records, identity documents, a full treatment history, and passwords are not needed to describe a navigation or reading problem. If you attach a screenshot, remove unrelated personal details where possible. The privacy policy explains correspondence and the route for questions about personal information sent to the website.
An alternative-format request can identify the particular information needed and the form that would help you use it. For example, you might need the text of a description, clearer wording for an instruction, or help identifying a contact link. A specific request makes the desired result easier to understand than a general request to make an entire website accessible. It does not require you to explain a medical condition.
Separate website support from treatment access
For information about a provider’s facilities or admission accessibility, contact that provider directly. For urgent medical help, use local emergency services rather than this website.
When contacting a provider, explain the relevant practical needs and confirm the actual program and address. Questions may concern step-free routes, room arrangements, communication support, dietary needs, or assistance during appointments. A general accommodation label or a photograph cannot establish how those needs will be met. The provider’s team should explain its current arrangements and any limits before travel or admission is planned.
If a directory barrier prevents you from identifying a provider’s published details, describe that access problem through the website contact route. The purpose of that report is to make the information or task understandable, not to request clinical assessment from the directory. Keeping the two needs distinct helps you ask the relevant organization for the information it is responsible for providing.