Supporting web accessibility
The Tanaguru team is there to support you at every stage in making your projects of any scale accessible.
The assistance in the implementation of accessibility is carried out at all stages of your projects. Our multidisciplinary team guides you from the web accessibility of your website to the definition of a digital accessibility approach in your organization, we work as closely as possible with your team.
The Tanaguru team is the experience of large accessibility projects with long missions in large organizations.
Support for the implementation of a digital accessibility approach
We support you in the upstream phases of your projects and in the implementation of your digital accessibility approach.
- Support for the implementation and monitoring of the multi-year accessibility plan
- Identify the key actors of the projects
- Identify the needs in training
- Defining realistic goals
- Support for measuring the current level of accessibility of your digital content
- Industrialization of digital accessibility
- Metrics and dashboards implementation
- Support for the choice of a suitable legal reference (RGAA, WCAG, AccessiWeb, Section 508) to meet your regulatory, budgetary or technical constraints.
- Learn more about regulations (European Directive, French Law for a Digital Republic, regulations in the United States…)
Measure the level of accessibility of your website according to the current standards (RGAA, WCAG). To assess the level of accessibility we carry out audits on a sample page or on a purchasing process as part of an e-commerce site.
Our audits are carried out by certified experts with several years of experience. We want our experts and your contacts to speak the same language. This is why we prefer profiles with dual skills (UX designer, Ergonomist, development team, contribution team).
Taking accessibility into account as early as possible in your design phase is an important point. The audit of functional mockups (wireframes) makes it possible to set the first accessibility elements and to check the first page structures and the first formulation elements before the designers’ work.
In a second step, we analyze the mockups on the basis of the designer’s guide written by the DINSIC. We use Tanaguru evaluation grids for this. This allows the entire project to follow anomalies, recommendations and changes in the accessibility score during iterations. These evaluations can also be performed directly in tools such as Invision or Zeplin.
The audit is regularly completed by workshops organized with the teams responsible for design: UI designers, UX designer, ergonomists, business teams, marketing… The goal is to find appropriate solutions to improve accessibility in line with the overall goals of the project.
Technical audit according to the selected legal reference
We carry out two types of audits depending on the maturity of the teams and the projects’ history.
The first common step for audits is to select the pages that make up the audit sample. This selection is made according to the goals of your website, the main features, the frequency of certain pages and a set of mandatory pages (contact, search…)
This audit is carried out on the basis of compliance with accessibility standards (RGAA or WCAG). This type of audit is appropriate for teams that are aware of and trained in accessibility. The audit grid lists all anomalies sorted according to the structure of the RGAA standard. The audit also makes it possible to write the accessibility declaration.
- allows to check the exact conformity to the legal standard;
- allows to write a declaration of conformity.
- Compliance is sorted according to the accessibility standard. This method is often far from the operational mode of the technical teams.
Component audits are more suitable for projects that have not yet started accessibility actions. These audits make it possible to divide the pages of a website into “functional bricks” and make recommendations.
These recommendations can easily be integrated into ticketing tools (Jira, Mantis…) and can be easily shared with development teams. The breakdown into components makes it easier to assign corrections to developers for specific components.