Accessibility
Building the site and portal to be usable by everyone.
This statement describes ScriptClear's accessibility target, the practices used to work toward it, known limitations, and how to report an accessibility issue.
- Standards
- v0.9 — Pilot draft
- Status
- Published
- Review cycle
- Reviewed quarterly
This page is a plain-language summary of ScriptClear's current practices. It is informational only and is not legal advice. Effective date: pending publication of v1.0 program terms. Questions can be sent through /contact.
Certification is granted for a defined scope and remains subject to monitoring.
- Standards version
- v0.9 — Pilot draft
- Decision basis
- Published criteria
- Independence
- Commercial roles excluded
- Change control
- Dated effective versions
On this page
What this page covers
Commitment
Accessibility as a design target, not an afterthought.
ScriptClear designs the website and portal with the goal of being usable by people with a wide range of abilities, including people who use assistive technology, keyboard-only navigation or reduced-motion settings.
Target standard
WCAG 2.2 AA as the design goal.
ScriptClear designs toward the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, as an internal target. This is stated as a goal ScriptClear is designing toward, not a certified conformance claim or the result of an independent accessibility audit.
Practices
How accessibility is built into the site.
- Semantic HTML structure so headings, landmarks and lists are conveyed correctly to assistive technology
- Keyboard operability for interactive elements, including forms, navigation and the portal
- Color contrast chosen to meet the target contrast ratios for text and interface elements
- Visible focus states so keyboard users can track their position on the page
- Support for reduced-motion preferences, minimizing non-essential animation for users who request it
- Descriptive link text and form labeling rather than reliance on visual cues alone
Known limitations
Where the site currently falls short of the target.
Accessibility work is ongoing, and some areas of the site and portal may not yet fully meet the WCAG 2.2 AA target — for example, some third-party embedded content or complex data visualizations may have partial support for assistive technology.
- Some third-party embedded content may not fully match this statement's accessibility target
- Newer platform features may receive accessibility refinement after initial release
- Legacy content is reviewed and updated on an ongoing basis rather than all at once
Feedback
Reporting an accessibility issue.
- 1
Describe the issue
Send a description of the page, the assistive technology or browser used, and what happened, through /contact.
- 2
Acknowledgment
ScriptClear acknowledges accessibility reports and treats them as a priority category of feedback.
- 3
Remediation
Reported issues are evaluated and addressed based on severity and scope, with follow-up to the reporter where contact information is provided.
FAQ
Questions we hear often
- Is ScriptClear certified as WCAG 2.2 AA conformant?
- No. WCAG 2.2 AA is stated here as a design target, not a certified conformance claim or the outcome of an independent audit.
- How do I report an accessibility problem?
- Use /contact and describe the page, device and assistive technology involved. Accessibility reports are treated as priority feedback.
- Does the site support reduced-motion preferences?
- Yes, non-essential animation is minimized for users whose systems request reduced motion.
Not sure where your organization stands? Start with a preliminary eligibility check.
Compliance should be clear, not complicated
Found an accessibility barrier.
Tell ScriptClear about it through /contact so it can be evaluated and addressed.
Know where you stand. Fix what matters. Stay ready.