Skip to content

Commit f220c8c

Browse files
authored
Add However before Because
1 parent 4a56d49 commit f220c8c

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

introduction.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,7 @@ Although WCAG2ICT covers a wide range of issues, it is not able to address all t
2828

2929
While WCAG 2 was designed to be technology neutral, it assumes the presence of a “user agent” such as a browser, media player, or assistive technology that is used as a means to access web content. As a result, the application of WCAG 2 to documents and software in non-web contexts necessitates some interpretation in order to determine how the intent of each WCAG 2 success criterion could be met in these different contexts of use. Therefore, the bulk of the WCAG2ICT Task Force’s work involved evaluating how each WCAG 2 success criterion would apply in the context of non-web ICT.
3030

31-
The WCAG2ICT Task Force found that the majority of WCAG 2 success criteria can be applied to non-web documents and software with either no or minimal changes. Since most of the success criteria do not include any web-related terms, they apply directly as written and as described in the “Intent” sections from the [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/) \[\[UNDERSTANDING-WCAG22\]\] resource. Additional notes were provided, as needed, to increase understanding about applying WCAG success criteria to non-web documents and software.
32-
33-
Because it is not possible to satisfy all Level AAA success criteria for some non-web content, it is not recommended that Level AAA conformance be required as a general policy for non-web documents and software.
31+
The WCAG2ICT Task Force found that the majority of WCAG 2 success criteria can be applied to non-web documents and software with either no or minimal changes. Since most of the success criteria do not include any web-related terms, they apply directly as written and as described in the “Intent” sections from the [Understanding WCAG 2.2](https://www.w3.org/WAI/WCAG22/Understanding/) \[\[UNDERSTANDING-WCAG22\]\] resource. Additional notes were provided, as needed, to increase understanding about applying WCAG success criteria to non-web documents and software. However, because it is not possible to satisfy all Level AAA success criteria for some non-web content, it is not recommended that Level AAA conformance be required as a general policy for non-web documents and software.
3432

3533
#### Interpretation of Web Terminology in a Non-Web Context
3634

0 commit comments

Comments
 (0)