Perceivable
Text has strong contrast, images use meaningful alternative text where needed, decorative images use empty alt text and tables include captions.
Accessibility statement
NexaTech is a fictional educational prototype. The site has been designed with WCAG 2.1 principles in mind, but it does not claim full WCAG conformance without a comprehensive independent audit.
Commitment and approach
The prototype aims to support people using keyboards, touch screens, zoomed layouts, screen readers and standard browser settings.
Operable
Navigation, forms, links, details controls and the skip link are keyboard accessible with visible focus indicators.
Understandable
Pages use descriptive titles, one main heading, consistent navigation, clear labels and plain-language prototype notices.
Robust
The site uses semantic HTML landmarks, native controls and limited ARIA so content remains understandable across browsers and assistive technology.
Accessibility features implemented
The features below are implemented across the website unless a page does not need that feature.
- Skip-to-main-content link at the start of each page.
- Semantic header, navigation, main and footer landmarks.
- One clear H1 per page with logical H2 and H3 structure.
- Descriptive page titles and meta descriptions.
- Visible labels for every form field and helpful field instructions.
- Native form validation for required text, email, select, checkbox and number controls.
- Highly visible focus indicators using CSS outline and shadow tokens.
- Responsive layouts that reflow product cards, footer columns and tables.
- Accessible FAQ components using native details and summary elements.
- Tables with captions, row headers and column headers.
- Reduced-motion media query to minimise transitions for users who request it.
- No autoplaying video, flashing content, carousels or keyboard traps.
Supported interaction methods
The prototype is intended to work with mouse, touch, keyboard and common assistive technology browsing modes.
| Interaction method | Implemented support | Evidence to capture |
|---|---|---|
| Keyboard | Links, forms, summary controls and skip link can receive focus and be activated. | Screenshot of focus ring on navigation and contact form. |
| Touch | Buttons and links use minimum practical heights and layouts stack on small screens. | Mobile screenshot at approximately 375 px width. |
| Zoom | Content uses responsive widths, no fixed page width and tables scroll horizontally when needed. | Browser screenshot at 200 percent zoom. |
| Screen-reader structure | Semantic landmarks, headings, form labels, table headers and descriptive links are used. | Heading and landmarks output from a browser or accessibility tool. |
Testing approach and known limitations
The supporting documents include a structured test plan and accessibility evidence guide for the academic report.
Testing approach
Manual checks should include keyboard navigation, skip link activation, visible focus, page zoom, mobile widths, form labels, colour contrast and WAVE or aXe review.
Known limitations
No full screen-reader audit or real-user accessibility test has been completed inside the static prototype. Any tool results should be recorded honestly in the report.
Report an issue
Use the contact form and select accessibility feedback. Submit test information only, because this page is not connected to a real support service.