Accessibility
What this site does to stay usable, what has actually been tested, and what hasn't yet. The last part is the honest bit most accessibility statements leave out.
The standard we build to
We aim at WCAG 2.1 Level AA. That is a target we work toward and test against, not a certification — nobody has audited this site on our behalf, and we would rather say so than imply otherwise.
What is in place
Every page has one main heading and a heading structure that runs in order, so a screen reader can navigate by headings without hitting a gap.
A skip link is the first thing keyboard focus reaches, so you can jump past the navigation straight to the content instead of tabbing through every menu item on every page.
Every image carries alternative text, every form field has a real label, and every link and button has a name that says where it goes or what it does.
Focus is always visible — a two-pixel amber outline, offset, on whatever element you are on.
Wide data tables scroll sideways on narrow screens and can be scrolled from the keyboard, not just by dragging.
Text colours are chosen against their backgrounds for contrast. Our amber never carries white text, because that combination fails the standard even though it looks fine.
If your system is set to reduce motion, the site respects it.
The site works without JavaScript for reading. Submitting the bid form needs it, because the bot check and the file upload do.
Known gaps
This is a real list, from an audit run against the built site on 4 August 2026. It is not complete, because no such list is.
It has not been tested with an actual screen reader. Automated checks catch structure; they do not catch a page that is technically correct and still confusing to listen to. VoiceOver and NVDA passes are outstanding.
It has not been tested at 200% zoom or 400% reflow, and it has not been checked against a screen magnifier.
The bot-protection widget on our forms is a third-party component. We chose one that behaves well and stays invisible for most people, but we do not control its markup.
The error page shown if the site itself fails to load is generated by our framework and does not carry the same landmarks as the rest of the site.
Uploading files needs a pointer or a keyboard-accessible file dialog. If that is a barrier for you, email the plan set instead and we will handle it exactly the same way.
Reporting a problem
If something on this site is hard to use, call (903) 513-4138 or email hello@premiumprecision.us and tell us what happened. It gets fixed rather than logged.
You do not need to describe it in technical terms, and you do not need to know what went wrong. Telling us what you were trying to do and what the site did instead is enough.
If a page is in your way and you need the information today, call and we will read it to you or send it in another format. That is not a workaround we are embarrassed by — it is a phone number, and it works.