Web Accessibility Initiative (WAI) - Checkpoints

Web Accessibility Initiative (WAI) - Checkpoints

  
Desde do ano de 2007 a resolução do Conselho de Ministros 155/2007, de 2 de Outubro de 2007, estabelece os requisitos mínimos de acessibilidade que devem respeitar as páginas Internet do Governo, serviços e organismos públicos da Administração Central, adoptando os níveis de conformidade das directrizes sobre a acessibilidade do conteúdo desenvolvidas pelo World Wide Web Consortium (W3C).


Em anexo, as lista de checkpoints da WAI.

http://www.w3.org/WAI/


(Portugal)

Web Content Accessibility Guidelines (WCAG) 2.0

http://www.w3.org/TR/WCAG20/


Hi Ricardo

Thanks for this info.

Please check the following technical note:

Accessible Apps with OutSystems & WCAG 2.0
This document explains how to make web content accessible to people with disabilities, using the Agile Platform. This technical note is intended for OutSystems developers who need to create web business applications with Compliance Level “A”, according with the W3C Web Content Accessibility Guidelines 2.0 (WCAG20), thus satisfying all the Priority 1 checkpoints.BTW, we continue improving the platform in order to reduce the effort needed to deliver WCAG Level A compliant apps.

Regards,
António




This is very useful but I have recently been asked about compliance with Level Double-A which is mandatory for UK public sector. This requires satisfying Priority 2 checkpoints as well as Priority 1. Can you make a statement about that? Can you seeing anything in the Priority 2 list that could not be supported?

Doug Michael
Jumar Solutions
Hi,

After have read your post we looked into Level AA guidelines and it turned out that applications developed in the Agile Platform are, in fact, also conform with Level AA. Why? Well, these guidelines are mainly focused on improving the Web pages content displayed to the end-user and, for that, the Agile Platform provides you with all necessary tools to achieve Level AA conformity.

Best regards

Jaime Vasconcelos

P.S.: We have updated the former "Accessible Apps with OutSystems & WCAG 2.0" technical note to include Level AA information.
You may find the document here: http://www.outsystems.com/community/download.aspx?DocumentId=123


Hi Jaime,

As you may now the present legislation for web content accessibility, in the majority of Europe, says that the websites should follow the WCAG1.0 guidelines and not the W3C newer version of these same guidelines. Nevertheless I give my congrats to OutSystems for taking this issue as a concern and as a work item.

This said I have two questions for you:
1. Why TotalValidator when there are several tools that are much more easy to use, accurate and used as reference in much more studies? TAW3 (that auto evaluates an entire website against WCAG1.0 and evaluates in a single-page manner against WCAG2.0) and Sortsite (that auto evaluates an entire website against WCAG1.0, WCAG2.0 and Section508) are some examples of these other tools.

2. What's your opinion and what's the OutSystems stand on report such as the APDSI eBusiness Group accessibility report (http://www.apdsi.pt/main.php?srvacr=pages_167&mode=public&template=frontoffice&lang=pt&layout=layout&id_page=271) that claims that the reality of the Web in Portugal is very worrying in terms of Web Content Accessibility?

Well done for looking into this and making the new version of the document available so quickly. Just one small point: on the web page where you download the document you have this text:

"This document explains how to make web content accessible to people with disabilities, using the Agile Platform. This technical note is intended for OutSystems developers who need to create web business applications with Compliance Level A and Level AA, according with the W3C Web Content Accessibility Guidelines 2.0 (WCAG20), thus satisfying all the Priority 1 checkpoints."

I think you should say at the end "... thus satisfying all the Priority 1 and Priority 2 checkpoints."

Thanks
Doug

Hi,

We choose to work against WCAG 2.0 validation, which we believe is going to be the next step in accessibility requirements; it is more detailed and comprehensive than WCAG 1.0.

Concerning the validation tool, we used TotalValidator because we already gave support to a few clients that were developing applications with accessibility requirements, and this happened to be the required validation tool for them.

Regarding WCAG validation tools, no validation tool is perfect and a final human validation is always required. Nevertheless, we did consider your suggested tools and looked into them. Since TAW3’s support for WCAG 2.0 is still in beta we decided to give priority to the SortSite tool. It did find a small number of additional glitches which we will take into account by reviewing the WCAG 2.0 technical note and the sample accessibility OML.

Regarding your second question we don’t really have an official stand on these statistics. Nevertheless we are committed to promote and support accessible applications in the Agile Platform.

Kind regards

jaime vasconcelos