Built to be usable by every member.

WCAG 2.2 AA is the bar. Human review is how we hold it.

Marqee's target conformance level for marqee.com and the member dashboard is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We treat that standard as the floor rather than the ceiling: it is the minimum a career service ought to meet before it invites anyone to entrust their livelihood to it. We design against it up front, we audit against it as we ship, and when we find gaps we say so on this page rather than quietly hoping nobody notices.

Automated scans catch a lot, but not enough on their own. A large share of the barriers real members hit — a label that scans as valid but reads confusingly under a screen reader, a focus order that jumps around a page, a chart that technically has alt text but doesn't tell you what the chart says — only surface when a human sits down and works through the flow. Our accessibility review is a person with a keyboard and a screen reader running the actual task the member is trying to run, not just a linter report. Both matter, and we do both.

Foundations already in the site and the dashboard.

These are the concrete things a member using assistive technology will find working today across marqee.com and the member experience. Each one has been checked in a real assistive-technology session, not only in an automated scan.

• Semantic HTML markup. Real headings, real landmarks, real lists — no divs impersonating structure. Screen readers can navigate the page by heading, region, and list without guessing.
• Full keyboard navigation. Every interactive control — nav menus, plan toggles, FAQ disclosures, form fields, dashboard actions — is reachable and operable with a keyboard alone. A visible skip-to-content link at the top of every page jumps past the nav to the main region.
• Visible focus rings on every focusable element. We don't strip default focus outlines without replacing them. The active control is always obvious, in both dark and light modes, so keyboard users never have to guess where they are on the page.
• ARIA live regions for asynchronous surfaces. When the dashboard updates in the background — a new application queued for approval, a strategist message arriving, a status change on a submission — screen-reader users are notified through aria-live announcements rather than only through a visual change they might miss.
• Sufficient color contrast in dark and light modes. Body text meets a 4.5:1 contrast ratio against its background, and large text and UI components meet the 3:1 threshold, in both dark-hero surfaces and light content surfaces. The same standard applies to icons that convey meaning.
• Respect for reduced-motion preferences. If your operating system requests reduced motion, our beam animations, transitions, and parallax scroll effects are disabled or shortened. Nothing on the site relies on motion to communicate meaning.
• Screen-reader tested on the three we care most about. Every marketing page and every core dashboard flow is checked in VoiceOver on macOS and iOS, NVDA on Windows, and TalkBack on Android. New surfaces get the same treatment before they ship.

Where we're not there yet, and what we're doing about it.

A statement without honest gaps is a marketing page dressed as a compliance page. These are the surfaces we know don't fully meet AA today, along with the mitigation we've put in place while the fix is in flight.

• The placement feed chart on marqued.html. The interactive chart component on our public placement feed has partial ARIA labeling — the trend summary and time-range control are announced, but individual data points don't yet have the granular labels a screen-reader user would want to explore the series in detail. Mitigation: a plain-text summary of the same data sits directly above the chart and is fully readable by assistive technology. Full data-point labels and a keyboard-accessible data table alternative are on our next accessibility milestone.
• User-generated personal site templates. The personal-site builder lets members publish a page at marqee.com/@username. The templates we ship and verify meet AA, but members are able to customize copy, structure, and images. Custom-authored content — a low-contrast color choice, an image without alt text — can drop the finished page below AA. Mitigation: our standard templates are AA-verified as shipped, the builder surfaces contrast and alt-text warnings during editing, and we're working on making those warnings blocking rather than advisory for the fields where a violation would harm a visitor most.

If you find something not listed here, we want to know. Reporting instructions are below — real member reports are how the list gets shorter.

Real hardware, real software, real workflows.

We test against the platforms our members actually use, on current browser and operating-system versions, running the same tasks a member would run. That includes the sign-up flow, the plan-purchase flow, the strategist chat, and the weekly readout — the surfaces where a barrier would cost someone the most.

• VoiceOver on macOS (Safari) and iOS (Safari) — our baseline for Apple platforms.
• NVDA on Windows (Chrome and Firefox) — our baseline for Windows screen-reader users.
• TalkBack on Android (Chrome) — our baseline for Android members.
• Keyboard-only navigation across all supported browsers, with no pointer device attached.
• OS-level zoom and browser zoom up to 200%, plus reflow at the 320 CSS-pixel width WCAG requires.
• Operating-system dark-mode and light-mode preferences, including forced-colors mode on Windows.

Any content on marqee.com, in a format that works for you.

If a page on marqee.com — a pricing page, a guide, a policy, a strategist bio — doesn't work for you in its published form, we will produce the same content in an alternative format on request, at no cost. That includes plain-text versions stripped of layout, large-print versions at a font size you specify, and read-aloud versions delivered as an audio file for content that isn't practical to have your own screen reader dictate.

We also welcome requests we haven't listed — Braille-ready files, EPUB, a version with simplified language, a phone call with a strategist who reads the content aloud in real time. Ask, and we'll get you what you need.

How to report a barrier, and what happens next.

If something on marqee.com or in the dashboard doesn't work with your assistive technology, or doesn't meet a standard you rely on, tell us. The fastest path is email to accessibility@marqee.com. Include the URL, a short description of what went wrong, and the assistive technology and browser you were using if you're able to. If describing the barrier is itself hard because of the barrier, send whatever you can — a subject line saying "accessibility issue" and your account email is enough to get us started.

Every report is acknowledged within five business days by a real person on our team, not a form-letter autoresponder. The acknowledgement will name the person handling your report, tell you what we've been able to reproduce, and give you a clear estimate of when we expect a fix. Where a fix is going to take longer than a couple of weeks, we'll offer an interim workaround so you're not blocked in the meantime.

If you're not satisfied with our response, you can escalate directly to Marqee's accessibility owner — the same address, with "escalation" in the subject line, will route your message to the leader responsible for the program rather than the responder who first picked it up.

How this stays honest as the site changes.

Accessibility on a live product isn't a one-time audit that stays true forever. New pages ship, dependencies update, copy gets rewritten. We keep the standard in force with a two-track audit cadence, and we publish the outcome of each pass so members can see what's changed.

Outcomes of each pass — what was found, what was fixed, and what's carried forward — are summarized in our public changelog. If a serious barrier is found between audits, we don't wait for the next cycle; we fix it and note it in the changelog when it ships.

Standards and jurisdictions.

Marqee is committed to substantially conforming with the following, and treats a shortfall against any of them as a defect to be fixed rather than a gap to be litigated:

• Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the international technical standard we build against, published by the W3C.
• Americans with Disabilities Act (ADA) — United States. As a service made available to members in the United States, we work to ensure marqee.com and the member dashboard are usable by people with disabilities in a manner consistent with Title III of the ADA.
• Accessibility for Ontarians with Disabilities Act (AODA) — Ontario, Canada. Where AODA applies to our services to members in Ontario, we work to conform to its Information and Communications Standards at the AA level.

Where local law imposes a stricter or additional standard on services offered in a given jurisdiction, that standard applies in addition to — not in place of — the commitment above. If you believe a specific legal requirement in your jurisdiction is not being met, please tell us through the reporting channel above so we can address it directly.