|
|
Posted by 1001 Webs on 11/11/07 13:12
On Nov 11, 1:52 pm, 1001 Webs <1001w...@gmail.com> wrote:
> On Nov 11, 1:39 pm, 1001 Webs <1001w...@gmail.com> wrote:
>
>
>
> > On Nov 11, 12:52 pm, 1001 Webs <1001w...@gmail.com> wrote:
>
> > > On Nov 11, 8:20 am, Spheric <no...@nothanks.yo> wrote:
>
> > > > An ingrate wrote:
> > > > > How old are you Chaddy?
> > > > > My guess is 2+2+2.
>
> > > > > And you have the nerve to claim to be a webmaster ...
> > > > > A kid can do better than you, pathetic troll, and the proof is right
> > > > > at the links above.
>
> > > > > Have a nice day now, Shoddy666
>
> > > > I can certainly belive my eyes. This person has just attacked Chad. It so
> > > > happens that Chad is legally blind and has proofed some of my sites for
> > > > users with disability.
>
> > > Is he blind, really? Now it all makes sense.
>
> > > I am awfully sorry.
>
> > > I didn't know that, no one told me.
>
> > > That makes me a bloody asshole then.
>
> > > Sorry Chaddy, I still don't know why you attacked me in the first
> > > place, but please, accept my apologies.
>
> > > it wasn't at all my intention to make fun of someone with
> > > disabilities.
>
> > > I think I'd better go now, Good-bye everybody.
>
> > One question remains, though.
> > If Chaddy is blind, how come he's doing Flash "presentations"?http://freewebdesign.awardspace.biz/portfolio.php
>
> > Please explain that to this bloody asshole.
> > Either of two, he's not blind or he doesn't have any consideration for
> > real blind people.
>
> Moreover,
> when we try to validate the page at w3.org:http://validator.w3.org/check?uri=http%3A%2F%2Ffreewebdesign.awardspa...
>
> we get:
> This page is not Valid XHTML 1.0 Strict!
> Result: Failed validation, 4 Errors
Furthermore:
Accessibility evaluation results of http://freewebdesign.awardspace.biz/portfolio.php
Detailed accessibility evaluation report
Errors with priority: 3
Checkpoint Description HTML element, attribute Line
4.3 Identify the primary natural language of a document
More information: http://www.w3.org/TR/WCAG10/#gl-abbreviated-and-foreign
HTML, LANG 3
Warnings with priority: 1
Checkpoint Description HTML element, attribute Line
1.3 Until user agents can automatically read aloud the text
equivalent of a visual track, provide an auditory description of the
important information of the visual track of a multimedia
presentation. .
More information: http://www.w3.org/TR/WCAG10/#gl-provide-equivalents
OBJECT, 28
1.4 For any time-based multimedia presentation (e.g., a movie or
animation), synchronize equivalent alternatives (e.g., captions or
auditory descriptions of the visual track) with the presentation. .
More information: http://www.w3.org/TR/WCAG10/#gl-provide-equivalents
OBJECT, 28
2.1 Ensure that all information conveyed with color is also available
without color, for example from context or markup. .
More information: http://www.w3.org/TR/WCAG10/#gl-color
OBJECT, 28
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..
More information: http://www.w3.org/TR/WCAG10/#gl-new-technologies
OBJECT, 28
7.1 Until user agents allow users to control flickering, avoid
causing the screen to flicker.
More information: http://www.w3.org/TR/WCAG10/#gl-movement
OBJECT, 28
8.1 Make programmatic elements such as scripts and applets directly
accessible or compatible with assistive technologies .
More information: http://www.w3.org/TR/WCAG10/#gl-own-interface
OBJECT, 28
4.1 Clearly identify changes in the natural language of a document's
text and any text equivalents (e.g., captions).
More information: http://www.w3.org/TR/WCAG10/#gl-abbreviated-and-foreign
N/A N/A
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.
More information: http://www.w3.org/TR/WCAG10/#gl-new-technologies
N/A N/A
6.2 Ensure that equivalents for dynamic content are updated when the
dynamic content changes.
More information: http://www.w3.org/TR/WCAG10/#gl-new-technologies
N/A N/A
11.4 If, after best efforts, you cannot create an accessible page,
provide a link to an alternative page that uses W3C technologies, is
accessible, has equivalent information (or functionality), and is
updated as often as the inaccessible (original) page.
More information: http://www.w3.org/TR/WCAG10/#gl-use-w3c
N/A N/A
14.1 Use the clearest and simplest language appropriate for a site's
content.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-comprehension
N/A N/A
Warnings with priority: 2
Checkpoint Description HTML element, attribute Line
3.1 When an appropriate markup language exists, use markup rather
than images to convey information
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
OBJECT, 28
3.5 Use header elements to convey document structure and use them
according to specification
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
H1, 11
3.5 Use header elements to convey document structure and use them
according to specification
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
H2, 19
3.5 Use header elements to convey document structure and use them
according to specification
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
P, 20, 21, 23, 29
3.6 Mark up lists and list items properly.
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
UL, 13
7.3 Until user agents allow users to freeze moving content, avoid
movement in pages.
More information: http://www.w3.org/TR/WCAG10/#gl-movement
OBJECT, 28
9.2 Ensure that any element that has its own interface can be
operated in a device-independent manner.
More information: http://www.w3.org/TR/WCAG10/#gl-device-independence
OBJECT, 28
13.1 Clearly identify the target of each link.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
A, 13, 14, 15, 15, 16, 17, 25
2.2 Ensure that foreground and background color combinations provide
sufficient contrast when viewed by someone having color deficits or
when viewed on a black and white screen.
More information: http://www.w3.org/TR/WCAG10/#gl-color
N/A N/A
3.2 Create documents that validate to published formal grammars.
More information: http://www.w3.org/TR/WCAG10/#gl-structure-presentation
N/A N/A
7.5 Until user agents provide the ability to stop auto-redirect, do
not use markup to redirect pages automatically. Instead, configure the
server to perform redirects.
More information: http://www.w3.org/TR/WCAG10/#gl-movement
N/A N/A
11.1 Use W3C technologies when they are available and appropriate for
a task and use the latest versions when supported.
More information: http://www.w3.org/TR/WCAG10/#gl-use-w3c
N/A N/A
12.3 Divide large blocks of information into more manageable groups
where natural and appropriate.
More information: http://www.w3.org/TR/WCAG10/#gl-complex-elements
N/A N/A
13.3 Provide information about the general layout of a site (e.g., a
site map or table of contents).
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
13.4 Use navigation mechanisms in a consistent manner.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
Warnings with priority: 3
Checkpoint Description HTML element, attribute Line
10.5 Until user agents (including assistive technologies) render
adjacent links distinctly, include non-link, printable characters
(surrounded by spaces) between adjacent links.
More information: http://www.w3.org/TR/WCAG10/#gl-interim-accessibility
A, 13, 14, 15, 15, 16, 17, 25
13.6 Group related links, identify the group (for user agents), and,
until user agents do so, provide a way to bypass the group.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
A, 13, 14, 15, 15, 16, 17, 25
4.2 Specify the expansion of each abbreviation or acronym in a
document where it first occurs
More information: http://www.w3.org/TR/WCAG10/#gl-abbreviated-and-foreign
N/A N/A
11.3 Provide information so that users may receive documents
according to their preferences (e.g., language, content type, etc.)
More information: http://www.w3.org/TR/WCAG10/#gl-use-w3c
N/A N/A
13.5 Provide navigation bars to highlight and give access to the
navigation mechanism.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
13.7 If search functions are provided, enable different types of
searches for different skill levels and preferences.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
13.8 Place distinguishing information at the beginning of headings,
paragraphs, lists, etc.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
13.9 Provide information about document collections (i.e., documents
comprising multiple pages.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
13.10 Provide a means to skip over multi-line ASCII art.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-navigation
N/A N/A
14.2 Supplement text with graphic or auditory presentations where
they will facilitate comprehension of the page.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-comprehension
N/A N/A
14.3 Create a style of presentation that is consistent across pages.
More information: http://www.w3.org/TR/WCAG10/#gl-facilitate-comprehension
N/A N/A
Navigation:
[Reply to this message]
|