Accessibility Statement
Last updated: September 5, 2026
Healthcare SBC is committed to making our website usable by as many people as possible, including people with disabilities. We treat accessibility as a functional requirement rather than a compliance checkbox.
Conformance target
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive and neurological disabilities.
Measures we take
- Semantic HTML structure with correct heading hierarchy and landmark regions
- Keyboard navigability throughout, with a visible focus indicator on every interactive element
- A skip-to-content link for keyboard and screen reader users
- Color contrast ratios meeting WCAG AA for text and interactive elements
- Text alternatives for non-decorative images and appropriate ARIA where native semantics are insufficient
- Support for the prefers-reduced-motion setting
- Form inputs with associated labels and programmatically linked error messages
- Responsive layouts that support zoom to 200% without loss of content or functionality
Known limitations
We are aware that accessibility is ongoing work rather than a finished state. Third-party embedded content, such as video players or scheduling widgets, may not fully conform to our target. Where we identify a barrier we cannot immediately remove, we work to provide an equivalent alternative.
Feedback and assistance
If you encounter an accessibility barrier on this site, or need information in an alternative format, please contact us at info@healthcaresbc.com or call (609) 428-8307. Please describe the page, the barrier you encountered and the assistive technology you were using. We aim to respond within three business days and will work with you to provide the information you need.
Assessment approach
We evaluate accessibility through a combination of automated testing, manual keyboard and screen reader testing, and review against the WCAG 2.2 success criteria during development. We welcome reports from users, which frequently identify issues that automated tooling does not.
