partsERP/templates/_page_accessibility_statement.html

{% extends 'layout.html' %}

{% block title %}{{ model.title }}{% endblock %}

{% block page_body %}
    <!-- Include Stylesheet -->
    <link rel="stylesheet" href="{{ url_for('static', filename='css/services.css') }}">
    
    <!-- HTML content -->
    <div class="{{ model.FLAG_CARD }} {{ model.FLAG_COLUMN }}">
        <h4>Accessibility statement for {{ model.NAME_COMPANY }}</h4>
        <!--
            [Note: you can have a single accessibility statement that covers multiple domains, or a separate statement for each domain or subdomain. As long as the user can access relevant accessibility information easily from any page on your website.

            For mobile apps also include the application’s version information and publication date.

            This wording is legally required and must not be changed.]
        -->
        <p>This accessibility statement applies to the public website of {{ model.NAME_COMPANY }}.</p>
        <!--
            [Note: use this section to make a brief, general statement about what the website allows disabled users to do. Base it on the evaluation covered in detail in the ‘Technical information about this website’s accessibility’ section.

            It must be specific to your own website. If you’re not confident that something is accurate, leave it out. If you’re not confident enough to say anything specific here, leave this section out completely.]
        -->
        <p>This website is run by {{ model.NAME_COMPANY }}. We want as many people as possible to be able to use this website. For example, that means you should be able to:
            <ul>
                <li>zoom in up to 400% without the text spilling off the screen</li>
                <li>navigate most of the website using just a keyboard or speech recognition software</li>
                <li>listen to most of the website using a screen reader (including the most recent versions of NVDA and TalkBack)</li>
                <li>We've also made the website text as simple as possible to understand.</li>
            
            <a href="https://mcmw.abilitynet.org.uk/">AbilityNet</a> has advice on making your device easier to use if you have a disability.
        </p>

        <h5>How accessible this website is</h5>
        <!--
            [Note: use this section to provide a summary of accessibility issues that a disabled user can act on - for example, avoid a particular section of the website, or request an alternative version rather than waste time trying to make it work with their assistive technology. Try to list in order of most impact to least impact.]
        -->
        <p>We know some parts of this website are not fully accessible:
            <ul>
                <li>you cannot modify the line height or spacing of text</li>
            </ul>
        </p>
        
        <h5>Feedback and contact information</h5>
        <p>If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: {{ model.app.MAIL_CONTACT_PUBLIC }} or complete our Contact Us form.

            If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
            {% set block_id = 'button_get_in_touch' %}
            {% include '_shared.html' %}
            We’ll consider your request and get back to you in 7 days.

            <!-- If you cannot view the map on our ‘contact us’ page, email us for directions. -->
        </p>
        
        <h5>Enforcement procedure</h5>
        <p>The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the <a href="https://www.equalityadvisoryservice.com/">Equality Advisory and Support Service (EASS).</a>
        </p>
        <!--
            [Note: if your organisation is based in Northern Ireland, refer users who want to complain to the Equality Commission for Northern Ireland (ECNI) instead of the EASS and EHRC.

            You must link to either the EASS or ECNI websites.]
        -->
        
        
        <h4>Technical information about this website’s accessibility</h4>
        <!--
            [Note: this wording is legally required and must not be changed.]
        -->
        <p>{{ model.NAME_COMPANY }} is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
        </p>
        
        <h5>Compliance status</h5>
        <p>The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
        </p>
        <!--
            [Note: say that the website is fully compliant if the website meets the Web Content Accessibility Guidelines (WCAG) [2.1 or 2.2] AA standard in full.

            Say that it’s partially compliant if it meets most requirements of the WCAG [2.1 or 2.2] AA standard.

            If it does not meet most requirements of the WCAG [2.1 or 2.2] AA standard, say that it’s not compliant.

            If your website is either partially compliant or not compliant with the WCAG [2.1 or 2.2] AA standard, you’ll need to explain why. This will be due to one or both of the following:
            <ul>
                <li>non-compliances - this means the content in question is in scope of the regulations, but there’s an accessibility problem with it</li>
                <li>an exemption - this means the inaccessible content is out of scope of the regulations, or it’d be a disproportionate burden for you to make it accessible</li>
            </ul>
            There’s a legally required way of expressing the compliance status of your website, so do not change it. Choose one of the options below, for example (a), (b) or (c), and delete those not applicable.
        -->
        <p><!-- [Select (a) only if all requirements of the technical specification are fully met without exceptions for WCAG 2.1 or WCAG 2.2.] -->

            (a) This website is fully compliant with the <!--[Web Content Accessibility Guidelines version 2.1 AA standard or -->Web Content Accessibility Guidelines version 2.2 AA standard.
            <!-- 
            [Select (b) if most requirements of the technical specification are met, but with some exceptions. This means not yet fully compliant and that the necessary measures are to be taken in order to reach full compliance.]
            
            (b) This website is partially compliant with the [Web Content Accessibility Guidelines version 2.1 AA standard or Web Content Accessibility Guidelines version 2.2 AA standard], due to [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.
            
            [Select (c) if most requirements of the technical specification are not met.]
            
            (c) This website is not compliant with the [Web Content Accessibility Guidelines version 2.1 AA standard or Web Content Accessibility Guidelines version 2.2 AA standard]. The [insert one of the following: ‘non-compliances’, ‘exemptions’ or ‘non-compliances and exemptions’] are listed below.
            -->
        </p>
        
        <!-- 
        <h4>Non-accessible content</h4>
        <!--
            [Note: if the website is fully compliant with the standard, you can leave the ‘Non-accessible content’ section out.

            Otherwise, do not change the ‘Non-accessible content’ heading or the ‘The content listed below is non-accessible for the following reasons’ sentence - they’re legally required.

            Do not change the ‘Non-compliance with the accessibility regulations’, ‘Disproportionate burden’ and ‘Content that’s not within the scope of the accessibility regulations’ subheadings: they’re also legally required.

            But if you need to list a lot of problems, you can break these subsections up with further subheadings - for example, ‘Navigation and accessing information’ or ‘Interactive tools and transactions’.]
        --
        <p>The content listed below is non-accessible for the following reasons.
        </p>

        <h5>Non-compliance with the accessibility regulations</h5>
        <!--
            [Note: In this subsection, list:
            <ul>
                <li>accessibility problems</li>
                <li>which of the WCAG success criteria the problem fails on</li>
                <li>when you plan to fix the problem</li>
            </ul>
            Do not include any problems where you’re claiming disproportionate burden, or where the problem is outside the scope of the accessibility regulations (those should go in the subsections below).

            These are examples only. Your statement must be specific to your website.]
        --
        <p>Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

            We plan to add text alternatives for all images by September 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.
        </p>

        <h5>Disproportionate burden</h5>
        <!--
            [Note: in this subsection list accessibility problems you’re claiming would be a disproportionate burden to fix.

            You must carry out an assessment before claiming disproportionate burden.

            Bear in mind that something which is a disproportionate burden now will not necessarily be a disproportionate burden forever. If the circumstances change, your ability to claim disproportionate burden may change too.

            These are examples only. Your statement should be specific to your website.]
        --
        <p><strong>Navigation and accessing information</strong>
            There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option).
            
            It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
            
            It’s not possible for users to change text size without some of the content overlapping.
            
            We’ve assessed the cost of fixing the issues with navigation and accessing information. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in [rough timing].
        </p>

        <h5>Content that’s not within the scope of the accessibility regulations</h5>
        <!--
            [Note: in this subsection list accessibility problems that fall outside the scope of the accessibility regulations.]
        --
        <p><strong>PDFs and other documents</strong>
            The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document].
            
            Any new PDFs or Word documents we publish will meet accessibility standards.
            
            <strong>Live video</strong>
            We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
        </p>
        -->

        <!--
        <h4>What we’re doing to improve accessibility</h4>
        <!--
            [Note: publishing an accessibility roadmap is optional. It’s a good idea to publish one if you want to be specific about the order you’re planning to tackle accessibility issues, and there’s no space to do so in the accessibility statement itself.]
        --
        <p>Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.
        </p>
        -->

        <h4>Preparation of this accessibility statement</h4>
        <!--
            [Note: the wording about when the statement was prepared and reviewed is required.

            It is recommended that an audit be carried out following a substantial revision to your website. The statement must also be updated.

            The statement must be reviewed at least once a year, even if there have not been significant changes to the website. Include the date of the last review.]
        -->
        <p>This statement was prepared on 30/04/2024<!--[date when it was first published]-->. It was last reviewed on 30/04/2024<!--[date when it was last reviewed]-->.

            This website was last tested on 30/04/2024 against the WCAG 2.2 AA standard.
        </p>
        <!--
            [Note: describe how you tested the website to write this statement - such as a self-assessment done by the website team or an assessment carried out by a third party.]
        -->
        <p>The test was carried out by <!--[add name of organisation that carried out test, or indicate that you did your own testing]-->{{ model.NAME_COMPANY }}. All pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.</p>
        <!--
            [Note: publishing the test report is optional but doing so may allow you to make your accessibility statement shorter and more focused.]
            https://www.w3.org/WAI/eval/report-tool/#/
        -->
        <p>You can read the full accessibility test report {{ url_for('accessibility_report') }}.</p>
    </div>

    <!-- Include JavaScript -->
    <script src="{{ url_for('static', filename='js/accessibility_statement.js') }}"></script>

    <script>
        var hashPageCurrent = "{{ model.HASH_PAGE_ACCESSIBILITY_STATEMENT }}";
        
        $(document).ready(function() {
            hookupPageAccessibilityStatement();
        });
    </script>
{% endblock %}