How do I write a concise note about accessibility features on a product page?

Start with an evidence check, not a marketing phrase. Write down each feature you might mention and what confirms it: for example, a product specification, a documented review, or a test record. Keep the description tied to that evidence. If all you have verified is that a control has a tactile marker, say that; do not turn it into a claim that the whole product is easy to use for everyone.

W3C guidance recommends describing functionality and known limitations in simple, common language. It also treats an accessibility statement as distinct from a technical assessment or declaration of conformity. That guidance is about statements for digital content, not an audit of any particular product, so it does not confirm your product’s features or compliance. [S1]

Make a small evidence table for your own review, even if you do not publish it. For every proposed detail, record the exact feature, the source of confirmation, and the scope of what was checked. Include known limitations that could change how a reader understands the feature. If a detail is unverified, leave it out or mark it for confirmation rather than smoothing it into a confident claim.

For a digital product, note which version or environment your evidence covers if that information is available. W3C guidance says an accessibility statement should identify the standard applied and, where relevant, the environments tested; it does not prescribe a product-specific checklist or establish that a product meets a standard. [S1] For other kinds of products, use evidence appropriate to that product and avoid implying the digital-content guidance is an audit method.

Here is a hypothetical example. Assume the product team has verified only that a control has a tactile marker and that the setup guide is available as a tagged digital document. Assume they have also confirmed that a different control has no tactile marker. Those details must be replaced with your actual verified facts:

“Accessibility features: The [control name] has a tactile marker. The setup guide is available as a tagged digital document. The [other control name] does not have a tactile marker.”

This names specific features and a known limitation without claiming that the product is fully accessible, suitable for every person, or compliant with a standard. If the document’s status has not been checked, remove that sentence. If you have only checked one version or setup, do not suggest the note covers other versions or conditions.

Use one or two sentences, each doing a clear job: identify a verified feature, then mention a relevant known limitation. Prefer concrete descriptions over a blanket label such as “fully accessible.” Include a standard or testing context only if you have evidence for that specific reference and scope. W3C guidance supports identifying the standard applied and relevant environments tested in accessibility statements, but does not establish that any particular product conforms. [S1]

Before publishing, ask a reviewer responsible for the product information to confirm that each statement matches the evidence and applies to the version being described. If the evidence is missing or unclear, narrow the wording, seek confirmation, or omit the claim. A short note can help readers understand what is known; it cannot substitute for an assessment.