top of page

FRMWRK

Accessibility Statement

This statement was last updated on 10.02.2025

 

We at FRMWRK are working to make our site frmwrk.me accessible to people with disabilities.

What web accessibility is

FRMWRK is building tools that work for as many people as possible—including people who use assistive technologies or need additional supports. We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA and applicable laws. Accessibility is an ongoing practice: design, content, and code all need continuous improvement and user feedback.

Accessibility adjustments on this site

 We have adapted this site in accordance with WCAG [2.0 / 2.1 / 2.2 - select relevant option] guidelines, and have made the site accessible to the level of [A / AA / AAA - select relevant option]. This site's contents have been adapted to work with assistive technologies, such as screen readers and keyboard use. As part of this effort, we have also [remove irrelevant information]:

  • We’ve implemented (or are implementing) the following adjustments:

    • Structure & semantics

  • Semantic HTML landmarks (header, nav, main, footer) and skip-to-content links.

  • Descriptive page titles, headings in logical order (H1–H6), and meaningful link text.

    • Keyboard & focus

  • Full keyboard navigation with visible focus indicators.

  • No known keyboard traps; modals and menus return focus on close.

    • Assistive tech support

  • Appropriate ARIA labels/roles, aria-live for toasts/alerts, and accessible form labels, instructions, and error messages.

  • Alt text for meaningful images; decorative images marked appropriately.

    • Color, contrast, motion

  • Target contrast ratio of 4.5:1 for text and 3:1 for large text/icons.

  • Honors user settings for prefers-reduced-motion to limit animations.

    • Media & documents

  • Captions for hosted videos (rolling coverage as we publish).

  • Transcripts for audio content where applicable.

  • Moving toward tagged PDFs for screen-reader accessibility.

    • Layout & text

  • Responsive design for zoom/resizing to 200%+ without loss of content or functionality.

  • Clear, plain-language copy and consistent component patterns.

    • Forms

  • Input labels, instructions, and error prevention where feasible.

  • Logical tab order and accessible button controls.

  • Personalization

  • In-progress options for font size, color themes, and reduced visuals.

Declaration of partial compliance with the standard due to third-party content [only add if relevant]

FRMWRK is in active development. We are partially compliant with WCAG 2.2 AA. Known limitations and work-in-progress areas include:

  • Some video lessons still awaiting captions or transcript verification.

  • A subset of legacy PDFs and long-form downloads are not fully tagged for accessibility.

  • Certain charts/graphs (e.g., analytics) may lack full text equivalents; we’re adding summaries and data tables.

  • Occasional contrast or focus state regressions may appear in new UI components until audits catch up.

  • Third-party embeds (e.g., payment, auth, calendaring) may have accessibility constraints beyond our direct control; we evaluate vendors and provide alternatives where possible.

We conduct automated checks (e.g., Lighthouse/axe) and manual tests (keyboard-only; popular screen readers on major browsers/OS). Issues found are prioritized in our accessibility backlog and remediated on a rolling basis.

Accessibility arrangements in the organization [only add if relevant]

  • Accountability: An Accessibility Lead coordinates audits, roadmaps, and release checks.

  • Standards: We design and review against WCAG 2.2 AA and inclusive design best practices.

  • Process:

    • Design system tokens for contrast, focus, spacing, and motion.

    • Pre-merge automated checks; periodic manual audits.

    • Content guidelines for plain language, headings, alt text, and link style.

  • Procurement: We prefer vendors and embeds with documented accessibility conformance.

  • Training: Ongoing team training for designers, engineers, and writers.

  • User feedback: We invite people with disabilities to test betas and give feedback that directly informs our backlog.z

Requests, issues, and suggestions

We welcome your feedback. If you need an alternative format, encounter a barrier, or have an idea to improve accessibility, please reach out.

  • Email: accessibility@frmwrk.me

  • Subject line: “Accessibility Request” or “Accessibility Issue”

  • Include (if possible): page/feature, steps to reproduce, your browser/OS or assistive tech, and any screenshots.

  • ​

Our commitment:

  • We’ll acknowledge your message within 3 business days.

  • We aim to provide a substantive response or remediation plan within 10 business days (complex issues may take longer; we’ll keep you updated).

  • For alternative formats (e.g., a tagged PDF or transcript), we will provide an estimated delivery window and accommodations in the interim.

bottom of page