Accessibility Statement
PlugMonkey is committed to digital accessibility. We aim to meet or exceed accepted standards so our website and Chrome extensions are usable by everyone, including people who use assistive technologies.
Our standard
We design and build the PlugMonkey website and our Chrome extensions to be accessible. Our goal is to conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines (WCAG) at Level AA where applicable, and to follow platform guidance for accessible browser extensions (Chrome, WAI-ARIA). We use semantic HTML, keyboard-accessible controls, visible focus indicators, appropriate ARIA for custom UI, and we do not rely on color or mouse-only interaction to convey information. We test with assistive technologies and keep accessibility in mind with every release.
Scope: This commitment applies to plugmonkey.xyz and to the user interfaces of our Chrome extensions (popups, options pages, in-page modals, and export interfaces).
Standards we align with
Our practices are informed by the following standards and resources:
- Chrome DevelopersMake your extension accessible (MV3) — high contrast, captions, alt text, standard controls, ARIA, keyboard focus.
- Chrome Extensions How ToAccessible UI, keyboard access, visible focus, text scaling, sufficient contrast.
- WAI-ARIARoles, states, and properties for custom controls and dialogs.
- WCAG 2.xContrast (1.4.3), focus visible (2.4.7), keyboard (2.1.1), labels (1.3.1, 4.1.2).
- Firefox Extension WorkshopKeyboard shortcuts, high contrast, toolbar titles.
- WebAIMScreen reader and alt text guidance.
How we meet our standard
Across our website and extension interfaces we apply the following accessibility practices:
Semantic HTML & controls
- Buttons and links use <button> or <a href> — no clickable divs for main actions.
- Forms use proper inputs, selects, textareas, checkboxes with <label for> or visible labels.
- Placeholders are hints only; critical info is not in placeholder alone.
- Modal and page titles use <h1>–<h3> in a logical order.
- Popups use <html lang="en"> and a clear <title>.
ARIA & dialogs
- Modals use role="dialog", aria-modal="true", and aria-labelledby pointing to the title.
- Confirmation dialogs use the same pattern with stable IDs (modal-title, confirmation-modal-title).
- Close and icon-only buttons use aria-label (e.g. "Close modal", "Open Settings").
Keyboard & focus
- Tab order follows the DOM; no arbitrary tabindex reordering.
- Modals close on Escape (shared behavior).
- Visible focus: shared buttons and inputs use :focus-visible (outline/offset) so keyboard users always see where focus is.
- Primary actions are reachable via keyboard; we don't rely on mouse-only interaction.
Links
- Links that open in a new tab use target="_blank" rel="noopener noreferrer" across popups, modals, and settings.
Images & media
- Content images (thumbnails, avatars) use meaningful alt (e.g. video title, "User Avatar").
- Decorative or layout images are not used to convey critical information; decorative SVGs use aria-hidden="true".
Color & contrast
- Shared UI uses design tokens (foreground, background, primary, muted) with light and dark themes.
- Information is not conveyed by color alone — status uses text or icons too.
- Layouts use relative units and flex/grid; zoom and text scaling are not disabled.
Feedback
If you encounter an accessibility barrier in any PlugMonkey extension or on this website, we want to hear from you.
Contact support