Accessibility
Accessibility statement
Last tested and reviewed 28 Oct 2026
Tiermark is built and operated by Edwards Consulting Group in Swansboro, North Carolina. We want everyone who works with defense contracts to be able to read this site and use its tools, whatever their abilities and whatever they use to browse. This page says what we aim at, what we have tested, what we know is not yet right, and how to tell us about a problem.
The standard we aim at
The public pages of tiermark.io are built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the W3C Recommendation of 12 December 2024. The site follows the conventions of the U.S. Web Design System: plain text on white, one link colour, a visible focus ring on every control, a skip link to the content, one heading structure per page, and no content that moves, flashes or plays on its own. Pages are built to work at 400 percent zoom and on a phone without sideways scrolling.
What was tested, and how
The nineteen public pages below were run through axe-core 4.13.0 (Deque Systems), through Playwright 1.63 in Chromium at a 1280 pixel width, with the rules for WCAG 2.0, 2.1 and 2.2 at Levels A and AA and axe’s best-practice rules turned on. That was done twice: on 25 October 2026 against the site running on a local development server, and on 28 October 2026, after the site’s colours changed, against our test environment. Each time the same pages were then loaded at a 320 pixel width to check for sideways scrolling. The runs are automated: they check what a machine can check, such as names, roles, landmarks, contrast, form labels and language, and they do not replace use by a person with a screen reader or a keyboard alone.
- Home /
- Pricing /pricing
- For suppliers /suppliers
- SPRS score calculator /sprs-score-calculator
- Requirements /requirements
- A requirement family (3.1 Access Control) /requirements/3-1-access-control
- About /about
- Security /security
- Guides /guides
- A guide (CMMC Phase II is suspended) /guides/cmmc-phase-2-suspension
- Rule changes /rule-changes
- Help center /help
- A help article (Frequently asked questions) /help/faq
- A help article with screenshots (Your supplier map) /help/your-supplier-map
- Privacy notice /privacy
- Terms of service /terms
- Sign in (Tiermark's own page) /sign-in
- Look up a company by UEI /lookup
- This page /accessibility
The guides, the help articles and the requirement families share one template each, so one of each was tested rather than all of them. Screenshots in the help center must carry a description or the site’s tests fail.
What was found, and fixed
The first run found three distinct problems, one a WCAG failure and two axe best-practice rules, each fixed the same day before this page went up, and a second run of all nineteen pages then found none.
- On the sign-in page, the email field’s autocomplete attribute carried two field names, which is not a valid value (WCAG 2.1 success criterion 1.3.5, Identify Input Purpose). It now carries one.
- On every page, the line at the top that said who runs the site sat outside any landmark, so a screen reader moving by landmark would skip it. That line has since been removed; the footer says who runs the site.
- On the pricing page, a section named “For suppliers” shared its name with the footer’s “For suppliers” group, so the two landmarks could not be told apart. The section is now “Plans for suppliers”.
The first run’s 320 pixel check found two pages wider than the screen, which at that width is a phone in portrait or a desktop browser at 400 percent zoom: the SPRS score calculator and the Requirements index (371 and 343 pixels). The calculator’s rows now wrap and the Requirements table stacks into cards.
The run of 28 October found no problems on any of the nineteen pages, and every one of them fits at 320 pixels.
On 25 October axe marked some text as “needs review” for colour contrast, where it could not work out the background behind the text; on 28 October, with the new colours, it marked none. The text is a blue-black of about 14 to 1 against white, the secondary text a grey of about 6.1 to 1, and the links a teal of about 7.6 to 1, all above the 4.5 to 1 that Level AA asks for. Because the teal is close to the text colour, links inside a paragraph are underlined. We have not yet checked each colour by hand.
Known limitations
- The second step of signing in is not ours. After you enter your email on Tiermark’s sign-in page, the password, authenticator code or passkey step is Amazon Cognito’s managed sign-in page. We do not control its markup and have not tested it. If it gives you trouble, write to us and we will take it up with AWS and look for another way in for you.
- The SPRS score calculator asks for a lot of keyboard travel. Each of the 110 requirements has a row of four answer buttons, so a person using the keyboard alone tabs through every button, up to 440 stops, with no arrow-key shortcut between the answers of one requirement. The Not answered filter and the family folds, which start closed, shorten the trip, and the running score is announced as it changes. A shorter keyboard pattern is on the list.
- Only automated testing so far. Nobody has yet walked the site end to end with a screen reader or with the keyboard alone, and no person with a disability has reviewed it. That is the next step, and this page will say when it has happened.
- Company profiles and lookup results. The lookup form was tested empty; the results it returns and the public company profiles it leads to were not part of this run.
- The console is not covered by this statement. The signed-in console, where primes and suppliers work, is built on the same components but has not been through this test. The statement will widen to it when it has.
- Files you download. An audit package is a zip of PDF, CSV and JSON files, and the System Security Plan export is a PDF generated from your answers; neither has been checked with assistive technology.
Reporting a problem
If something on this site does not work for you, write to help@tiermark.io and a person will answer. Tell us the page, what you were trying to do, and what you were using (browser, screen reader or other assistive technology), and we will fix what we can and tell you what we cannot. If you need the information on a page in another form, ask and we will provide it.
How this page is kept current
The date at the top is the date of the last test. When the public pages change in a way that could affect accessibility, the test is run again and this page is updated with what it found. The method, the pages and the findings above are recorded in the site’s own repository so a later run can be compared with this one.