Accessibility Statement
Needs Assessment Portal is committed to providing a digital experience that is accessible to the widest possible audience, regardless of technology or ability.
Our commitment
We aim to follow best practices for accessibility and usability. We design and build the portal so that people with disabilities can perceive, understand, navigate, interact with and contribute to the platform.
Standards and guidelines
- We aim to meet WCAG 2.1 Level AA success criteria where feasible.
- We follow ARIA best practices for dynamic content and component accessibility.
- We apply semantic HTML, proper heading structure, and meaningful link text.
Perceivable
Content is presented with sufficient contrast, scalable text, and alternatives for non-text content (alt text, captions, transcripts). Where applicable we provide captions for videos and text alternatives for images and icons.
Operable
Interactive components are keyboard accessible, focusable and usable with assistive technologies. We avoid time-dependent interactions where possible and provide clear focus indicators and skip links.
Understandable
We use clear language, consistent layouts, and helpful form labels and error messages. Complex flows include guidance and examples to reduce confusion.
Robust
The portal is built with modern, standards-compliant HTML, CSS and ARIA attributes to ensure compatibility with current and future assistive technologies and browsers.
Keyboard navigation
All primary functionality is available from the keyboard. Standard navigation keys, tab order, and ARIA roles are implemented. Focus states are visible and follow a high-contrast style.
- Use Tab / Shift+Tab to move between interactive elements.
- Use Enter or Space to activate buttons and links.
- Use arrow keys where applicable for composite widgets.
Screen reader support
We provide semantic headings, landmarks (header, main, nav, footer), ARIA labels and live region updates for dynamic content. We test common screen readers and work to ensure meaningful reading order.
Forms, errors & validation
Form fields include programmatic labels, helpful placeholders, and descriptive error messages. Errors are announced to assistive technologies and include suggestions for correction.
Visual design & contrast
We use a design system with accessible color palettes and sufficient contrast between text and backgrounds. Where interactive states appear (hover, focus, active) we ensure visual distinction and maintain contrast requirements.
Third-party content & integrations
Some embedded or third-party content (widgets, analytics, iframes) may not fully meet our accessibility standards. We review third-party services for accessibility and document known limitations below.
Testing & monitoring
Accessibility is part of our design and QA cycles. We perform automated checks, manual testing with keyboard and screen readers, and periodic audits to identify regressions and remediation opportunities.
Known limitations
While we strive to be inclusive, there may be areas (rich visualizations, third-party plugins, or legacy content) with accessibility gaps. We document issues, prioritise fixes, and provide alternatives where possible.
Provide feedback or request assistance
If you encounter an accessibility barrier, please contact us and we will respond within a reasonable timeframe.
Reasonable modifications
We will consider requests for reasonable modifications to our services and provide alternatives where appropriate. To request a modification, use the contact details above.