ASP.Net Control Accessibility

[=?Utf-8?B?TWlrZSBMb2dhbg==?=]

This page: http://msdn2.microsoft.com/en-us/lib...96(VS.80).aspx

at the top says "ASP.NET server controls cannot be used in applications that
must be 100 percent conformant with Web Content Accessibility Guidelines 1.0
(WCAG) priority 1 guidelines. In those cases, you must avoid using the
controls."

It would be nice if the page said what controls cannot ever be 100%. Like
the Menu control can never be 100% because it requires Client script.
--
Mike Logan

[Juan T. Llibre]

re:

Like the Menu control can never be 100% because it requires Client script.

Have you seen the new ASP.NET 2.0 CSS Friendly Control Adapters ?

http://www.asp.net/cssadapters/Default.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:78**********************************@microsof t.com...

This page: http://msdn2.microsoft.com/en-us/lib...96(VS.80).aspx

at the top says "ASP.NET server controls cannot be used in applications that
must be 100 percent conformant with Web Content Accessibility Guidelines 1.0
(WCAG) priority 1 guidelines. In those cases, you must avoid using the
controls."

It would be nice if the page said what controls cannot ever be 100%. Like
the Menu control can never be 100% because it requires Client script.
--
Mike Logan

[Mark Rae]

"Mike Logan" <Mi*******@community.nospamwrote in message
news:50**********************************@microsof t.com...

These adapters still don't make it able to use it without javascript,
correct?

Correct.

[Juan T. Llibre]

Maybe I'm confused, Mike.

My impression has been that the use of Javascript doesn't trangress
the Web Content Accessibility Guidelines 1.0 (WCAG) priority 1 guidelines.

Does it ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:50**********************************@microsof t.com...

Hello Juan,

These adapters still don't make it able to use it without javascript, correct?

I posted something about this awhile ago:

http://msdn.microsoft.com/newsgroups...3-aa42125ed800
--
Mike Logan
"Juan T. Llibre" wrote:

>re:

Like the Menu control can never be 100% because it requires Client script.

Have you seen the new ASP.NET 2.0 CSS Friendly Control Adapters ?

http://www.asp.net/cssadapters/Default.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:78**********************************@microso ft.com...

This page: http://msdn2.microsoft.com/en-us/lib...96(VS.80).aspx

at the top says "ASP.NET server controls cannot be used in applications that
must be 100 percent conformant with Web Content Accessibility Guidelines 1.0
(WCAG) priority 1 guidelines. In those cases, you must avoid using the
controls."

It would be nice if the page said what controls cannot ever be 100%. Like
the Menu control can never be 100% because it requires Client script.
--
Mike Logan

[Juan T. Llibre]

As I read it, all that section requires is that equivalent information
be made available on an alternative accessible page, if the user
has opted for turning off Javascript and that renders the page unusable.

There's no restriction regarding the use of Javascript itself, is there ?
For users who have *not* opted for turning off Javascript, its use is OK, isn't it ?

IOW, if you provide a text equivalent for the Javascript-based menu, it's OK.

That can be achieved by testing for Javascript (set a variable and check for
its presence) and, in the absence for the variable, rendering a text-only menu.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:0D**********************************@microsof t.com...

Not according to Checkpoint 6.3.

http://www.w3.org/TR/WCAG10-TECHS/#tech-scripts

--
Mike Logan
"Juan T. Llibre" wrote:

>Maybe I'm confused, Mike.

My impression has been that the use of Javascript doesn't trangress
the Web Content Accessibility Guidelines 1.0 (WCAG) priority 1 guidelines.

Does it ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:50**********************************@microso ft.com...

Hello Juan,

These adapters still don't make it able to use it without javascript, correct?

I posted something about this awhile ago:

http://msdn.microsoft.com/newsgroups...3-aa42125ed800
--
Mike Logan
"Juan T. Llibre" wrote:

re:
Like the Menu control can never be 100% because it requires Client script.

Have you seen the new ASP.NET 2.0 CSS Friendly Control Adapters ?

http://www.asp.net/cssadapters/Default.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:78**********************************@microso ft.com...
This page: http://msdn2.microsoft.com/en-us/lib...96(VS.80).aspx

at the top says "ASP.NET server controls cannot be used in applications that
must be 100 percent conformant with Web Content Accessibility Guidelines 1.0
(WCAG) priority 1 guidelines. In those cases, you must avoid using the
controls."

It would be nice if the page said what controls cannot ever be 100%. Like
the Menu control can never be 100% because it requires Client script.
--
Mike Logan

[Juan T. Llibre]

Cool. I'm glad our exchange cleared that up.

:-)

I also support your wish that the matrix you want be provided.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:B4**********************************@microsof t.com...

Your right. Which means that controls that require client script to function
are not accessible...and an accessible alternative should be provided. All I
want is for the MS guys to update that page with a matrix of what controls
are "able" (when configured) to adhere to WCAG and 508.

--
Mike Logan

"Juan T. Llibre" wrote:

>As I read it, all that section requires is that equivalent information
be made available on an alternative accessible page, if the user
has opted for turning off Javascript and that renders the page unusable.

There's no restriction regarding the use of Javascript itself, is there ?
For users who have *not* opted for turning off Javascript, its use is OK, isn't it ?

IOW, if you provide a text equivalent for the Javascript-based menu, it's OK.

That can be achieved by testing for Javascript (set a variable and check for
its presence) and, in the absence for the variable, rendering a text-only menu.


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:0D**********************************@microso ft.com...

Not according to Checkpoint 6.3.

http://www.w3.org/TR/WCAG10-TECHS/#tech-scripts

--
Mike Logan
"Juan T. Llibre" wrote:

Maybe I'm confused, Mike.

My impression has been that the use of Javascript doesn't trangress
the Web Content Accessibility Guidelines 1.0 (WCAG) priority 1 guidelines.

Does it ?


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:50**********************************@microso ft.com...
Hello Juan,

These adapters still don't make it able to use it without javascript, correct?

I posted something about this awhile ago:

http://msdn.microsoft.com/newsgroups...3-aa42125ed800
--
Mike Logan
"Juan T. Llibre" wrote:

re:
Like the Menu control can never be 100% because it requires Client script.

Have you seen the new ASP.NET 2.0 CSS Friendly Control Adapters ?

http://www.asp.net/cssadapters/Default.aspx


Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"Mike Logan" <Mi*******@community.nospamwrote in message
news:78**********************************@microso ft.com...
This page: http://msdn2.microsoft.com/en-us/lib...96(VS.80).aspx

at the top says "ASP.NET server controls cannot be used in applications that
must be 100 percent conformant with Web Content Accessibility Guidelines 1.0
(WCAG) priority 1 guidelines. In those cases, you must avoid using the
controls."

It would be nice if the page said what controls cannot ever be 100%. Like
the Menu control can never be 100% because it requires Client script.
--
Mike Logan

[Steven Cheng[MSFT]]

Hi Mike,

I also agree that it is a good idea to provide a more specific list of
accessiblity info of each ASP.NET server control. You are suggested to post
the request in the product feedback center:

http://connect.microsoft.com/feedbac...spx?SiteID=210

In addition, here are some other reference related to web accessibility:

http://support.microsoft.com/kb/819351/en-us

http://support.microsoft.com/kb/823030/

http://msdn2.microsoft.com/en-us/library/ms178233.aspx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

[Steven Cheng[MSFT]]

Thanks for your reply Mike,

The feedback site's submitted request or bug will be imported into our
internal database automatically and the dev team members will be able to
review them. Also, they'll make decision on the plan for any certain
request or bug due to their existing schedule or budget. Anyway, your
feedback and comments are really welcome and appreciated since it is quite
a good resource for us to improve the products.

Thanks again for your posting.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

This posting is provided "AS IS" with no warranties, and confers no rights.