Accessibility

Last updated October 9, 2026

StudyScope is a virtual microscope for science classes. Every student in the room should be able to use it, including students and teachers who navigate by keyboard, use a screen reader, magnify the screen, or are sensitive to motion. This page describes where the Service stands today, what we know falls short, and how to tell us about a barrier.

Our target is WCAG 2.2 Level AA. The Service substantially meets it on the pages we evaluated, with the known gaps listed below. If anything on StudyScope gets in your way, email support@thestudyscope.com and we will work with you on a fix or an alternative.

Our commitment

We design and build StudyScope to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level A and Level AA, which also covers WCAG 2.1 AA and the Section 508 web standard (WCAG 2.0 AA). Accessibility checks are part of how we review new features, and we update this page and the conformance report below when the Service changes.

How we evaluated

This is a self-evaluation carried out by the StudyScope developer on October 9, 2026. It is not a third-party audit. The evaluation combined:

Pages evaluated: the home page, the slide catalog (home, browse and category pages, and the slide detail view), the deep-zoom viewer on the slides that anyone can open without an account, the guides index and a guide, About, Privacy, this page, the class join page and the student live-lesson screens, the embeddable slide viewer, and the log-in and sign-up forms.

Not yet fully evaluated: the signed-in teacher workspace (library, lesson editor, point-of-interest editor, live presenting, account, organization and admin screens). It is built from the same components as the pages above, but we have reviewed it only at the code level so far. Nor have we yet tested with screen readers such as NVDA, JAWS, VoiceOver or TalkBack in daily use. Both are next: we plan to extend the evaluation to the teacher workspace, test with screen readers, and commission an independent third-party audit, and we will update this report as each is completed.

Supported browsers and assistive technology

StudyScope runs in current versions of Chrome, Edge, Firefox and Safari, including on Chromebooks, iPads and phones. It relies on standard HTML semantics and ARIA so that it works with the screen readers, magnifiers, voice control and switch software built into or commonly used with those browsers. It does not work in Internet Explorer.

Accessibility features

Known limitations

We would rather tell you about these gaps than have you find them. Each gap that affects WCAG conformance has a planned fix and a target date.

Accessibility Conformance Report

The report below follows the VPAT® 2.5Rev WCAG edition format from the Information Technology Industry Council. Each “Partially Supports” row includes our plan and target date for full conformance.

Product
StudyScope web application (thestudyscope.com)
Version
Production web app as deployed October 2026
Report date
October 9, 2026
Description
A browser-based virtual microscope with a catalog of real, deep-zoom scanned microscope slides, guides, and tools for teachers to save, annotate, measure, build lessons, and present live to students who join with a class code.
Contact
support@thestudyscope.com
Evaluation methods
Self-evaluation by the developer: axe-core 4.10 automated testing plus manual keyboard, structure, contrast, reflow, text-spacing and motion review in desktop Chrome, as described above. No third-party audit; no testing yet with screen readers in daily use.
Scope
Public site, catalog, free-to-view deep-zoom viewer, embeddable viewer, class join and student live-lesson screens, and account forms. The signed-in teacher workspace was reviewed at the code level only.

Applicable standards

Standards and guidelines covered by this report
Standard or guidelineIncluded in report
WCAG 2.0Level A (Yes), Level AA (Yes), Level AAA (No)
WCAG 2.1Level A (Yes), Level AA (Yes), Level AAA (No)
WCAG 2.2Level A (Yes), Level AA (Yes), Level AAA (No)

Terms

WCAG 2.2 report

Criteria new in WCAG 2.1 and 2.2 are marked as such. Remarks describe the evaluated scope.

Table 1: Success Criteria, Level A
CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text ContentSupportsImages have text alternatives and decorative images are hidden from assistive technology. The deep-zoom viewer is named for its slide, and each slide is identified by title, scientific name and stain, with a written description and "What to look for" notes. Points of interest, boxes, drawings and measurements drawn on the slide canvas have a text equivalent in the viewer’s "Labels and measurements" panel (labels, "Go to" buttons, drawing counts and measurement values), kept in sync as items change, and a step’s points of interest and finished measurements are announced through a polite live region. Embedded slides show no overlays. The display-only projector window mirrors the presenting teacher’s screen, where the panel is available.
1.2.1 Audio-only and Video-only (Prerecorded)Not ApplicableThe Service contains no prerecorded or live audio or video content.
1.2.2 Captions (Prerecorded)Not ApplicableThe Service contains no prerecorded or live audio or video content.
1.2.3 Audio Description or Media Alternative (Prerecorded)Not ApplicableThe Service contains no prerecorded or live audio or video content.
1.3.1 Info and RelationshipsSupportsHeadings, lists, landmarks, tables and form labels are marked up semantically; every evaluated page has one main heading and no skipped heading levels.
1.3.2 Meaningful SequenceSupportsReading and focus order follow the visual order. The duplicate copies used to loop the scrolling slide list are hidden from assistive technology.
1.3.3 Sensory CharacteristicsSupportsInstructions do not rely on shape, size, position or sound alone.
1.4.1 Use of ColorSupportsLinks in body text are underlined, and errors and states are given in text, not by color alone.
1.4.2 Audio ControlNot ApplicableThe Service plays no audio.
2.1.1 KeyboardSupportsNavigation, catalog, forms, dialogs and the viewer tool buttons work by keyboard. On the focused slide, arrows or W/A/S/D pan, plus and minus zoom, and 0 resets. The measure tool and point-of-interest boxes (including lesson-editor authoring) have a keyboard crosshair: arrows move it, Enter places each point, Escape cancels. Freehand drawing depends on the path of the pointer’s movement and is the only pointer-only tool, as the exception allows.
2.1.2 No Keyboard TrapSupportsDialogs keep focus inside on purpose and close with Escape or a Close button; the viewer canvas can be tabbed away from.
2.1.4 Character Key Shortcuts (WCAG 2.1)SupportsThe viewer's single-key shortcuts (pan, zoom, reset) only work while the slide image has keyboard focus.
2.2.1 Timing AdjustableSupportsNo task has a time limit. A live lesson ends when the teacher ends it, which is a real-time event.
2.2.2 Pause, Stop, HideSupportsThe scrolling slide list on the home page and the catalog slideshow have pause buttons, and both stop when the device asks for reduced motion.
2.3.1 Three Flashes or Below ThresholdSupportsNo content flashes.
2.4.1 Bypass BlocksSupportsPages with site navigation start with a "Skip to content" link, and the scrolling slide list has its own skip link. Sign-in, sign-up and join pages have no repeated blocks.
2.4.2 Page TitledSupportsEvery page has a unique, descriptive title.
2.4.3 Focus OrderSupportsFocus moves in a logical order. Dialogs take focus when they open and return it when they close; the sign-up steps and form errors move focus to the next field that needs attention.
2.4.4 Link Purpose (In Context)SupportsLink text, or the link text with its surrounding card or sentence, describes the destination. Image links take their name from the image's text alternative.
2.5.1 Pointer Gestures (WCAG 2.1)SupportsPinch-to-zoom has single-tap zoom buttons as an alternative.
2.5.2 Pointer Cancellation (WCAG 2.1)SupportsControls act on release, using standard click events.
2.5.3 Label in Name (WCAG 2.1)SupportsAccessible names of buttons and links contain their visible text.
2.5.4 Motion Actuation (WCAG 2.1)Not ApplicableNo function is triggered by device motion.
3.1.1 Language of PageSupportsEvery page declares English (lang="en").
3.2.1 On FocusSupportsFocusing a control never changes the context.
3.2.2 On InputSupportsTyping in a field or choosing a filter updates results in place without changing the context.
3.2.6 Consistent Help (WCAG 2.2)SupportsContact details (the support email) are on the About and Accessibility pages, which every page footer links to in the same relative order.
3.3.1 Error IdentificationSupportsForm errors are described in text next to the field, marked invalid, and linked to the field.
3.3.2 Labels or InstructionsSupportsEvery field has a visible label and, where needed, a hint (for example, password length).
3.3.7 Redundant Entry (WCAG 2.2)SupportsInformation entered in one sign-up step (seats, organization, code) is carried forward and never asked for twice.
4.1.1 ParsingSupportsObsolete in WCAG 2.2 and treated as always satisfied for WCAG 2.0 and 2.1. Markup is generated by the Vue framework and axe-core found no duplicate-ID or ARIA structure errors.
4.1.2 Name, Role, ValueSupportsControls have accessible names, roles and states (pressed, expanded, invalid). The viewer canvas is exposed as a named application region with keyboard instructions. axe-core reported no name, role or value violations on evaluated pages.
Table 2: Success Criteria, Level AA
CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live)Not ApplicableThe Service contains no prerecorded or live audio or video content.
1.2.5 Audio Description (Prerecorded)Not ApplicableThe Service contains no prerecorded or live audio or video content.
1.3.4 Orientation (WCAG 2.1)SupportsWorks in portrait and landscape; orientation is never locked.
1.3.5 Identify Input Purpose (WCAG 2.1)SupportsName, email, password and organization fields carry autocomplete attributes.
1.4.3 Contrast (Minimum)SupportsText meets 4.5:1 (3:1 for large text) in the light theme, the only theme offered. Viewer controls use light text on dark chrome. Text over photographs sits on a solid or scrimmed backing.
1.4.4 Resize TextSupportsText scales with browser zoom to 200% and beyond without loss of content; pinch-zoom is never disabled.
1.4.5 Images of TextSupportsText is real text. The exceptions are logos, badges and labeled specimen diagrams, where the labels are part of an image with significant other visual content.
1.4.10 Reflow (WCAG 2.1)SupportsEvaluated pages reflow to 320 CSS pixels with no horizontal page scrolling. The deep-zoom slide and wide data tables (like this report) are two-dimensional content and scroll within their own frame.
1.4.11 Non-text Contrast (WCAG 2.1)SupportsFocus rings, buttons, icons and viewer controls meet 3:1. Text fields, selects, text areas, search fields, join-code fields and the selected segment of toggle controls use a dedicated border of at least 3.26:1 against every background they sit on (3.78:1 on white), and focus adds a 2px accent outline (8.8:1). Checkboxes use the browser’s default border.
1.4.12 Text Spacing (WCAG 2.1)SupportsWith line height 1.5, paragraph spacing 2em, letter spacing 0.12em and word spacing 0.16em applied, the home page, catalog, slide browse, slide details and guides lose no content. Subject chips, category labels and tag options wrap, and category descriptions and lesson titles are not clamped.
1.4.13 Content on Hover or Focus (WCAG 2.1)SupportsMenus open on click or Enter and close with Escape. Hover hints are native browser tooltips.
2.4.5 Multiple WaysSupportsContent can be reached through site navigation, catalog search, category browsing, guides and footer links.
2.4.6 Headings and LabelsSupportsPage headings describe each page’s purpose (for example, "Log in to StudyScope", "Get started with StudyScope", "Reset your password"), and form fields have visible, descriptive labels.
2.4.7 Focus VisibleSupportsEvery keyboard stop on evaluated pages shows a visible focus indicator.
2.4.11 Focus Not Obscured (Minimum) (WCAG 2.2)SupportsFocused controls scroll clear of the fixed navigation bar, including when tabbing backward.
2.5.7 Dragging Movements (WCAG 2.2)SupportsEvery drag has a single-pointer alternative: pan buttons in the zoom bar, zoom buttons and slider, click-or-tap placement of both points for measuring and point-of-interest boxes, and "Go to" buttons for points of interest. Freehand drawing is essential dragging and is excepted.
2.5.8 Target Size (Minimum) (WCAG 2.2)SupportsButtons are at least 24 by 24 CSS pixels, most 44. Smaller text links sit inline in sentences or are spaced so that 24-pixel targets do not overlap.
3.1.2 Language of PartsSupportsAll content is in English. Scientific (Latin) names are technical terms, which the criterion exempts.
3.2.3 Consistent NavigationSupportsThe main navigation and footer appear in the same order on every page that has them.
3.2.4 Consistent IdentificationSupportsControls with the same function (Add to Library, zoom, close) are labeled the same way throughout.
3.3.3 Error SuggestionSupportsError messages say how to fix the problem (for example, "Use at least 8 characters").
3.3.4 Error Prevention (Legal, Financial, Data)SupportsPurchases are reviewed and confirmed on the payment processor's checkout page; deleting content asks for confirmation.
3.3.8 Accessible Authentication (Minimum) (WCAG 2.2)SupportsSign-in uses email and password with paste and password-manager autofill allowed, plus a show-password toggle. There is no CAPTCHA or cognitive test. Students never sign in.
4.1.3 Status Messages (WCAG 2.1)SupportsToasts, result counts, form errors, measurement readouts and live-lesson step captions use status, alert or live regions, so they are announced without moving focus.

Report a barrier or ask for help

If you run into a barrier on StudyScope, or need content from the Service in another format, email support@thestudyscope.com with “Accessibility” in the subject. It helps to tell us:

We read every message. We aim to reply within five business days, and we will tell you what we plan to fix and when. Where a fix will take time, we will work with you or your school on an alternative in the meantime. Schools and districts that need this report in another format, or as part of a procurement review, can reach us at the same address.