Accessibility Statement for ExamAdvantage

Effective date: August 16, 2026 Last updated: August 16, 2026

Certification Tool and Die, Ltd. is committed to making ExamAdvantage usable by people with a wide range of abilities. This statement describes what accessibility support ExamAdvantage provides today, what standards we target, what limitations we know about, and how to reach us with concerns or suggestions.


Application targets

ExamAdvantage is distributed as three application targets that share one codebase:

The accessibility features and known limitations described below apply to all three targets unless a target is named explicitly.


Standards we target

ExamAdvantage aims to conform with Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We have not commissioned a formal third-party audit. The improvements described here are self-assessed. We will update this statement as we make further progress.

We have not yet completed verified testing against physical screen readers, Android TalkBack, or keyboard-only use on real hardware. The ARIA markup, focus management, and semantic structure are in place and have been reviewed in source, but end-to-end assistive technology verification is pending. We are working to close that gap.

We do not claim WCAG Level AAA conformance.


What ExamAdvantage provides

For screen-reader users

For keyboard users

For low-vision users

For users with vestibular or motion sensitivity

For users with dyslexia or reading differences

For users who rely on text to speech

ExamAdvantage includes a built-in text-to-speech feature, activated by the 🔊 button in the navigation bar. It is separate from, and complementary to, any screen reader you may use.

The desktop and web applications use the browser's Web Speech API. Long passages are split into short chunks to avoid a known Chromium limitation that drops utterances longer than approximately 15 seconds. The Android application uses the device's native text-to-speech engine.

Note: ExamAdvantage's text-to-speech is a reading aid for sighted users who benefit from hearing content alongside reading it. It is not a replacement for a full screen reader such as NVDA, JAWS, or TalkBack, and it does not expose interactive controls or navigation.

For users of assistive input

ExamAdvantage does not implement its own speech-to-text, custom cursor, dwell click, or switch-access framework. Every interactive element uses standard HTML controls that work with the operating system's built-in accessibility framework:


Where to find and change accessibility settings

Open the ♿ Accessibility panel via the ♿ button in the navigation bar of any ExamAdvantage screen. All settings are saved to your local device and apply immediately. Nothing you configure here is transmitted to us or to any third party.


Known limitations

We list these openly because we would rather you know than be surprised.

Results screen charts have no data table alternative

The Results screen renders two performance charts — one by difficulty level (Easy / Moderate / Challenging) and one by domain — as inline SVG graphics. Both carry role="img" and a brief aria-label ("Performance by difficulty", "Performance by domain"), so screen readers identify them as images with a label, but the underlying data is not accessible from within the chart element itself.

Workaround: all the same data is present as text elsewhere on the Results screen: overall proficiency and correct-answer counts appear in the summary cards above the charts, and per-domain and per-topic proficiency percentages are in the expandable topic tree below them. Screen-reader users can access all figures without the charts.

Quiz screen answer reveal does not use a live region

When you submit answers on the Quiz screen, the result summary ("You answered X of Y correctly") and the individual answer explanations appear by re-rendering the page. There is no aria-live region to announce the transition, so screen-reader users may need to navigate to the result manually rather than hearing it announced automatically.

Glossary overlay may render without background or positioning (Web and Android)

The Glossary panel element in the web and Android applications uses a CSS class that does not yet have a matching rule in the stylesheet. The overlay is present in the DOM, carries appropriate role="dialog" and aria-modal attributes, and responds to keyboard interaction, but it may render without the expected modal background and positioning. A fix is planned for the next release.

Workaround: the Glossary can still be opened and closed with a keyboard. If the visual presentation is broken, closing it and continuing normally is not prevented.

Android speech rate preference is saved but not applied

The in-app speech rate control is present on Android and saves your preference, but the setting is not applied at playback time. The Android speech engine does not expose a rate parameter through the current API integration. The rate at which text is read aloud on Android is your device's default TTS rate. This will be addressed in a future release.

Keyboard and TalkBack walkthrough not yet completed on real hardware

The focus traps, skip links, ARIA roles, and semantic structure described in this statement have been reviewed in source code. End-to-end testing with physical screen readers (NVDA, JAWS, VoiceOver) and Android TalkBack on a real device has not yet been completed. We intend to carry out that testing and address any findings in a near-term release.

ScoreBar self-rating marker uses a tooltip, not a label

In the domain and subdomain score bars on the Results screen, the self-rating position marker carries a title attribute ("Self rating X%") rather than an aria-label. The title attribute is not reliably announced by all screen readers. The same figure is available as text in the legend alongside the bar ("X% self").

Browser print-to-PDF produces untagged output

The Results screen includes a Print / Save PDF button on the desktop and web applications. PDFs produced through the browser's print-to-PDF feature are untagged, which limits their accessibility in PDF readers. A server-side tagged PDF path is on the roadmap.

Content of exam questions

ExamAdvantage does not modify the wording or complexity of exam questions themselves, because doing so would invalidate the practice-study premise. Users with reading differences may find the reading-comfort font and larger text size settings helpful.


How to report an accessibility problem

We take accessibility feedback seriously and treat it as a defect report rather than a feature request.

If you encounter something that does not work with your assistive technology, or if you would like to request an accommodation ExamAdvantage does not currently offer, please email:

accessibility@certificationtoolanddie.com

Please include:

We aim to respond within 5 business days and to fix reproducible accessibility defects in the following release cycle. If a fix will take longer, we will tell you an honest timeline.


What this statement does not cover


Formal complaints

If you have raised an accessibility concern with us and are not satisfied with our response, you may file a complaint with the appropriate regulator in your jurisdiction:


Contact

Certification Tool and Die, Ltd. Attn: Accessibility Coordinator 351 Smith Street #28003 Providence, RI 02908 1.401.684.0091

accessibility@certificationtoolanddie.com

www.certificationtoolanddie.com