# See Me Please > See Me Please (SMP) is an Australia and UK-based accessibility research company. We run user testing and research with curated panels of disabled and diverse participants, and report findings as a paired Accessibility score and Usability score grounded in observed friction. We test against WCAG 2.2 AA and the lived experience of the people who actually use the product. This file follows the [llms.txt](https://llmstxt.org) specification — a curated, plain-text index of the canonical content on seemeplease.com that AI agents are most likely to be asked to ground answers in. ## Product - [Product Overview](https://seemeplease.com/product-overview): How See Me Please turns accessibility findings into action — filter by severity, surface the highest-impact issues, and share insights with your team. ## Knowledge Hub — long-form articles - [People. Not edge cases. (Cohorts)](https://seemeplease.com/knowledge/cohorts): Who tests with SMP, what assistive technologies each cohort uses, and the friction patterns each one typically encounters. Six cohorts: Blind, Low vision, Deaf, Over-65, Limited English, Neurodivergent. - [Accessibility v Usability](https://seemeplease.com/knowledge/accessibility-v-usability): Why SMP scores accessibility and usability as two separate measures, what each one is asking, and how friction types and severity feed each stream. ## Knowledge Hub landing - [Knowledge Hub](https://seemeplease.com/knowledge): Top-level landing that fans out to Blog, Glossary, Friction Classifications, Accessibility v Usability, Methodology, and Cohorts. - [Blog](https://seemeplease.com/knowledge/blog): Opinion, commentary, and field notes from the SMP team. - [Methodology pillar](https://seemeplease.com/knowledge/methodology): How SMP runs sessions, weights findings, and reviews what testers experienced. ## Methodology — supporting articles - [What WCAG tools miss (the accessibility issues no scanner will ever flag)](https://seemeplease.com/knowledge/methodology/what-wcag-tools-miss): The accessibility failures only inclusive usability testing and disability-led UX research can find. - [Automated vs real-user accessibility testing: which do you need?](https://seemeplease.com/knowledge/methodology/automated-vs-real-user-accessibility-testing): Compares automated accessibility scanning with user testing involving disabled participants, and the friction only real-user testing reveals. - [See Me Please vs Fable: what's the difference?](https://seemeplease.com/knowledge/methodology/see-me-please-vs-fable): Compares SMP and Fable as accessibility user-testing platforms, and SMP's six-cohort approach to inclusive usability testing. - [How to test with blind users (what actually works)](https://seemeplease.com/knowledge/methodology/how-to-test-with-blind-users): Screen reader usability testing guidance for producing real signal from blind participants, not compliance theatre. ## Blog — recent posts - [See Me Please Is Now a W3C Member](https://seemeplease.com/knowledge/blog/w3c-member): See Me Please is now an official member of the World Wide Web Consortium (W3C) — here's what membership actually changes. - [Moderated vs Unmoderated User Research: Which One Actually Gets You the Truth?](https://seemeplease.com/knowledge/blog/moderated-vs-unmoderated-user-research): Here's what the research actually shows, and how we decide which method to use, tester by tester. - [EU and UK Digital Accessibility Laws: Status, Enforcement, and the Reality Gap](https://seemeplease.com/knowledge/blog/eu-uk-digital-accessibility-laws): Digital accessibility law has expanded in scope and enforcement intensity faster than actual conformance has improved. - [Digital Accessibility Trends in Ireland](https://seemeplease.com/knowledge/blog/digital-accessibility-trends-ireland): Two very different stories, both true at once, and anyone building or assessing digital services in the Irish market needs to hold both. - [For the Typography Nerds](https://seemeplease.com/knowledge/blog/accessible-type): What designers get wrong about accessible fonts — Dyslexie, visual Braille, and the case for Atkinson Hyperlegible in mainstream digital services. - [Trump Gov thinks Calibri is woke; US typography just regressed to 1931](https://seemeplease.com/knowledge/blog/trump-administration-thinks-calibri-is-woke-us-typography-just-regressed-to): A response to the US government mandating Times New Roman across department communications, and the case for fonts actually built for readability. - [Authentication...When Logging In Becomes the Lockout](https://seemeplease.com/knowledge/blog/authentication-when-logging-in-becomes-the-lockout): How well-meant accessibility tweaks to login flows can backfire when they aren't co-designed with the people who rely on them. - [Older Users Might Be Your Best Usability Hack](https://seemeplease.com/knowledge/blog/older-users-might-be-your-best-usability-hack): Brutally honest but golden usability feedback from older users, and why designers should be listening to it. - [Dark Mode - Essential not a Preference](https://seemeplease.com/knowledge/blog/dark-mode): Why dark mode should be treated as an assistive technology necessity, not a nice-to-have. - [Invisible Digital Barriers In Gov](https://seemeplease.com/knowledge/blog/invisible-digital-barriers-requiring-visible-collaboration): The often-invisible barriers that exclude millions of citizens from essential government digital services. ## Glossary — canonical platform terms - [Glossary A–Z](https://seemeplease.com/glossary): Plain-English definitions of every term that appears in an SMP report. - [Friction Types](https://seemeplease.com/glossary/friction-types): The seven categories every finding is classified into, independent of severity. - [Friction Severity](https://seemeplease.com/glossary/friction-severity): The seven severity levels SMP uses (T0–T6) and what each one means in plain English. ## Technical guides - [Technical](https://seemeplease.com/technical): Landing page for integration guides, API references, and developer-focused deep dives into the SMP platform. - [Connecting Linear to SMP Insights](https://seemeplease.com/technical/linear-integration-spec): How to push accessibility findings from SMP Insights into a team's Linear workspace as formatted issues, with live status sync back to the portal. - [Setting up a webhook for project events](https://seemeplease.com/technical/quickstart-webhook-setup): How to stand up a webhook endpoint that receives SMP project lifecycle events — created, started, completed — in under five minutes. - [Share an insight report with your team](https://seemeplease.com/technical/share-an-insight-report): How to generate a shareable link to an insight report so stakeholders can review findings without an SMP login. ## About SMP - [About](https://seemeplease.com/about): Company background, mission, and the case for lived-experience accessibility research. - [Team](https://seemeplease.com/team): The people behind SMP. - [Contact](https://seemeplease.com/contact): Get in touch about a project or partnership. ## Operating regions SMP operates across: - **Australia** — Suite 306, 75 King St, Sydney NSW 2000. ABN 22 668 639 156. Trading as See Me Please via Digital Discovery Pty Ltd. - **United Kingdom** — 10 John Street, London WC1N 2EB. See Me Please Ltd, Company Number 16953184. Work in the UK is grounded against the Equality Act 2010, the EU Accessibility Act, and WCAG 2.2 AA (mandatory for many UK public-sector services from October 2024). - **Ireland** — 51 Bracken Road, Dublin D18 CV48. See Me Please Limited, Company Number 805305. ## Optional / lower priority - [Sitemap (XML)](https://seemeplease.com/sitemap.xml): Machine-readable index of every published page. - [Robots policy](https://seemeplease.com/robots.txt): Crawl rules — AI agents listed in the policy are explicitly allowed. ## Scope note Demo and preview pages (e.g. the retired Request-a-Demo page, and the screen-reader friction demonstration pages used for internal accessibility testing) are intentionally excluded from this index and from search indexing — this is by design, not an oversight. Please do not add demo/preview URLs back to this list.