Accessibility of this website

Conformance status

This site is partially conformant with WCAG 2.2, level AA. Partially conformant means most of the standard is met, and some of it has not yet been verified to my satisfaction.

There are no accessibility failures I know about. I describe it as partially conformant rather than fully conformant because testing with assistive technology is not finished: VoiceOver on iPhone and iPad has not been tested yet.

What has been tested

• Automated testing against WCAG 2.1 and 2.2, levels A and AA, on every page at phone, tablet and desktop widths. This runs on every change, not once.
• A width sweep from 320 to 1600 pixels on every page, checking that nothing forces the page to scroll sideways.
• Keyboard navigation: that the skip link comes first, that focus order follows reading order, and that no focused control is hidden behind the sticky header.
• Target sizes, including the spacing exception, for every control smaller than 24 by 24 pixels.
• That every page works with JavaScript switched off, including the contact form.
• Testing with the NVDA screen reader in Chrome, on every page: page titles, headings, landmarks, the skip link, lists, the scope-of-work tables, and the narrow-screen menu. The menu was also checked with NVDA in Firefox.
• That when a contact form submission fails, NVDA reads the reason aloud as the page reloads, without the reader having to look for it, and that after a successful one it starts reading at the confirmation rather than at the navigation.
• The contact form’s spam check, by hand with NVDA on the deployed form: it can be reached with the Tab key and completed with the Space bar when it asks for a check, and NVDA announces when it has passed.
• Testing with the VoiceOver screen reader on a Mac, in WebKit, the engine behind Safari: the headings on every page, lists, the scope-of-work tables and their captions, the engagement links, and the narrow-screen menu, which announces whether it is open and closes with the Escape key.
• That after a contact form submission, the first thing VoiceOver reads is the outcome: the reason it failed, or that the message was sent.

The automated checks run whenever any part of the site changes, so a regression fails the build rather than reaching you. The screen-reader tests are scripted and run by hand.

Known limitations and testing still to do

• VoiceOver on iPhone and iPad is not yet tested

  VoiceOver, the screen reader built into Apple devices, has been tested on a Mac. Testing on iPhone and iPad, where most people use it, is still to come, and this page will be updated with what it finds.

• VoiceOver starts at the top of the page after a form is sent

  After a contact form submission, NVDA starts reading at the result. VoiceOver starts at the top of the page instead, though the first thing it reads is still the outcome.

• NVDA can misreport the narrow-screen menu after Escape

  On phones and small tablets the navigation is a native HTML disclosure element. Closing it with the Escape key closes it and returns focus to the menu button, but NVDA in Chrome then announces the menu as expanded: the browser reports it as closed, and NVDA reads an out-of-date copy. Opening and closing the menu with Enter is announced correctly.

• Wide tables scroll sideways

  The scope-of-work tables are too wide for a phone. Rather than hiding columns and losing information, they scroll inside a labeled region, which becomes a keyboard stop whenever the table is wider than the screen. Scrolling is still more work than reading.

Tell me if something does not work

If you hit a barrier on this site, I want to know so I can fix it. Email hector@baselinehealthtech.com or call (541) 250-3321. Tell me the page, what you were trying to do, and what you are using to browse if you know it.

I reply within one business day. If the fix is quick I will make it and tell you when it is live. If it is not quick I will tell you that instead, and what the timeline is.

Technical detail

The site is static HTML and CSS. It carries no tracking scripts and sets no cookies. Four small scripts handle details that nothing depends on: closing the narrow-screen menu with the Escape key, preselecting an option on the contact form, changing the header’s color where it meets the footer, and taking a wide table out of the tab order while it fits on the screen. Every page, including the contact form, works with JavaScript switched off.

Text can be resized to 200 percent without loss of content, and the layout reflows to a 320 pixel viewport without horizontal scrolling. Color is never the only way information is conveyed.

How this statement is maintained

Last reviewed October 2, 2026. It is reviewed whenever the site changes materially, and the list above is updated with what testing has actually been done rather than what was intended.

Granite Peak Holdings, LLC dba Baseline Health Technology, Lebanon, Oregon.