[
    {
        "role": "user",
        "content": "give%20me%20a%20summary%20of%20wcag%201.1.1"
    },
    {
        "role": "assistant",
        "content": "Here\u2019s a clear, detailed summary of *WCAG Success Criterion 1.1.1: Non-text Content (Level A)*:\n\n---\n\n## What it Requires\n\n- **All non-text content** presented to users must have a **text alternative** that **serves the equivalent purpose**. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))  \n- Some exceptions apply\u2014for example, content that\u2019s purely decorative, used only for visual formatting, or not visible to users. These can be coded so assistive technologies can **ignore** them. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))\n\n---\n\n## What Counts as Non-text Content\n\nNon-text content includes more than just images. It covers:\n\n- Photographs, illustrations, charts, diagrams, icons, etc. ([pearson.com](https://www.pearson.com/accessibility-guidelines/perceivable-principle/non-text-content.html?utm_source=openai))  \n- Audio or video media, especially if not already covered under other WCAG criteria. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))  \n- Controls or inputs that are non-text (e.g. image buttons). These require a descriptive name. ([digitalaccessibility.nyu.edu](https://digitalaccessibility.nyu.edu/testing/sc111.html?utm_source=openai))\n\n---\n\n## Key Exceptions & Special Cases\n\nOr, more precisely, situations where the full text alternative might be modified or where only a descriptive label is needed:\n\n1. **Purely decorative content**: If it adds no informational or functional value, it does *not* need a meaningful alt text; often a null alt (alt=\"\") is used. ([wcag.com](https://www.wcag.com/authors/1-1-1-non-text-content/?utm_source=openai))  \n2. **Controls/Inputs/Button**: Must have accessible names that describe their purpose. ([accessibility.actumdigital.com](https://accessibility.actumdigital.com/docs/wcag-documents/perceivable/1.1-text-alternatives/1.1.1-non-text-content?utm_source=openai))  \n3. **Time-based media**: Audio or video should have descriptions or titles so users know what they\u2019re encountering. More detailed requirements are handled in WCAG Guideline 1.2. ([digitalaccessibility.nyu.edu](https://digitalaccessibility.nyu.edu/testing/sc111.html?utm_source=openai))  \n4. **Tests/Exercises**: If the test requires senses (like visual or auditory) to be valid, a full text alternative might defeat the purpose. Instead, a description of the purpose is required. ([accessibility.actumdigital.com](https://accessibility.actumdigital.com/docs/wcag-documents/perceivable/1.1-text-alternatives/1.1.1-non-text-content?utm_source=openai))  \n5. **CAPTCHAs**: Since many are sensory-based, you need to provide text alternatives that describe their purpose, plus alternate forms accessible in different modalities. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))\n\n---\n\n## Why It Matters\n\n- People who are **blind or have low vision** rely on screen readers or Braille displays that need text to work. Without alt text, visual content is inaccessible. ([pearson.com](https://www.pearson.com/accessibility-guidelines/perceivable-principle/non-text-content.html?utm_source=openai))  \n- People who are **deaf or hard of hearing** benefit when audio content has transcripts or text equivalents. ([pearson.com](https://www.pearson.com/accessibility-guidelines/perceivable-principle/non-text-content.html?utm_source=openai))  \n- Also important for users with cognitive disabilities or for anyone using device settings / assistive tech that don\u2019t support visual or auditory content. ([pearson.com](https://www.pearson.com/accessibility-guidelines/perceivable-principle/non-text-content.html?utm_source=openai))\n\n---\n\n## How To Implement Correctly\n\nHere\u2019s what effective implementation entails:\n\n- Use HTML attributes like `alt` on images to provide concise descriptions. ([nlm.nih.gov](https://www.nlm.nih.gov/oet/ed/cidi/Accessibility_Fundamentals_WCAG_WAI.pdf?utm_source=openai))  \n- For audio/video, supply transcripts or equivalent narrations, or titles/descriptions if full transcripts are covered elsewhere. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))  \n- Ensure decorative images are given null alt text and are programmatically hidden from assistive technologies. ([accessibility.actumdigital.com](https://accessibility.actumdigital.com/docs/wcag-documents/perceivable/1.1-text-alternatives/1.1.1-non-text-content?utm_source=openai))  \n- Use accessible names/labels for controls, image buttons, etc., so their purpose is clear without needing to see the image. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))  \n\n---\n\n## Common Failures & Pitfalls\n\nSome frequent mistakes include:\n\n- Missing `alt` attributes on images or controls. ([a11yied.com](https://a11yied.com/wcag-rules/1-1-1-non-text-content?utm_source=openai))  \n- Vague, misleading or irrelevant alt text (examples: using filenames like `\"image123.jpg\"` or simply `\"photo\"`). ([wcag.com](https://www.wcag.com/authors/1-1-1-non-text-content/?utm_source=openai))  \n- Covering meaning conveyed through visuals (like color, layout, or icons) without providing that context in text. ([w3.org](https://www.w3.org/WAI/WCAG21/Understanding/non-text-content?utm_source=openai))  \n- Decorative content mistakenly treated as informative, or vice versa. ([accessibility.actumdigital.com](https://accessibility.actumdigital.com/docs/wcag-documents/perceivable/1.1-text-alternatives/1.1.1-non-text-content?utm_source=openai))  \n\n---\n\nIf you like, I can also send you a checklist or examples (good vs bad) for auditing 1.1.1 in practice\u2014would that be helpful?"
    }
]