Difference between revisions of "Accessibility"
(Created page with "=Accessibility statement= This system is run by Dizions Ltd. We want as many people as possible to be able to use this website. For example, that means you should be able to...") |
|||
| Line 5: | Line 5: | ||
* zoom in up to 300% without the text spilling off the screen | * zoom in up to 300% without the text spilling off the screen | ||
* navigate most of the website using just a keyboard | * navigate most of the website using just a keyboard | ||
| − | + | *navigate most of the website using speech recognition software | |
| − | + | *listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver) | |
| + | |||
We’ve also made the website text as simple as possible to understand. | We’ve also made the website text as simple as possible to understand. | ||
| + | |||
AbilityNet has advice on making your device easier to use if you have a disability. | AbilityNet has advice on making your device easier to use if you have a disability. | ||
| − | How accessible | + | =How accessible is the system= |
| + | |||
We know some parts of this website are not fully accessible: | We know some parts of this website are not fully accessible: | ||
| − | + | *the text will not reflow in a single column when you change the size of the browser window | |
| − | + | *you cannot modify the line height or spacing of text | |
| − | + | *most older PDF documents are not fully accessible to screen reader software | |
| − | + | *live and recorded video streams may not have captions | |
| − | + | *you cannot skip to the main content when using a screen reader | |
| − | What to do if you cannot access parts of | + | |
| + | =What to do if you cannot access parts of the system= | ||
| + | |||
If you experience difficulties using the system you can contact our support team via: | If you experience difficulties using the system you can contact our support team via: | ||
| − | + | *email support@charitylog.co.uk | |
| − | + | *call 0333 222 5957 | |
| − | + | ||
| − | Reporting accessibility problems with | + | =Reporting accessibility problems with the software= |
| + | |||
We’re always looking to improve the accessibility of our software. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact our support team via: | We’re always looking to improve the accessibility of our software. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact our support team via: | ||
| − | + | *email support@charitylog.co.uk | |
| − | + | *call 0333 222 5957 | |
| − | Enforcement procedure | + | |
| + | =Enforcement procedure= | ||
| + | |||
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 Equality Advisory and Support Service (EASS). | 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 Equality Advisory and Support Service (EASS). | ||
| − | Contacting us by phone | + | |
| + | =Contacting us by phone= | ||
We have an email support service for people who are D/deaf, hearing impaired or have a speech impediment. Use support@dizions.co.uk for support requests. | We have an email support service for people who are D/deaf, hearing impaired or have a speech impediment. Use support@dizions.co.uk for support requests. | ||
| − | Technical information about | + | |
| + | =Technical information about the software's accessibility= | ||
| + | |||
Dizions is committed to making its software accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. | Dizions is committed to making its software accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. | ||
This software is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below. | This software is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below. | ||
| − | Non accessible content | + | =Non accessible content= |
| + | |||
Currently select fields for selecting organisations and people are not accessible. Other non accessible pages can be reported to our support team via: | Currently select fields for selecting organisations and people are not accessible. Other non accessible pages can be reported to our support team via: | ||
| − | email support@charitylog.co.uk | + | *email support@charitylog.co.uk |
| − | call 0333 222 5957 | + | *call 0333 222 5957 |
| − | Non compliance with the accessibility regulations | + | |
| + | =Non compliance with the accessibility regulations= | ||
Some dates highlight in red when overdue and do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). | Some dates highlight in red when overdue and do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). | ||
| + | |||
We plan to add text alternatives for all overdue dates by February 2021. | We plan to add text alternatives for all overdue dates by February 2021. | ||
| − | Navigation and accessing information | + | |
| + | =Navigation and accessing information= | ||
| + | |||
Currently there are no known issues with the navigation of the software. | Currently there are no known issues with the navigation of the software. | ||
Interactive tools and transactions | Interactive tools and transactions | ||
Currently select fields for selecting organisations and people are not accessible. We are currently working on this issue to ensure these fields are fully accessible. We have planned for this to be rectified in our February 2021 release. | Currently select fields for selecting organisations and people are not accessible. We are currently working on this issue to ensure these fields are fully accessible. We have planned for this to be rectified in our February 2021 release. | ||
| − | Live video Webinars | + | |
| + | =Live video Webinars= | ||
| + | |||
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live). | Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live). | ||
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. | We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. | ||
| − | How we tested | + | |
| + | =How we tested the software= | ||
| + | |||
This software undergoes testing via our QA department. We test for accessibility as part of our standard test routines. | This software undergoes testing via our QA department. We test for accessibility as part of our standard test routines. | ||
We work with the Royal College of the blind to do annual testing on essential features of the software. | We work with the Royal College of the blind to do annual testing on essential features of the software. | ||
| − | What we’re doing to improve accessibility | + | |
| + | =What we’re doing to improve accessibility= | ||
| + | |||
We endeavour to ensure that all new features and content of the software are accessible. Any reported accessibility issues are dealt with along with our SLA’s and treated as issues like any other non-functioning areas. | We endeavour to ensure that all new features and content of the software are accessible. Any reported accessibility issues are dealt with along with our SLA’s and treated as issues like any other non-functioning areas. | ||
| + | |||
This statement was prepared on 22 January 2021. It was last updated on 22 January 2021 | This statement was prepared on 22 January 2021. It was last updated on 22 January 2021 | ||
Revision as of 15:42, 22 January 2020
Contents
- 1 Accessibility statement
- 2 How accessible is the system
- 3 What to do if you cannot access parts of the system
- 4 Reporting accessibility problems with the software
- 5 Enforcement procedure
- 6 Contacting us by phone
- 7 Technical information about the software's accessibility
- 8 Non accessible content
- 9 Non compliance with the accessibility regulations
- 10 Navigation and accessing information
- 11 Live video Webinars
- 12 How we tested the software
- 13 What we’re doing to improve accessibility
Accessibility statement
This system is run by Dizions Ltd. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible is the system
We know some parts of this website are not fully accessible:
- the text will not reflow in a single column when you change the size of the browser window
- you cannot modify the line height or spacing of text
- most older PDF documents are not fully accessible to screen reader software
- live and recorded video streams may not have captions
- you cannot skip to the main content when using a screen reader
What to do if you cannot access parts of the system
If you experience difficulties using the system you can contact our support team via:
- email support@charitylog.co.uk
- call 0333 222 5957
Reporting accessibility problems with the software
We’re always looking to improve the accessibility of our software. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact our support team via:
- email support@charitylog.co.uk
- call 0333 222 5957
Enforcement procedure
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 Equality Advisory and Support Service (EASS).
Contacting us by phone
We have an email support service for people who are D/deaf, hearing impaired or have a speech impediment. Use support@dizions.co.uk for support requests.
Technical information about the software's accessibility
Dizions is committed to making its software accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. This software is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non accessible content
Currently select fields for selecting organisations and people are not accessible. Other non accessible pages can be reported to our support team via:
- email support@charitylog.co.uk
- call 0333 222 5957
Non compliance with the accessibility regulations
Some dates highlight in red when overdue and do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all overdue dates by February 2021.
Currently there are no known issues with the navigation of the software. Interactive tools and transactions Currently select fields for selecting organisations and people are not accessible. We are currently working on this issue to ensure these fields are fully accessible. We have planned for this to be rectified in our February 2021 release.
Live video Webinars
Live video streams do not have captions. This fails WCAG 2.1 success criterion 1.2.4 (captions - live). We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
How we tested the software
This software undergoes testing via our QA department. We test for accessibility as part of our standard test routines. We work with the Royal College of the blind to do annual testing on essential features of the software.
What we’re doing to improve accessibility
We endeavour to ensure that all new features and content of the software are accessible. Any reported accessibility issues are dealt with along with our SLA’s and treated as issues like any other non-functioning areas.
This statement was prepared on 22 January 2021. It was last updated on 22 January 2021
