The PROACT app is intended for those with the skills and knowledge in the area of AI medical scan analysis, and as such our app will not be accessible to all only to those trained to use the tools. However, where possible, we endeavour to support being able to:
- Use different screen sizes
- Get alt text for images
- Correct content sequencing
- Consistent navigation
- Appropriate labels
- Resize text
- No content that relies solely on sensory characteristics of components such asshape, size, visual location, orientation, or sound.
- Descriptive links
- Heading hierarchies for content pages
- Image/Graph captions, transcriptions and audio descriptions in content pages
- Use any content types or features that have been optimised such as accordions, slideshows, tables and tabs.
- Use of Web Rotor to navigate pages
We aim for no restrictions for:
- Deaf users
- Limited hearing users
- Non-verbal users
- Limited manipulation users
- Limited reach and strength users
- Cognitive user group
There are some restrictions for:
- Userswithout vision
- Users with limited vision
- Users without perception of colour
Whilst we have endeavoured to ensure the accessibility of our app, there are some known limitations. Both Proact and MIME applications are partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to ‘the non compliances’ listed below.
- Some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. WCAG 2.1 1.3.1 (Info and Relationships).
- Some link text is duplicated with a page (WCAG 2.1 2.4.4: Link Purpose (In Context)
- Some tables need captions. WCAG 2.1 1.3.1 (Info and Relationships).
- Images on some pages do not always have suitable image descriptions. WCAG 22.214.171.124 (Non text Content).
- Colour contrast issues on some pages. 1.4.3: Contrast (Minimum)
- Pages display completely at 125%, but no larger without right-hand side overspill.WCAG 2.1 1.4.4: Resize Text
- PDFs and other downloadable documents may not always be accessible.
What we’re doing to improve accessibility
- We strive to make sure our use of navigation, images, graphs, slideshows,documents and tables meets accessibility standards.
- We will work to address issuesraised in accessibility audits.
- We aim to introduce automated checks into the development process.
- We listen to user feedback.
Feedback and contact information
Reporting accessibility problems with this application
We’re always looking to improve the ac cessibility of this application. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us.