[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev]

From: Keith Bowes
Subject: Re: [Lynx-dev]
Date: Sun, 4 Dec 2011 02:22:15 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

Je 2011-Dec-01 je 13:12, Krzysztof ┼╗elechowski skribis:
> WCAG <> does not mention stylesheets at
> all, so I am not sure what you are talking about.

I'll have to check that out.  It seems like an odd omission being that
it's a basic principle of web accessibility to be able to view a
web page, regardless of device or user agent.

I did skim over it recently and I was shocked about how short it was.  I
remember everyone talking about how massive version 2.0 was when it was
being drafted.  I suppose that caused them to leave some common-sense
things out.

WGAG 1.0 did have such a provision.  Copied from the spec:
"Guideline 6. Ensure that pages featuring new technologies transform gracefully.
Next guideline: 7 Previous guideline: 5 Go to contents
Ensure that pages are accessible even when newer technologies are not supported 
or are turned off.

Although content developers are encouraged to use new technologies that solve 
problems raised by existing technologies, they should know how to make their 
pages still work with older browsers and people who choose to turn off features.

6.1 Organize documents so they may be read without style sheets. For example, 
when an HTML document is rendered without associated style sheets, it must 
still be possible to read the document. [Priority 1]
    When content is organized logically, it will be rendered in a meaningful 
order when style sheets are turned off or not supported.
    Techniques for checkpoint 6.1
6.2 Ensure that equivalents for dynamic content are updated when the dynamic 
content changes. [Priority 1]
    Techniques for checkpoint 6.2
6.3 Ensure that pages are usable when scripts, applets, or other programmatic 
objects are turned off or not supported. If this is not possible, provide 
equivalent information on an alternative accessible page. [Priority 1]
    For example, ensure that links that trigger scripts work when scripts are 
turned off or not supported (e.g., do not use "javascript:" as the link 
target). If it is not possible to make the page usable without scripts, provide 
a text equivalent with the NOSCRIPT element, or use a server-side script 
instead of a client-side script, or provide an alternative accessible page as 
per checkpoint 11.4. Refer also to guideline 1. 
    Techniques for checkpoint 6.3
6.4 For scripts and applets, ensure that event handlers are input 
device-independent. [Priority 2]
    Refer to the definition of device independence.
    Techniques for checkpoint 6.4
6.5 Ensure that dynamic content is accessible or provide an alternative 
presentation or page. [Priority 2]
    For example, in HTML, use NOFRAMES at the end of each frameset. For some 
applications, server-side scripts may be more accessible than client-side 
    Techniques for checkpoint 6.5"

Looking at WCAG 2.0, it seems to be more about "principles" than
"guidelines."  I suppose the disadvantage is that people can say that
it's not mentioned explicitly, so it doesn't apply (ignoring that it's
against the principle, regardless of whether it's mentioned explicitly
or not).  Being sure not to confuse users and that content is readable
are two of the "principles"; if a browser doesn't support stylesheets or
a certain stylesheet technology or the user has turned it off, and that
technology is required to view the webpage, it obviously goes against
those principles.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]