Trust · Trust disclosure
Semantec SEO aims to make MIRENA information usable across devices, input methods, and assistive technology.
The accessibility commitment covers navigation, headings, contrast, keyboard operation, focus, tables, forms, images, responsive layouts, print documents, and a route for reporting barriers.
Verified facts and boundaries.
These fields identify the entity, product, document, or operational boundary without turning related parties into the same entity.
Accessibility target.
Semantec SEO aims to design and maintain its public pages in line with WCAG 2.2 Level AA. This is a target and operating standard, not a claim of formal certification or perfect conformance.
The work includes visual, keyboard, screen-reader, responsive, zoom, text, table, form, and document considerations.
Core requirements.
- One clear page title and logical heading order
- Keyboard access to navigation, disclosures, links, and essential controls
- Visible focus and sufficient colour contrast
- Text alternatives for informative images and empty alternatives for decorative images
- Labels, instructions, errors, and status messages for forms and tools
- Responsive content that does not hide essential evidence, limits, or legal clauses
- Tables with headers, captions, relationships, and mobile overflow
- Reduced-motion respect where animation is used
- Printable legal and policy documents with stable clause numbering
Product and external platform boundary.
Semantec SEO controls the accessibility of its website content and the interfaces it builds directly. OpenAI controls the ChatGPT interface in which MIRENA runs.
A user experiencing a ChatGPT accessibility issue should use OpenAI's support and accessibility routes. A content or link issue on semantecseo.com should be reported to Semantec SEO.
Content accessibility.
Accessibility is not limited to code. Important meaning should not depend on colour, position, a diagram, or an unexplained abbreviation.
Long policies need descriptive headings, short paragraphs, consistent terms, table summaries, and links that identify the destination. Product pages need visible evidence, limitations, and next steps before a high-commitment action.
Testing approach.
| Area | Representative checks | Release consequence |
|---|---|---|
| Keyboard | Tab order, focus, menus, disclosures, buttons, forms | Block when essential content or action is unreachable |
| Screen reader | Landmarks, headings, names, tables, alerts, image text | Repair missing meaning or duplicated announcements |
| Visual | Contrast, zoom, reflow, spacing, focus, text size | Repair barriers to reading or operation |
| Mobile | Content parity, touch targets, overflow, order | Block when essential information disappears |
| Documents | Print, copy, headings, clauses, links, reading order | Repair before legal or policy release |
Known limitations and third-party content.
A page may contain external links or provider-hosted flows that Semantec SEO does not control. The provider remains responsible for its own interface, although Semantec SEO should choose accessible routes where practical.
No page should claim full accessibility without current testing evidence across the target environment.
Report a barrier.
Email support@semantecseo.com with the page URL, task, device, browser, assistive technology where relevant, observed barrier, and preferred contact method.
Do not include sensitive personal information that is unnecessary for the accessibility request.
Check the controlling first-party and official sources.
These routes support the current public statement. External platform and legal sources remain subject to their own updates.
WCAG 2.2
Official W3C Web Content Accessibility Guidelines.
Semantec SEO contact
Current first-party support route.
MIRENA product overview
Current first-party product and platform boundary.
Move to the page that owns the next question.
Each route has a separate job so company, product, trust, legal, and compliance information does not collapse into one promotional page.
Owned route
Colors and typography
Contrast, hierarchy, reading surfaces, and responsive design.
Open route →
Owned route
Contact
Accessibility feedback and support route.
Open route →
Owned route
Editorial Standards
Readable language, headings, tables, and disclosures.
Open route →
Owned route
AI Output Review
Review of generated alt text, labels, and page content.
Open route →
Owned route
Privacy Policy
Personal data in accessibility requests.
Open route →
Owned route
MIRENA Product
Product scope and external ChatGPT boundary.
Open route →