<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Accessibility for teams on Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/</link>
    <description>Recent content in Accessibility for teams on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Jan 2025 19:42:55 -0500</lastBuildDate>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Accessibility for content designers</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/content-design/</link>
      <pubDate>Mon, 09 Jul 2018 09:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/content-design/</guid>
      <description>Getting started How to use this guide:&#xA;We recommend conducting accessibility testing throughout the design and development processes. If you have project-specific questions, ask your agency’s accessibility team. Plain language Can you quickly understand the main points of the content?&#xA;Why it&amp;rsquo;s important Karin is not a native English speaker and she sometimes has trouble decoding legal or bureaucratic language. John has a developmental disability and has difficulty interpreting content written above a sixth-grade reading level.</description>
    </item>
    <item>
      <title>Accessibility for front-end developers</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/front-end-development/</link>
      <pubDate>Mon, 09 Jul 2018 09:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/front-end-development/</guid>
      <description>Getting started Accessible front-end development ensures people with different abilities can access, understand, and navigate web content, regardless of how they&amp;rsquo;re accessing it. Front-end developers collaborate with other members of a cross-functional team to implement a robust user experience.&#xA;How to use this guide:&#xA;We recommend conducting accessibility testing throughout the design and development processes. A good place to start testing is on high-touch pages, critical user paths, and site-wide templates.</description>
    </item>
    <item>
      <title>Accessibility for product managers</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/product-management/</link>
      <pubDate>Mon, 09 Jul 2018 09:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/product-management/</guid>
      <description>Getting started Product managers play a vital role in communicating accessibility requirements early in the project lifecycle, ensuring each team member knows their responsibility, and keeping the team accountable for building accessible products. Following these steps, you’ll make sure you’re not only following legal requirements, but making your product more usable for everyone.&#xA;Why you should care Any product released by the government must conform to the standards of Section 508 (which aligns with the W3C Web Content Accessibility Guidelines (WCAG) 2.</description>
    </item>
    <item>
      <title>Accessibility for user experience designers</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/ux-design/</link>
      <pubDate>Mon, 09 Jul 2018 09:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/ux-design/</guid>
      <description>Getting started Accessibility is usability for people who interact with products differently. Your role is to help the team approach accessibility as a facet of user experience rather than checklist of requirements.&#xA;How to use this guide:&#xA;If you have project-specific questions, ask your agency’s accessibility team. Inclusive design Adopt an inclusive design mentality&#xA;Celebrate accessibility requirements as a set of design constraints that help you create a better product for all users.</description>
    </item>
    <item>
      <title>Accessibility for visual designers</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/visual-design/</link>
      <pubDate>Mon, 09 Jul 2018 09:00:00 -0500</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/guides/accessibility-for-teams/visual-design/</guid>
      <description>Getting started Everyone benefits from designs that are easier to see. People with different visual abilities see your designs in varying ways—the diverse nature of impairments creates a wide variation in how your designs are perceived. A clean and clear visual presentation helps everyone make sense of a website&amp;rsquo;s information and functionality.&#xA;How to use this guide:&#xA;We recommend planning for accessibility in your design process and regularly conducting accessibility testing throughout the design and development processes.</description>
    </item>
  </channel>
</rss>
