Les tests automatisés dans le cadre de votre approche à 360 degrés des tests Web

Glenda Sims

By Glenda Sims

14 décembre 2012

360-Degree Web Testing: Post 2 of 4

How do you test for web accessibility?  Whether you are testing for WCAG 2.0, 508, or any of the other accessibility standards used internationally, you will benefit from using a mix of manual and automated testing techniques, applied regularly and consistently.

While manual testing can yield detailed and accurate results, the cost of this method is high, and the shelf life of the testing results can be extraordinarily short.

On average, experienced web accessibility experts conducting manual tests spend anywhere from 1 – 3 hours doing a thorough examination of a page for violations of WCAG 2.0.   Factors that affect the length of the review include complexity of the page, number of violations on that page, requests to identify every single violation on every page, and misleading browser and assistive technology bugs.  In addition to discovering each issue, the expert is often asked to clearly explain, in writing, exactly where the problem is located and how to resolve it.

Now imagine a project where the objective is to manually review 100 pages on a specific site.  The client has a modern, dynamic and interactive site that is updated regularly with new content.  The release cycle for infrastructure changes to the site is based on an agile timeline, so changes to the underlying template and code happen as frequently as every 4 weeks.

  • Approximate hours for manual accessibility review for 100 pages = 100-300 hours
  • Potential shelf life of that review – 4 weeks

Clearly this approach is not feasible for most organizations.

So, how do you balance practicality with accuracy?   The smart solution is to use automated accessibility scans to monitor the breadth and depth of your site(s), coupled with focused manual testing on key representative pages.  In other words, use the power of automation as a proactive warning system and use manual testing to confirm that key users paths are truly accessible.

What is the right mix of manual testing (high touch) and automated testing (high tech)?  Based on my experience, the most effective and efficient use of your resources is to employ the 80/20 rule.  80% of your testing effort should be automated and 20% should be manual.  I recommend monthly, automated scans for unambiguous or explicit accessibility issues.  These smart scans will alert you if accessibility testing was skipped during development, or if  obviously inaccessible third party content was added.

What are the top 5 explicit accessibility issues that can be identified with an automated scan?

Accessibility issueCritères de conformité WCAG 2.0508 Paragraph
Images missing alt attributes

1.1.1

(a)

Active images with a null alt attribute

1.1.1

(a)

Form fields missing explicit labels and/or titles

1.1.1

(n)

No title on a web page

2.4.2

(k)

No primary language specified for the web page

3.1.1

Not applicable

Running a monthly scan across your site to identify explicit accessibility issues is one of the very best methods for detecting accessibility problems when you have limited resources.  These monthly scans will help you get your head turned in the right direction so you can focus your detailed manual testing efforts in the smartest way possible.  An approach that combines robust automated testing with select manual testing is an approach that is practical and realistic for organizations to implement.

Remember, what gets measured gets done.  If you don’t monitor the accessibility health of a web site on an ongoing basis, it will decay.

This post is the second in a series on what we call “360 Degree” web testing: the approach that Deque advocates for obtaining the most detailed and accurate sense of a site’s accessibility.

Les articles de cette série sont les suivants :

Si vous recherchez un logiciel d'accessibilité Web pour votre entreprise, téléchargez notre liste de contrôle. Elle vous sera d'une grande aide pour évaluer les différentes solutions logicielles disponibles sur le marché.

Téléchargez dès maintenant la liste de contrôle sur l'accessibilité !

Glenda Sims

Glenda Sims

Glenda Sims est directrice de l'accessibilité de l'information chez Deque, où elle met son expertise et sa passion pour le Web ouvert au service d'organismes publics, d'établissements d'enseignement et d'entreprises de toutes tailles, des petites structures aux grandes sociétés. Glenda est conseillère et cofondatrice d'AIR-University (Accessibility Internet Rally) et d'AccessU. Elle intervient en tant que consultante en accessibilité, membre du jury et formatrice pour Knowbility, une organisation dont la mission est de favoriser l'autonomie des personnes en situation de handicap en promouvant l'accès à des technologies de l'information sans barrières. En 2010, Glenda a coécrit l'ouvrage *InterACT with Web Standards : A holistic approach to Web Design*.

Recevez les articles de blog directement dans votre boîte mail

Pas de bavardages inutiles, mais des informations concrètes sur l'accessibilité, fournies par des experts qualifiés.

Vous acceptez que Deque , utilise et partage des informations conformément à Dequedéclaration de confidentialité. Vous pouvez modifier votre consentement à tout moment en nous contactant.

En savoir plus sur ce sujet

Deque named a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility 

Logo de Deque
October 9, 2026 By Deque Systems

Deque has been recognized as a Leader in the 2026 Gartner® Magic Quadrant™ for Digital Accessibility!

Lire l'article
Abstract depiction of a chart with four vertical stripes, increasing in height from left to right, colored purple, red, yellow, and green

How to test MCP Apps for accessibility, and why it matters

Harris Schneiderman
October 1, 2026 By Harris Schneiderman

MCP Apps are still new enough that whatever approaches we can establish now will be the ones that stick over the long term. Which means if we can get accessibility right at this stage, it will stay right as the ecosystem grows. This is how we can avoid introducing the same problems we've had to deal with across the rest of the web for so long.

Lire l'article
Example of an interactive UI using MCP Apps, depicting a weather chatbot and a question about weather in San Francisco