FreshContext Accessibility
FreshContext is working toward accessible public surfaces for the site, demo, and documentation pages. This page describes the current approach and how to report barriers.
Current Approach
The public site is reviewed against WCAG-oriented engineering checks, including semantic page structure, keyboard navigation, focus visibility, readable contrast, mobile layout, and automated axe/html validation.
FreshContext pairs automated checks with manual keyboard and layout review because automated reports alone do not prove that every user experience is accessible.
This page is a trust/readiness note, not a legal conclusion or formal conformance statement.
Last reviewed: May 27, 2026.
Standards Referenced
FreshContext uses public accessibility standards and guidance as engineering references, including WCAG, ADA web accessibility guidance, and EU accessibility materials where relevant.
- W3C Web Content Accessibility Guidelines overview
- ADA.gov web accessibility guidance
- Directive (EU) 2019/882
- EU web accessibility standards and harmonisation note
Known Limitations
The current site is a static public information surface. It does not include account flows, payments, forms, video, audio, or authenticated product dashboards.
Automated accessibility checks do not prove that every user experience is accessible. Manual review and professional accessibility/legal review may still be needed before commercial launch, procurement, or regulated use.
Report An Accessibility Barrier
If you have trouble using a FreshContext public page, contact gimmanuel73@gmail.com.
Please include the page URL, device/browser if known, the assistive technology involved if relevant, and a short description of the issue. Do not include secrets, tokens, private logs, or customer data.