SwiftSchemaGenerate
    Schema stack

    Accessibility Features Stack

    Accessibility feature/support pages with WebPage + Service or Product context, FAQs, and breadcrumbs.

    Open generatorValidate in Rich Results Test
    Included schema
    Web Page
    Service
    Product
    Frequently Asked Questions
    Breadcrumb
    Fit

    When to use this stack

    • Accessibility features pages for apps or products
    • Support pages outlining accommodations and accessibility policies
    • Pages where FAQs clarify assistive technology and compliance
    Composition

    What is included

    • Web Page

      Declares the accessibility page and its description.

    • Service

      Describes accessibility support services or accommodations offered.

    • Product

      Links accessibility features to the specific product or app.

    • Frequently Asked Questions

      Answers questions about assistive tech, compliance, and support.

    • Breadcrumb

      Provides navigation context to the accessibility page.

    Data contract

    Properties across the bundle

    Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.

    Required properties

    • areaServed.name
    • description
    • itemListElement[].name
    • mainEntity[].@type=Question
    • mainEntity[].acceptedAnswer.text
    • name
    • provider.name
    • serviceType
    • url

    Recommended properties

    • brand.name
    • dateModified
    • description
    • image
    • inLanguage
    • itemListElement[].item
    • mainEntity[].acceptedAnswer.text
    • mainEntity[].author.name
    • mainEntity[].name
    • offers.url
    Copy-ready example

    Combined JSON-LD

    Paste this as one script tag, then replace every example value with data from the live page.

    Validate
    [
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "@id": "https://www.example.com/accessibility#page",
    "name": "Accessibility Features",
    "description": "Accessibility features and support options for the Northwind app.",
    "url": "https://www.example.com/accessibility",
    "inLanguage": "en",
    "dateModified": "2025-07-01"
  },
  {
    "@context": "https://schema.org",
    "@type": "Product",
    "@id": "https://www.example.com/accessibility#product",
    "name": "Northwind App",
    "description": "Productivity app with screen reader and keyboard navigation support.",
    "url": "https://www.example.com/app",
    "brand": {
      "@type": "Organization",
      "name": "Northwind"
    },
    "image": "https://www.example.com/images/app-hero.webp"
  },
  {
    "@context": "https://schema.org",
    "@type": "Service",
    "@id": "https://www.example.com/accessibility#service",
    "name": "Accessibility Support",
    "serviceType": "AccessibilityAssistance",
    "description": "Accessibility support for assistive tech compatibility and accommodations.",
    "provider": { "@type": "Organization", "name": "Northwind" },
    "areaServed": { "@type": "AdministrativeArea", "name": "United States" },
    "offers": {
      "@type": "Offer",
      "url": "https://www.example.com/accessibility#contact"
    }
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Is the app compatible with screen readers?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. The app supports VoiceOver and TalkBack with labeled controls."
        }
      },
      {
        "@type": "Question",
        "name": "Do you offer keyboard-only navigation?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes. All key flows are keyboard accessible and focus states are visible."
        }
      },
      {
        "@type": "Question",
        "name": "How can I request accommodations?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Use the accessibility support form or email the support team."
        }
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
      { "@type": "ListItem", "position": 2, "name": "Support", "item": "https://www.example.com/support" },
      { "@type": "ListItem", "position": 3, "name": "Accessibility", "item": "https://www.example.com/accessibility" }
    ]
  }
]
    Workflow

    Implement and verify

    1. 01

      Start with the live page

      Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.

    2. 02

      Add one JSON-LD script

      Use the combined example as a template in the document head or before the closing body tag.

    3. 03

      Complete regional details

      Fill shipping destinations and timing for every region the page actually serves.

    4. 04

      Link the return policy

      Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.

    5. 05

      Match visible answers

      Add only FAQs that users can read on the same page, with identical answers.

    6. 06

      Validate after changes

      Run Rich Results Test after implementation and whenever price, availability, or policy data changes.

    Quality check

    Common errors and fixes

    • Missing currency or availability

      Use ISO currency codes and complete schema.org availability URLs in Offer data.

    • Incomplete shipping details

      Include shippingDestination.addressCountry and deliveryTime.transitTime with units.

    • Return policy is not connected

      Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.

    • FAQ answers differ from the page

      Keep structured FAQ answers identical to visible answers.

    Questions

    Stack FAQs

    Do I need both Service and Product?

    Use Product for feature descriptions and Service for support processes. Include both if both are visible on the page.

    Should I include compliance standards?

    Yes. Mention WCAG level or accessibility policies in the page content when applicable.

    Primary sources

    References