Does this website work with a screen reader?

It is built to. The pages use ordinary headings, lists, links, and landmarks, so a screen reader can announce the structure and you can jump from heading to heading instead of listening to a whole page. Form fields are labeled, and errors in the form are announced rather than only shown in red. We cannot promise perfection on every page, and we do not claim to have tested every screen reader. If something reads wrong or reads as nothing at all, please call us at (323) 675-2991 and tell us which page, because that is exactly the kind of report that gets a fix made.

What should I do if a page is hard to use or I cannot finish something?

Call us at (323) 675-2991. You do not have to fight with the website. An advisor can take the same information over the phone and carry on from there, and telling us what went wrong helps us fix it for the next person. If you would rather write, use our contact page and say which page you were on and what you were using, for example a screen reader, a phone, or a keyboard on its own.

Can I get help by phone instead of using the website?

Yes, completely. Nothing on this site is a required step. The whole service, from the first conversation through the tours and the move itself, works by phone, and for many families that is the faster route anyway. The website exists to answer questions at two in the morning, not to stand between you and a person.

Is this site certified as accessible or fully compliant?

No, and be careful with any site that says it is. There is no official certification for website accessibility in the United States, and this site has not been audited by an outside organization. What we can tell you honestly is the standard we work to, WCAG 2.1 Level AA, that we consider the site partially conformant with it, and what we know is still imperfect. That is on this page, in the known limitations section.

The text is too small for me. Can I make it bigger?

Yes. Hold Ctrl and press the plus key to zoom in, or Command and plus on a Mac, and Ctrl or Command with zero to go back to normal. On a phone or tablet, pinch outward with two fingers. We have not disabled pinch zoom, which some sites do. Windows, macOS, iPhone, and Android also have a display setting that enlarges text in every app at once, which is usually more comfortable than adjusting one site at a time.

Do you use an accessibility overlay or accessibility widget?

No, deliberately. Overlays are the little toolbars that promise instant compliance from a single line of script. They do not deliver it, they often interfere with the screen reader or magnifier a person already has set up the way they like it, and their presence has not kept sites out of court. We would rather spend the same effort fixing the underlying pages, which is what this statement describes.

Accessibility Statement

Our commitment

We want this website to be usable by everyone who needs it, including people who use a screen reader, enlarge the text, magnify the screen, or move through a page with a keyboard rather than a mouse.

We aim to conform to the Web Content Accessibility Guidelines, version 2.1, at Level AA. That is the standard most often referenced in United States accessibility law and in public sector accessibility rules elsewhere, and it is what we hold our own work against.

This matters more here than it would on an ordinary website. Our visitors are older adults and their adult children. Eyesight, hearing, and steadiness of hand change with age, and many people arrive on this site during a hospital discharge or a bad week at home, on a phone, under real stress. Every one of those things makes a page harder to use. So we treat accessibility as the main job rather than a box to tick, because for this audience an unreadable page is not an inconvenience, it is a family that does not get help.

What we have done

These are the specific measures in place on this site today. We have listed only what is genuinely done.

Semantic HTML throughout: a single main heading on each page, section headings beneath it, real lists and real links, and proper navigation, main, and footer landmarks, so assistive technology can describe the page and move around it.
A skip to main content link as the first thing on every page, so a keyboard or screen reader user can jump straight past the menus to the part they came for. It is a plain link, so it works whether or not JavaScript is running.
A clear focus outline on every link, button, and field, so if you are moving through the page with the Tab key you can always see where you are. It is drawn thick and set slightly away from the control so it stays visible to someone with reduced contrast sensitivity.
Buttons and menu controls given a touch area of at least 44 by 44 pixels. That is the stricter AAA target size rather than the AA minimum, and we took it on purpose: a hand with a tremor or with arthritis should not have to land on a small target. Where a control looks smaller than that, its touchable area is quietly larger.
Text alternatives on images that carry meaning, and images that are purely decorative marked so that a screen reader passes over them instead of reading out a filename.
Form fields with labels properly attached to them, so the label is announced when you reach the field and tapping the label puts your cursor in it. Sets of choices, such as the type of care, are grouped and introduced by name rather than arriving as a row of unexplained buttons.
Errors and progress in the form announced out loud rather than only shown in color, so a screen reader user hears what went wrong, which field it belongs to, and when a step has been saved.
Color contrast measured across the whole palette and corrected where it fell short. Body text now clears the 7:1 ratio, which is the stricter AAA threshold rather than the 4.5:1 that AA asks for. We went the extra step deliberately, because reduced contrast sensitivity is one of the most common changes in an older eye. The colors themselves are unchanged in hue, only in lightness, so the site still looks like itself.
Text that enlarges to 200 percent without losing content or spilling off the side of the screen. Sizes are set in relative units, so the page follows the text size you have chosen in your browser or in your device settings, and we have not disabled pinch zoom on phones the way some sites do.
Written content delivered by the server, so every page can be read with JavaScript turned off, on an older browser, or on a slow connection in a hospital corridor.
Plain language, short paragraphs, and descriptive headings, which help everyone and matter a great deal to a reader who is tired, worried, or using speech output.
Reduced motion respected. If your computer or phone is set to reduce motion, because movement on a screen makes you dizzy or makes text hard to follow, this site drops its animations and transitions to match. There is nothing here that flashes, and nothing that moves on its own.
No video or audio anywhere on the site, so there is no media here that needs captions or a transcript, and nothing that starts playing at you.
No accessibility overlay and no third party accessibility script. We fix the pages themselves instead, for the reasons set out in the questions at the end.

Conformance status

The Web Content Accessibility Guidelines set out requirements for making web content more accessible to people with disabilities. They define three levels of conformance: A, AA, and AAA.

This website is partially conformant with WCAG 2.1 Level AA, which means that some parts of the content may not yet fully conform to the standard.

We say partially and we mean it. This assessment comes from our own review of the site rather than from a third party audit, and we hold no accessibility certification, because there is no official certification for website accessibility in the United States. Accessibility work on a site that is still being written is never finished either. So we would rather show you the standard we work to, and an honest list of what is not right yet, than claim something we cannot stand behind.

Known limitations

These are the parts we know are not there yet. If you hit one of them, the phone number below gets you a person, and that route works regardless.

The step by step inquiry form needs JavaScript to work. The written content of every page can be read without it, but that form cannot be completed with JavaScript switched off. If it is off, the form says so where it stands and gives you the phone number, and an advisor will take the same details by phone.
The drop down menus in the header also need JavaScript to open. With it switched off, the links in the footer at the bottom of every page still reach our services, guides, and area pages.
Content published by other organizations is outside our control. When we link to a senior living community, a state agency, or a benefits form, that page belongs to them, and we cannot guarantee it meets the same standard. Tell us if one of our links sends you somewhere unusable and we will find you the information another way.
Our guide pages are long, because the detail is the part families actually need. We break them up with clear headings so you can move through them by heading, but a long page is still a long page.
We publish new pages regularly. A page added recently may not have had the same checking as an older one, and problems can be reintroduced by an ordinary content update. This is a standing risk on any site that is still being written.
We cannot test every combination of browser, operating system, and assistive technology. If your particular setup runs into trouble here, that is worth a call to us, not an evening of your time.

How to get help or report a problem

If any part of this site is hard to use, or something is stopping you from getting the information you need, please tell us. We would far rather hear about it than have you give up and go without help.

Call us at (323) 675-2991. That is the fastest route. If we cannot pick up, leave a message with a number to call back and we will. You can also use the contact page or write to us at 108 S Las Palmas Ave, Los Angeles, CA 90004.

If you are reporting a problem, it helps us enormously to know which page you were on, what you were trying to do, and what you were using, for example a screen reader, a phone, a magnifier, or a keyboard on its own. Even a rough description is enough. We can usually work out the rest.

We read every report and we aim to respond promptly. Two promises go with that. First, we will tell you honestly whether we can fix the thing you found and what we are doing about it. Second, and more important on the day, we will help you get what you came for by phone in the meantime. Nobody should lose access to this service because of a defect on our website, and our placement help is free either way.

Ways to make this site easier to use

A few settings that already exist on your own device will do more for you than anything a website can add, and they work everywhere, not just here.

Make this page bigger. Hold Ctrl and press the plus key, or Command and plus on a Mac. Ctrl or Command with the zero key puts it back. On a phone or tablet, pinch outward with two fingers.
Make everything bigger, once. Windows, macOS, iPhone, and Android each have a display or accessibility setting that enlarges text across every app at the same time. It is usually far more comfortable than zooming one site at a time, and this site follows that setting.
Have the page read to you. A screen reader is already built into your device: VoiceOver on iPhone and Mac, TalkBack on Android, Narrator on Windows. Our pages use ordinary headings and lists, so you can move heading by heading instead of listening from the top.
Or skip the website entirely. Call (323) 675-2991 and talk to an advisor. Everything here can be handled in conversation, usually faster, and it costs your family nothing.

When this statement was last reviewed

This statement was last reviewed in September 2026, following a round of accessibility work on the site. We revisit it when we make significant changes, and we update the known limitations as things are fixed or as we find new ones. A statement that never changes is not being maintained, and we would rather this one showed its age honestly.

Questions families ask about accessibility

Does this website work with a screen reader?: It is built to. The pages use ordinary headings, lists, links, and landmarks, so a screen reader can announce the structure and you can jump from heading to heading instead of listening to a whole page. Form fields are labeled, and errors in the form are announced rather than only shown in red. We cannot promise perfection on every page, and we do not claim to have tested every screen reader. If something reads wrong or reads as nothing at all, please call us at (323) 675-2991 and tell us which page, because that is exactly the kind of report that gets a fix made.
What should I do if a page is hard to use or I cannot finish something?: Call us at (323) 675-2991. You do not have to fight with the website. An advisor can take the same information over the phone and carry on from there, and telling us what went wrong helps us fix it for the next person. If you would rather write, use our contact page and say which page you were on and what you were using, for example a screen reader, a phone, or a keyboard on its own.
Can I get help by phone instead of using the website?: Yes, completely. Nothing on this site is a required step. The whole service, from the first conversation through the tours and the move itself, works by phone, and for many families that is the faster route anyway. The website exists to answer questions at two in the morning, not to stand between you and a person.
Is this site certified as accessible or fully compliant?: No, and be careful with any site that says it is. There is no official certification for website accessibility in the United States, and this site has not been audited by an outside organization. What we can tell you honestly is the standard we work to, WCAG 2.1 Level AA, that we consider the site partially conformant with it, and what we know is still imperfect. That is on this page, in the known limitations section.
The text is too small for me. Can I make it bigger?: Yes. Hold Ctrl and press the plus key to zoom in, or Command and plus on a Mac, and Ctrl or Command with zero to go back to normal. On a phone or tablet, pinch outward with two fingers. We have not disabled pinch zoom, which some sites do. Windows, macOS, iPhone, and Android also have a display setting that enlarges text in every app at once, which is usually more comfortable than adjusting one site at a time.
Do you use an accessibility overlay or accessibility widget?: No, deliberately. Overlays are the little toolbars that promise instant compliance from a single line of script. They do not deliver it, they often interfere with the screen reader or magnifier a person already has set up the way they like it, and their presence has not kept sites out of court. We would rather spend the same effort fixing the underlying pages, which is what this statement describes.