appYaccess · RGAA software
Assess your pages’ accessibility with software built around the RGAA. Automate a large proportion of checks, identify what needs attention and run your checks again after each change. Your teams save time and work with structured, reproducible results.
Activate it on its own or with appYuser and appYplanet.
Your teams have what they need to act
Results your teams and service providers can put to use.
What changes for you
Your results become a shared basis for assessing, fixing and checking changes to your site.
Automate a large proportion of checks and focus human work on the points that require judgement or validation.
Results by page and criterion, identified instances of non-compliance and validations still to complete.
Deterministic checks follow the RGAA tests. With the same content, scope, environment and version, they produce the same results.
Run the checks again after a fix or a deployment. Track non-compliance and identify regressions within the assessed scope.
Pages assessed, results, instances of non-compliance and points still to validate: the information is structured to make it easier to prepare and update your accessibility statement, once the necessary validations have been completed.
Understand what to do
A useful result tells you what to check, where to act and how to verify the fix. appYaccess structures the information to help your teams move the work forward.
Educational examples created to illustrate the RGAA method using common accessibility issues.
Finding. On a contact page, an input field has no associated label. Visitors need to understand what information to enter.
Fix. The team associates a clear label with the field and checks that it accurately describes its purpose.
Verification. After the fix, the check is run again on the page. The user journey is also reviewed in context.
References: RGAA 11.1 and 11.2.
Finding. In this example, regular text at 16 px uses #949494 on a white background. Its calculated contrast is approximately 3.03:1, below the applicable 4.5:1 threshold.
Fix. With #595959 on the same background, the calculated ratio reaches approximately 7.00:1.
Verification. Contrast is checked again after the fix and after subsequent changes to the page.
Reference: RGAA 3.2.
With appYaccess, criteria, affected elements and validations still to complete provide a shared basis for your work. You organise fixes and run the checks again within a defined scope.
Sources: RGAA criteria and tests (in French) · minimum contrast, W3C.
With RUM*, you gain context: the pages viewed, the journeys taken and the difficulties encountered. Cross-reference this usage data with your check results to organise fixes more effectively.
* RUM (Real User Monitoring): measurement of visitors’ actual experience on your site.
Traffic complements the analysis. A critical barrier remains a priority, even on a page with few visits.
Criteria, tests and their results form part of a documented approach, with the human validations still to complete.
The tag collects real usage data. The scope of the checks is defined for your assessment.
Identify the pages and journeys to assess. Usage data informs this choice, in line with the RGAA sampling method.
Find the criteria assessed, the elements concerned and the points still to complete, so you can work from a shared basis.
Verify fixes and compare assessments within a controlled scope as your site changes.
Automate your RGAA checks and monitor accessibility over time.
Can be used on its own.
Explore digital experience and its links with your conversions in more detail.
Explore digital experience →Compare your improvements with changes in your site’s environmental impacts.
Explore impact measurement →Yes. You can activate appYaccess on its own, then add appYuser to explore digital experience and conversions in more detail, or appYplanet to measure environmental impacts.
appYaccess automates the checks that can be automated and structures the results. Tests that require human judgement remain identified for completion. Partial automated results do not, on their own, constitute a complete compliance assessment.
Yes. appYaccess automates a large proportion of checks and structures the results for your teams. You define the pages to assess, address the issues and complete the necessary validations. The results can also provide a shared basis for working with your technical service provider or accessibility lead.
Run the checks again on the pages concerned and compare results under controlled conditions. Repeating the checks allows you to verify the effect of a fix and identify regressions across versions.
Structured results inform its preparation: the assessed scope, results and instances of non-compliance. To finalise it, you need to complete the necessary validations and information specific to your organisation, in accordance with the accessibility statement framework.
The tag collects real usage data without cookies. This information provides context for assessments and prioritisation. Installation takes around five minutes when you have the necessary access to the site or its tag manager.
Explore the links between accessibility, user experience and conversions, then plan your assessments and budget. These resources are available in French.
Organise assessments with software and your team’s skills.
Who can carry out an RGAA audit?Understand the costs and how appYaccess supports recurring checks.
RGAA audit costs and ongoing monitoringVerify fixes and monitor accessibility across versions.
How to maintain compliance over timeDiscover the checks, actionable results and how to prepare your statement in a demo.