Website accessibility
Accessibility statement
We want everyone to be able to use this website, including people who use a screen reader, a keyboard alone, voice control, screen magnification or larger text. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This page says what we have done so far, how to tell us about a barrier, and how to reach us another way if a page or form does not work for you.
Our target
We build and test this website against WCAG 2.2 Level AA. That is a target we work toward, not a claim that every page is perfect. The most recent test was on September 18, 2026, by our web team: automated Lighthouse accessibility audits on every page template in English and Spanish, plus scripted keyboard, layout and settings tests in Chromium at desktop and phone widths, at the largest text size and with Windows high-contrast simulation. No issues were open at the end of that test.
Display settings you can change
Every page has an "Accessibility" button at the top. It opens display settings that are saved on your device and apply to every page of this site, in English and Spanish.
- Text size. Three sizes. The largest is about 40 percent bigger than normal, and the page reflows so nothing is cut off. Your browser's own zoom (Ctrl or Cmd and the plus key) works on top of this.
- High contrast. Black text on white, darker colors, and every link underlined. If your computer or phone is already set to ask for more contrast, the site uses this look automatically.
- Easier reading spacing. More space between lines, letters, words and paragraphs, which many people with dyslexia or low vision find easier to read.
- Reduce motion. Turns off animations and smooth scrolling. This also happens automatically when your device is set to reduce motion.
- Windows high contrast mode. Buttons, links, the current page in the menu and focus outlines stay visible when Windows replaces the site's colors.
What we have done
- Semantic structure. Pages use real headings in order, landmarks, lists and data tables with captions and header cells, so assistive technology can describe and move through the page. A "skip to content" link is the first item on every page.
- Keyboard access. Every link, button, menu, form field, the display settings panel and the cookie settings panel can be reached and used with a keyboard alone, with a visible focus indicator. Menus and dialogs close with the Escape key and return focus to where you were. The item you have focused is never hidden behind the call bar on a phone.
- Screen readers. Landmarks and menus are named, the current page is announced in the menu, links that open a new tab say so, tables keep their row and column headers on every screen size, and forms announce when a request is being sent or has failed.
- Contrast and size. Text and controls are designed to meet Level AA contrast ratios, and links, buttons and menu items meet the minimum target size. Information is never shown by color alone.
- Reduced motion. If your device is set to reduce motion, the site turns off animations, transitions and smooth scrolling.
- Text and zoom. Pages reflow with no sideways scrolling when text is enlarged to 200 percent or the window is narrowed to a phone width, and nothing is cut off when line, letter and word spacing are increased.
- Forms. Every field has a visible label, required fields are marked, phone and email fields bring up the right keyboard, and error messages are written in text and announced to screen readers.
- Images. Meaningful images have text alternatives. Decorative images are hidden from assistive technology.
- No overlays. We do not use accessibility overlay widgets. We fix the pages themselves.
- Plain language. Family pages are written in short sentences at about a grade 7 to 8 reading level.
How we test
Automated accessibility checks run when the site's code changes. Each page template also gets a manual keyboard pass. Automated tools catch only some problems, which is why reports from real visitors matter to us. Tools and browsers used so far: Lighthouse and Playwright in Chromium. A manual pass with the VoiceOver and NVDA screen readers in Safari, Chrome and Firefox is planned before launch and after each major change.
Known limits
Documents and websites run by others that we link to, such as government PDF forms, may not meet the same standard. If you need the information in one of them, tell us and we will give it to you another way. We know of no open accessibility issues on this site. When one is reported, we will list it here with the planned fix date.
How to report a barrier
- Step 1
Contact us
Call (909) 347-7000 or email info@betahospice.com. Describe the page and the difficulty, and tell us how you prefer to be contacted. Please do not send sensitive medical details in a general message.
- Step 2
Tell us what happened
The page address, what you were trying to do, and the device, browser and assistive technology you were using, if you know. A short description is enough.
- Step 3
We reply and fix it
We acknowledge accessibility reports within 2 business days and give you an initial update within 5 business days, and we agree on follow-up with you for anything more complex. In the meantime we will give you the information or service you needed in a way that works for you.
Other ways to reach us
You never have to use this website to get care or information from us.
- Phone. A hospice nurse answers the phone 24 hours a day, 7 days a week, and can visit when needed. The number is at the bottom of every page.
- Relay. People who are deaf, hard of hearing or have a speech disability can call through the California Relay Service by dialing 711.
- In person or by mail or fax. Our office is in San Bernardino. The address, fax number and office hours are on the contact page.
- Large print, audio or another format. Ask and we will provide it free of charge. See language assistance and our notice of nondiscrimination.
