<commit_before>import { FC, createElement as h } from 'react';
import { Helmet } from 'react-helmet-async';
import { PageProps } from '@not-govuk/app-composer';
import { A, NavigationMenu } from '@not-govuk/components';


export const title = 'Inclusive language';
const description = 'Accessibility guidance for xxx content';
export const section = 'Accessibility';

const Page: FC<PageProps> = ({ location }) => (
  <div className="govuk-grid-row">
    <Helmet>
      <title>{title} - Home Office Design System</title>
      <meta name="description" content={description} />
      <meta name="og:title" content={title} />
      <meta name="og:description" content={description} />
      <meta name="og:article:section" content={section} />
    </Helmet>
    <div className="govuk-grid-column-one-quarter">
    <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Page structure</span>
      <NavigationMenu items={[
        {
          href: '/accessibility/links',
          text: 'Links'
        },
        {
          href: '/accessibility/tables',
          text: 'Tables'
        }
      ]} />
      <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Interactivity</span>
        <NavigationMenu items={[
          {
            href: '/accessibility/error-messages',
            text: 'Error messages'
          },
          {
            href: '/accessibility/keyboard',
            text: 'Keyboard basics'
          },
          {
            href: '/accessibility/keyboard/tab-navigation',
            text: '- Tab navigation'
          },
          {
            href: '/accessibility/keyboard/focus',
            text: '- Focus'
          },
          {
            href: '/accessibility/keyboard/skip-to-content',
            text: '- Skip to content links'
          },
          {
            href: '/accessibility/keyboard/character-key-shortcuts',
            text: '- Character key shortcuts'
          },
          {
            href: '/accessibility/keyboard/pointer-gestures',
            text: '- Pointer gestures'
          },
        ]} />
      <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Written content</span>
        <NavigationMenu items={[
          {
            href: '/accessibility/inclusive-language',
            text: 'Inclusive language'
          },
        ]} />
        <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Providing alternatives</span>
          <NavigationMenu items={[
            {
              href: '/accessibility/audio-and-video',
              text: 'Audio and video'
            },
            {
              href: '/accessibility/images',
              text: 'Images'
            },
          ]} />
        <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Resources</span>
          <NavigationMenu items={[
            {
              href: '/accessibility/resources',
              text: 'Guidance, tools and further reading'
            }
          ]} />
    </div>
    <div className="govuk-grid-column-three-quarters">
      <h1>
        <span className="caption">Accessibility</span>
          Inclusive language
      </h1>
      <p>As an organisation and in communications with our users, we should write in a way which is clear, compassionate and respectful.</p>



      <h2>Helping everyone</h2>
      <p>When we build government services, we must ensure they’re accessible and inclusive to everyone who needs to use them.</p>
      <p>Inclusive language builds trust and allows us to communicate effectively with our users.</p>
      <p>This guidance is not comprehensive, but aims to provide principles and specific suggestions for writing and talking about diverse groups of people.</p>
      <h2>Writing inclusive content</h2>
      <h3>Age</h3>
        <p>Do:</p>
        <ul>
        <li>only ask for a person’s age if it is needed - for example, if a person must be over 18 to use a service</li>
        <li>only refer to someone’s age if it’s relevant to what you’re writing about</li>
        </ul>

        <p>Do not:</p>
        <ul>
        <li>use age-related descriptors like ‘young’ or ‘old’ - use specific age ranges, such as ‘18-24’ or ‘over 65’ </li>
        </ul>
        <h3>Disability</h3>
        <p>As well as following our <a href="https://ukhomeoffice.github.io/accessibility-posters/">accessible design principles</a>, you should consider how your language is inclusive to people who face different barriers to accessing services.</p>
          <p>Do:</p>
          <ul>
          <li>clearly signpost users to alternative methods of accessing the service and get support if needed</li>
          <li>recognise the variety of barriers in society that can make life harder for people</li>
          <li>use positive and person-centred language, when talking about people with disabilities - such as, people with health conditions or impairments</li>
          </ul>

          <p>Do not:</p>
          <ul>
          <li>use language that implies conditions or disability being a barrier - instead focus on removing barriers that they might face in society</li>
          </ul>
          <h3>Sex, gender and sexuality</h3>
            <p>Do:</p>
            <ul>
            <li>only refer to a person’s sex or gender if relevant and there’s a reason why you’re collecting this data</li>
            <li>allow for flexibility around this information, such as asking for both a person’s sex and their gender, to ensure that the data captured accurately represents the individual and their needs</li>
            <li>allow people to self-describe - use language that reflects how a person refers to themselves</li>
            </ul>
            <h4>Sex</h4>
              <p>Do:</p>
              <ul>
              <li>ask for, or refer to, a person’s sex only when it’s relevant for biological data, not when concerning how a person identifies</li>
              <li>refer to the sex someone was registered with at birth</li>
              <li>provide options other than male and female where possible</li>
              <li>allow people to disclose whether their sex registered at birth is different from their sex at present if you need to understand a persons’ current needs</li>
              </ul>
            <div class="govuk-inset-text">
            The UK currently does not use an X marker for sex on identity documents, meaning that identity documents cannot have a sex other than male or female. <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/919615/euss-interim-guidance-gender-identity-and-sex-markers-on-documents-v1.0-ext.pdf">Current policy</a> states that for Biometric Residence Permits (BRPs) or identity documents, caseworkers will need to contact them to ask for a preference for their identity documentation. If relevant to your service, you should inform users of this when providing an ‘other’ option for questions about their sex.
            </div>
            <h4>Gender</h4>
              <p>Do:</p>
              <ul>
              <li>refer to gender when relevant to how a person identifies, rather than when referring to biological characteristics - for example, if you need this data to understand the needs of users for policing, housing or asylum accommodation purposes</li>
              <li>use gender neutral pronouns - for example, ‘<NAME> has settled status, they have the right to live and work in the UK’</li>
              </ul>
              <p>Do not:</p>
              <ul>
              <li>use language that reinforces harmful stereotypes and assumptions</li>
              </ul><commit_msg>docs: Fix: Correct prop name<commit_after>import { FC, createElement as h } from 'react';
import { Helmet } from 'react-helmet-async';
import { PageProps } from '@not-govuk/app-composer';
import { A, NavigationMenu } from '@not-govuk/components';


export const title = 'Inclusive language';
const description = 'Accessibility guidance for xxx content';
export const section = 'Accessibility';

const Page: FC<PageProps> = ({ location }) => (
  <div className="govuk-grid-row">
    <Helmet>
      <title>{title} - Home Office Design System</title>
      <meta name="description" content={description} />
      <meta name="og:title" content={title} />
      <meta name="og:description" content={description} />
      <meta name="og:article:section" content={section} />
    </Helmet>
    <div className="govuk-grid-column-one-quarter">
    <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Page structure</span>
      <NavigationMenu items={[
        {
          href: '/accessibility/links',
          text: 'Links'
        },
        {
          href: '/accessibility/tables',
          text: 'Tables'
        }
      ]} />
      <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Interactivity</span>
        <NavigationMenu items={[
          {
            href: '/accessibility/error-messages',
            text: 'Error messages'
          },
          {
            href: '/accessibility/keyboard',
            text: 'Keyboard basics'
          },
          {
            href: '/accessibility/keyboard/tab-navigation',
            text: '- Tab navigation'
          },
          {
            href: '/accessibility/keyboard/focus',
            text: '- Focus'
          },
          {
            href: '/accessibility/keyboard/skip-to-content',
            text: '- Skip to content links'
          },
          {
            href: '/accessibility/keyboard/character-key-shortcuts',
            text: '- Character key shortcuts'
          },
          {
            href: '/accessibility/keyboard/pointer-gestures',
            text: '- Pointer gestures'
          },
        ]} />
      <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Written content</span>
        <NavigationMenu items={[
          {
            href: '/accessibility/inclusive-language',
            text: 'Inclusive language'
          },
        ]} />
        <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Providing alternatives</span>
          <NavigationMenu items={[
            {
              href: '/accessibility/audio-and-video',
              text: 'Audio and video'
            },
            {
              href: '/accessibility/images',
              text: 'Images'
            },
          ]} />
        <span className="govuk-caption-m" style={{marginBottom: "1em"}}>Resources</span>
          <NavigationMenu items={[
            {
              href: '/accessibility/resources',
              text: 'Guidance, tools and further reading'
            }
          ]} />
    </div>
    <div className="govuk-grid-column-three-quarters">
      <h1>
        <span className="caption">Accessibility</span>
          Inclusive language
      </h1>
      <p>As an organisation and in communications with our users, we should write in a way which is clear, compassionate and respectful.</p>



      <h2>Helping everyone</h2>
      <p>When we build government services, we must ensure they’re accessible and inclusive to everyone who needs to use them.</p>
      <p>Inclusive language builds trust and allows us to communicate effectively with our users.</p>
      <p>This guidance is not comprehensive, but aims to provide principles and specific suggestions for writing and talking about diverse groups of people.</p>
      <h2>Writing inclusive content</h2>
      <h3>Age</h3>
        <p>Do:</p>
        <ul>
        <li>only ask for a person’s age if it is needed - for example, if a person must be over 18 to use a service</li>
        <li>only refer to someone’s age if it’s relevant to what you’re writing about</li>
        </ul>

        <p>Do not:</p>
        <ul>
        <li>use age-related descriptors like ‘young’ or ‘old’ - use specific age ranges, such as ‘18-24’ or ‘over 65’ </li>
        </ul>
        <h3>Disability</h3>
        <p>As well as following our <a href="https://ukhomeoffice.github.io/accessibility-posters/">accessible design principles</a>, you should consider how your language is inclusive to people who face different barriers to accessing services.</p>
          <p>Do:</p>
          <ul>
          <li>clearly signpost users to alternative methods of accessing the service and get support if needed</li>
          <li>recognise the variety of barriers in society that can make life harder for people</li>
          <li>use positive and person-centred language, when talking about people with disabilities - such as, people with health conditions or impairments</li>
          </ul>

          <p>Do not:</p>
          <ul>
          <li>use language that implies conditions or disability being a barrier - instead focus on removing barriers that they might face in society</li>
          </ul>
          <h3>Sex, gender and sexuality</h3>
            <p>Do:</p>
            <ul>
            <li>only refer to a person’s sex or gender if relevant and there’s a reason why you’re collecting this data</li>
            <li>allow for flexibility around this information, such as asking for both a person’s sex and their gender, to ensure that the data captured accurately represents the individual and their needs</li>
            <li>allow people to self-describe - use language that reflects how a person refers to themselves</li>
            </ul>
            <h4>Sex</h4>
              <p>Do:</p>
              <ul>
              <li>ask for, or refer to, a person’s sex only when it’s relevant for biological data, not when concerning how a person identifies</li>
              <li>refer to the sex someone was registered with at birth</li>
              <li>provide options other than male and female where possible</li>
              <li>allow people to disclose whether their sex registered at birth is different from their sex at present if you need to understand a persons’ current needs</li>
              </ul>
            <div className="govuk-inset-text">
            The UK currently does not use an X marker for sex on identity documents, meaning that identity documents cannot have a sex other than male or female. <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/919615/euss-interim-guidance-gender-identity-and-sex-markers-on-documents-v1.0-ext.pdf">Current policy</a> states that for Biometric Residence Permits (BRPs) or identity documents, caseworkers will need to contact them to ask for a preference for their identity documentation. If relevant to your service, you should inform users of this when providing an ‘other’ option for questions about their sex.
            </div>
            <h4>Gender</h4>
              <p>Do:</p>
              <ul>
              <li>refer to gender when relevant to how a person identifies, rather than when referring to biological characteristics - for example, if you need this data to understand the needs of users for policing, housing or asylum accommodation purposes</li>
              <li>use gender neutral pronouns - for example, ‘<NAME> has settled status, they have the right to live and work in the UK’</li>
              </ul>
              <p>Do not:</p>
              <ul>
              <li>use language that reinforces harmful stereotypes and assumptions</li>
              </ul>
{'fraction_non_alphanumeric': 0.10696857310169823, 'fraction_numerical': 0.004814887110417073, 'mean_word_length': 2.255666172421097, 'pattern_counts': {'":': 0, '<': 261, '<?xml version=': 0, '>': 263, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 18, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7149787', 'n_tokens_mistral': 4063, 'n_tokens_neox': 3949, 'n_words': 1429}