01
Foundation · Editorial position
Our Commitment to Access
Why accessibility is a precondition of our editorial work, not a feature we layer on top of it.
ScreenExtendersHub exists to help people design productive multi-screen workspaces. That mission is meaningless if our content cannot be perceived, operated, or understood by people who use screen readers, magnification software, switch devices, voice input, captioning, or who navigate with a keyboard alone. Accessibility is not a feature we add — it is a precondition of doing this work honestly.
We design, build, and audit every page on this site against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the global benchmark published by the World Wide Web Consortium. Where we fall short of that standard, we say so on this page rather than hide it. Where a third party imposes a constraint we cannot directly remediate, we name the third party and document the workaround.
Editorial Position
A product recommendation that reaches some readers and excludes others is not a service — it is a sales pitch with collateral damage. Our review work is only as valuable as the population it actually reaches. Accessibility is therefore as foundational as our testing methodology and our affiliate disclosure.
02
Frameworks · Legal anchoring
Standards & Legal Frameworks
The five regimes we track and harmonize against. We design to the strictest applicable standard so one body of work serves all of them.
Primary · Global
WCAG 2.1 Level AA
W3C · International
The Web Content Accessibility Guidelines organize accessibility around four principles: Perceivable, Operable, Understandable, Robust. Level AA is the practical conformance target for nearly every regulatory regime worldwide.
View criteria
Public sector · United States
Section 508
US Rehabilitation Act
Applies to US federal information and communication technology. Substantially harmonized with WCAG 2.0 AA. We treat its requirements as a floor regardless of audience.
Read the law
Civil rights · United States
ADA Title III
Americans with Disabilities Act
Federal courts have repeatedly held that the prohibition on discrimination by places of public accommodation extends to commercial websites. WCAG 2.1 AA is the operative compliance standard.
ADA reference
Public sector · European Union
EN 301 549
European harmonised standard
European accessibility requirement for ICT products and services. Incorporates WCAG 2.1 AA by reference. Legal basis for the EU Web Accessibility Directive and informs the European Accessibility Act.
ETSI standards
Private sector · Ontario
AODA
Accessibility for Ontarians with Disabilities Act
Requires private-sector websites with sufficient revenue to meet WCAG 2.0 AA. Our standard exceeds the threshold by targeting WCAG 2.1.
AODA statute
Civil rights · United Kingdom
Equality Act 2010
UK statute
Requires service providers to make reasonable adjustments for disabled users, interpreted in practice as WCAG 2.1 AA conformance for digital services.
Statute reference
03
Audit · POUR principles
WCAG 2.1 Conformance Matrix
Our self-declared conformance status across the four POUR principles. Hover any criterion code for the requirement; status definitions follow.
Each quadrant below represents one of the four WCAG principles. The chips inside list the AA criteria we audit against, color-coded by status: green means conformant across audited templates, amber means partial (most templates conform, at least one instance does not), red means a documented known issue with a remediation timeline. Each quadrant shows its conformance ratio at the bottom.
P
Principle 1
Perceivable
Information and UI components must be presentable in ways users can perceive.
1.1.1
1.3.1
1.3.2
1.4.3
1.4.4
1.4.10
1.4.11
6 of 7 conformant
86%
O
Principle 2
Operable
UI and navigation must be operable by all users, including via keyboard alone.
2.1.1
2.1.2
2.4.1
2.4.2
2.4.4
2.4.7
2.5.5
5 of 7 conformant
71%
U
Principle 3
Understandable
Information and operation must be readable, predictable, and recoverable.
3.1.1
3.2.1
3.2.4
3.3.1
3.3.2
5 of 5 conformant
100%
R
Principle 4
Robust
Content must be robust enough for assistive technology to interpret reliably.
4.1.1
4.1.2
4.1.3
2 of 3 conformant
67%
04
Radical honesty · Open issues
Known Limitations & Remediation
Four open issues, named by WCAG criterion, with severity, owner, workaround, and target fix window. Resolved items move to the audit trail in section 09.
Publishing these is the point. An accessibility statement that lists no failures is either dishonest or untested. Severity reflects the realistic impact on users who depend on the affected functionality, not theoretical edge cases.
Product images on review pages are pulled directly from Amazon's content delivery network. The alt-text attribute is inherited from Amazon's product listing and is sometimes generic — for example, the manufacturer's SKU rather than a descriptive phrase. Where we have not yet manually overridden this in the page template, the alt text is suboptimal for screen reader users.
Workaround
Every product is also described in the surrounding body text, so screen reader users receive the product context even when the image alt text is suboptimal.
Remediation
Manual alt-text override audit across all SPAP pages, completing by end of Q3 2026. Owner: editorial team.
The interactive compatibility checker on our Buying Guide presents a sequence of conditional questions. Keyboard users can complete the flow, but in some branch paths the focus order returns to the page top rather than the next visible question, requiring an extra Tab cycle.
Workaround
A non-interactive decision-tree fallback is provided in plain text below the widget for users who prefer to bypass the checker entirely.
Remediation
Focus-management refactor of the widget JavaScript planned for Q2 2026. Owner: front-end engineering.
On the Glossary, dense inline cross-references between terms can produce small adjacent tap targets on mobile. WCAG 2.5.5 (Target Size) is a Level AAA criterion and therefore not strictly required at our AA conformance target, but we treat it as a usability obligation.
Workaround
Each term is also accessible via the glossary search and the alphabetical index, both of which use full-row tap targets.
Remediation
Glossary CSS revision to enforce 44px minimum height on all term links, planned for Q4 2026. Owner: design team.
When a visitor submits the form on our Contact page, success and error states are visible but are not always exposed to screen readers via an ARIA live region. The form is functional with assistive technology, but confirmation may require the user to re-read the page rather than receive an automatic announcement.
Workaround
An email auto-reply confirms successful submission for any user who provides an email address.
Remediation
aria-live="polite" region added to the form response container in Q2 2026. Owner: front-end engineering.
05
Compatibility · Lab matrix
Assistive Technology × Browser Matrix
Tested combinations across screen readers, magnifiers, voice input, and keyboard-only navigation. Hover any cell for the testing note.
Compatibility Lab
Last full pass · April 2026
✓ Full pass
! Partial — see known limitations
— Not applicable / not standard
06
Editorial relevance · Why this matters
Accessibility Is Editorial, Not Cosmetic
The audience for our content disproportionately includes people for whom display configuration is itself an accommodation. That makes accessibility editorial.
Multi-screen workspaces are themselves an accessibility tool for many people. Larger displays reduce eye strain. Vertical orientations support readers with visual processing differences. Screen-extender setups enable side-by-side workflows that low-vision users rely on. The audience for our content includes — disproportionately — people for whom display configuration is itself an accommodation.
That makes the accessibility of our reviews more than a compliance question. If a reader cannot perceive the comparison tables on our Laptop Screen Extenders, Portable Monitors, Desktop Screen Extenders, or Docking Stations hubs, they cannot make the purchasing decision the page exists to inform. Failing accessibility means failing the user at the exact moment they need our help most.
07
Recourse · Reporting
Feedback Pathways
If you encounter an accessibility barrier, we want to know. Three pathways, listed in order of fastest response.
How to report an accessibility issue
Please include the page URL, the assistive technology and browser you were using, and a description of what did not work. We aim to acknowledge every report within two business days.
-
The fastest route. Select "Accessibility" as the inquiry type. The form is keyboard-operable and labeled for assistive technology.
-
Email support@screenextendershub.com
For users who prefer not to use a web form, including those whose assistive technology has trouble with the form. Plain text is welcome.
-
If your issue concerns a feature you expected to find, our FAQ covers common navigation and content questions. If it does not resolve your issue, please file a report — that gap is itself information we need.
08
Escalation · External accountability
If Our Response Is Inadequate
An accessibility statement is hollow without an external accountability mechanism. Three escalation steps available to you.
01
Request a written response from the editorial lead
Reply to the original support thread asking for escalation. The editorial lead will respond in writing within ten business days with either a remediation plan and timeline or a substantive explanation of why a remediation cannot be made.
02
File a complaint with the appropriate regulator
In the United States, the US Department of Justice accepts ADA complaints. In the EU, complaints route through your member state's accessibility ombudsperson. In Ontario, see the AODA enforcement office.
09
Public ledger · Change history
Audit Trail
A living record of audits, resolutions, and material updates. Resolved issues from section 04 land here with their resolution date.
April 30, 2026
LaunchInitial publication of the Accessibility Statement
Conformance matrix self-declared at WCAG 2.1 AA across 16 audited criteria. Assistive-technology compatibility lab established with eight tested combinations. Four open issues documented with target remediation windows.
April 22, 2026
AuditComprehensive AT compatibility pass completed
Full traversal testing across NVDA 2025, JAWS 2025, VoiceOver (macOS Sequoia + iOS 18), TalkBack 14, Dragon, and ZoomText. Compatibility-checker widget regression on TalkBack confirmed and documented as WCAG 2.1.1 partial.
April 8, 2026
AuditWCAG 2.1 AA self-audit kickoff
16 success criteria mapped to site-wide templates. Manual contrast verification performed on category hubs and SPAP review templates against the 4.5:1 (text) and 3:1 (non-text) thresholds.
March 14, 2026
ResolvedHeader dropdown keyboard navigation (WCAG 2.1.1)
Premium-dropdown header rework completed. Tab order through dropdown panels now follows visible reading order; Escape collapses panels. Verified across NVDA, JAWS, VoiceOver.
February 2, 2026
ResolvedSkip-link implementation site-wide (WCAG 2.4.1)
Skip-to-main-content link added to the global header template. Visible on focus, routes correctly to the primary landmark on every template.
Document version v1.0 · Effective April 30, 2026 · Next scheduled review October 30, 2026
