What is the purpose of making 3 priority level by WCAG?
is it like?
- If client not paying extra or if we don't have much time then go for A
- If client paying then or if we have time to make site compatible go for at least AA
- If client paying and needed according to govt. rules then go for AAA
If we are making site then which level we should we try to achieve, or we should do only on client request?
Although i found these definitions on this site but these are confusing for me
• Priority 1: For all users to access the Web content and for Web developers to attain Conformance level “A”, these requirements must be satisfied.
• Priority 2: These requirements should be satisfied by the Web developers so that no group finds it difficult to access the Web content and so as to attain Conformance level “AA”.
• Priority 3: These requirements may be satisfied by the Web developers to facilitate access to Web content for some groups and attain Conformance level “AAA”.
It is certainly true that the more A's the harder it is to achieve, but conversely the more people who are likely to benefit.
Not sure I agree with Adam that you should aim for 100. Since W3C have said 100 is not achievable in some cases, then it could be a waste of client resources to aim for 100. To give an analogy if you were employed to sell services for a client and they provide you with leads, you could aim to sell to 100% of the leads but everyone knows that although theoretically 100% is possible, in the real world it could never be achieved. It is better to set a realistic target.
WCAG 2.0 is divided into three conformance levels (A-AA-AAA) because the success criteria are organised based on the impact they have on design or visual presentation of the pages. The higher the level, the more restraining it becomes on design.
For example, let's take guideline 1.4 (Distinguishable), which is about making it easier for users to see and hear content including separating foreground from background.
As you can see, the more higher we get, the more demanding it becomes and the more pressure it put on how things can be presented in the web page.
As a rule of thumb, success criteria from level A should be invisible or barely noticeable to the interface. On the other hand, level AAA will have such a high impact on design, that even the W3C claims that most organizations will not be able to achieve that level (as the compromises on design will be too important):
Source: http://www.w3.org/TR/WCAG20/#conformance-reqs (WCAG 2.0) - from the W3C
"Note 2: It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content."
Working towards compliance to one conformance level or another in any given project shouldn't have anything to do with what the client pays or doesn't pay. It should always be about making everything you can (within the boundaries of resources and budget of course) to ensure that all users, regardless of disabilities or limitations, can enjoy the content that is provided to the public. And this is especially true when it comes to government content.
The different levels are used to 'grade' a site based on accessibility. You should always aim for the best.
It's like saying "how good is this website out of 100?". You can't say to the client "I'll only aim for a score of 70", you should aim for 100.
Web accessibility helps people with disabilities or elders to use the web. WCAG 2.0 defined 3 levels of accessibility A, AA, and AAA. The main reason of the different levels was to lower the impact of the design of the page, keeping the website accessible but at the same time with a good design quality. Since the level AAA may impact on the design standards like Section 508 in the USA and EN 301549 in Europe require only AA level.
Source: https://www.w3.org/TR/WCAG20/#conformance-reqs
The WCAG documentation explains why there are different levels.