[Athen] Section 508 revised and javascript requirement ...

[Terrill Thompson]

Hi Nicaise, 

Scripting on the web presents a tricky problem. As web pages become more like rich, interactive applications rather than static documents, scripting plays a key role in making that interactivity possible. Under WCAG 1.0, particularly the early years, we could assume the position that scripts should only be used as an enhancement to content that was otherwise accessible as static HTML (known as "progressive enhancement" or "graceful degradation" depending on how you looked the problem). Today, it's not so easy to assume that position since many web applications are necessarily dependent on scripting for their core functionality.    

Given this reality, WCAG 2.0 doesn't assume as hard a line against scripting as WCAG 1.0 did. The goal is no longer to bypass scripts, it's to ensure their accessibility. I think the most relevant WCAG 2.0 success criterion is 4.1.2, which is a Level A success criterion (the highest level):  

<quote>
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
</quote>

This is where ARIA comes in (Accessible Rich Internet Applications). ARIA is another W3C specification that  documents the techniques for marking up web pages so that these interactive components can be made accessible, especially to assistive technology users. 

So that's the WCAG 2.0 position. As the Access Board works on updating the Section 508 standards, it's informed by WCAG 2.0, and by this final report that was painstakingly drafted and presented to the Access Board by the Telecommunications and Electronic and Information Technology Advisory Committee (TEITAC): 

http://www.access-board.gov/sec508/refresh/report/

The TEITAC assumes a similar position to that of WCAG 2.0, that "For all user interface components, including form elements and those generated by scripts, the name, role, states, properties, and values must be PROGRAMMATICALLY DETERMINABLE."

All that said, even if the standards allow scripts I think we should still recommend that web developers practice progress enhancement (or graceful degradation). WebAIM's recent screen reader survey results found that 10.4% of screen reader users disable Javascript in their browsers, and 16.4% haven't upgraded their assistive technologies at least within the last year. That amounts to a lot of people who will be impacted by Javascript-dependent web pages, and even more whose assistive technologies aren't current enough to support ARIA techniques: 

http://webaim.org/blog/screen-reader-user-survey-results/


Hope that helps. 

Terry


Terrill Thompson
Technology Accessibility Specialist
DO-IT, Accessible Technology
UW Technology Services
University of Washington
tft at u.washington.edu
206/221-4168


-----Original Message-----
From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org] On Behalf Of Nicaise D
Sent: Sunday, November 01, 2009 2:03 PM
To: 'Access Technology Higher Education Network'
Subject: Re: [Athen] Section 508 revised and javascript requirement ...

How about JavaScript and wcag2.0--  even though section 508 requires that a
page be functional including any scripted interactive content on that page,
and I believe this was in-line with wcag1.0 at that time; is wcag2.0 still
saying that or not? In other words, I am seeking guidance here with regards
to what to do when I am evaluating a javascripted page. Should I continue to
check for what happens when script is turned off and on or should I go and
evaluated with only script turned on? Is this still the case under wcag2.0?

Thanks in advance for your assistance and guidance on this.

Nicaise D


-----Original Message-----
From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org] On
Behalf Of Ron Stewart
Sent: Sunday, November 01, 2009 12:52 PM
To: 'Access Technology Higher Education Network'
Subject: Re: [Athen] Section 508 revised and javascript requirement ...

Currently the proposed standards are under review by the Access Board and
other relevant federal agencies.  As I understand it we should see the
request for public comment posted in the federal register in the next few
months.  Even when this starts it could be a year of two before they replace
the current standards, if they do.

Ron Stewart

-----Original Message-----
From: athen-bounces at athenpro.org [mailto:athen-bounces at athenpro.org] On
Behalf Of Nicaise D
Sent: Sunday, November 01, 2009 12:25 PM
To: 'Access Technology Higher Education Network'
Subject: [Athen] Section 508 revised and javascript requirement ...

Hi everyone,

Has section 508 been refreshed and have these revisions gone into effect? If
yes could somebody tell me where to find the revised section 508 standards?
Everywhere I have looked so far has pointed me toward the section 508 we've
always known. Also what is the new requirement on javascript? Is it still
the test that nothing should be lost or disrupted whether javascript is
turned on or off or javascrip is no longer required to be turned off perhaps
due to technology having caught up? Lastly does wcagt 2.0 have an exact
position on that?
Any help or direction anybody could provide would be greatly appreciated.
Thanks,

Nicaise D


_______________________________________________
Athen mailing list
Athen at athenpro.org
http://athenpro.org/mailman/listinfo/athen_athenpro.org


_______________________________________________
Athen mailing list
Athen at athenpro.org
http://athenpro.org/mailman/listinfo/athen_athenpro.org


_______________________________________________
Athen mailing list
Athen at athenpro.org
http://athenpro.org/mailman/listinfo/athen_athenpro.org