情報アクセシビリティの国際標準化に関する調査研究(PDFﾌｧｲﾙ約
Contents
1. X 2 5 52. 5 4 6
3. Lis X 5 4 7
4. LH H D F i LL api
5. a 2 X8341 1 b
6. Vox 6 3 1
7. 5 5 2 1 6 fig 7 SAV CW D DBD AEST SD VED HD a
8. 1 JIS X8341 12 JIS X8341 1 2 3 JBMIA XXXXXXXXXXXXXXXXXXXXXXXXX d a eSI 4 5 6 JIS X 8341 5 5 7 8
9. XX a flit HETR S fon PAS JIS Z8071 b r5t GEO JIS Z8071 GR c d 0 1 2 3 4
10. 508 BE 255 FPC TEITAC 4 3 A URL http teitac org wiki EWG Draft Jan 7 2 1 3 2 1 4
11. 5 1 LES
12. b 6 1
13. 6 3 2 6 3 2 1 JIS 10 a JIS X8341 b
14. VL Rips CO ate 2 2 ISO 9241 20 9 1 1 Supporting basic and auxiliary functions a Basic functions that are needed to perform the main tasks that the ICT equipment or service should be capable of being used to the widest extent possible by all is designed to perform users EXAMPLE Since text entry is a basic function of a word processing program a variety of ways of text entry is provided to the widest possible range of users b Auxiliary functions that support or extend the basic functions should be capable of being used by most users 20 LNL DRETH oT BAIRRI ZAMEN 7 5 2Providing adjustable location of controls 7 5 3 Supporting either or only one hand 9 5 1 Providing installation information When the user is
15. IT INSTAC 2000 JIS JIS X8341 JIS X8341 5 5 2006 1 20 1 1 1 2 5 18 JIS
16. EL bls X8341 1 X8341 1 Annex B Sample checklist for assessing applicability and conformance of ICT equipment and services BELUT Ss CGC 6 2 2 6 3 JIS X8341
17. 21 JIS Z 8518 JIS Z 8519 JIS C 5512 ule JIS Z 8524 JIS Z 8528 2 FPD E E JIS T 0921 aa JIS T 0922 CES Q003 1 IT FCC 47CFR 68 137 a Receive Objective Loudness Rating ROLR FCC 68 TEC 60118 1 Ed 3 1 1999 b Hearing a1ds Part1 Hearing aids with induction pick up coil input 28 TIA ANSI TIA EIA 504 A 1997 Telecommunications Telephone Terminal Equipme
18. 0 OK AD Os WCAG 2 0 H Bo E 0 PIS Ow NE Error Suggestion If an input error is detected and suggestions for correction are known then the suggestions are provided to the user unless it would jeopardize the security or purpose of the content NN us BAT aS AI Error Prevention Legal Financial Data For forms that cause legal commitments or financial transactions to occur that modify or delete user controllable data in data storage systems or that submit test responses at least one of the followin
19. 4 2 4 3 4 4
20. ay 2 oT PUSS ROY HAA eux CR ere OSE Ae aE S o EAR SUR qw operations 6 2 Development accountability General managers and development managers should ensure that the information accessibility policy is followed in the planning design development and evaluation of ICT equipment and services The range of user characteristics supported by the ICT equipment and services should be sufficient to allow all groups of users to perform the tasks intended in the design 7 1 8 Supporting assistive technologies Standard interface mechanisms should be provided to support assistive technology b 3 Process c Produce design solutions paying particular attention to accessibility considerations Note4 In developments involving multiple parties the way of achieving accessibility
21. Re authenticating AAA When an authenticated session expires the user can continue the activity without loss of data after re authenticating Do not create content that is known to cause seizures 2 3 AF AD Three Flashes or Below Threshold A Content does not contain anything that flashes more than three times in any one second period or the flash is below the general flash and red flash thresholds 3 BIO DC amp Bie YO Fic 1 3 30 FRAMED HARD bw Z o B 5 3i 2 WAG Level 2 0
22. 28 4 1 1 1 2 1 3 2 1 2 2 2 3 2 4 3 1 471 4 2 FDIS FDIS JIS X8341 1 ISO FDIS9241 20 WCAG2 0 Lastcall WCAG2 0 5 WD WCAG2 0 JIS 2007 5 15 WCAG2 0 2 nd Lastcall NWIP NWIP 29 1 1 FDIS Reference ISO FDIS 9241 20 Committee ISO TC 159 SC 4 Edition number 1 Vienma agreement English title Ergonomics of human system interaction Part 20 Accessibility guidelines for information communication technology ICT equipment and services French title Ergonomie de l interaction homme systeme Partie 20 Lignes directrices sur l accessibilit de l quipement et des services des technologies de l information et de la communication TIC Start date 2007 11 23 End date 2008 01 23 Opened by ISO CSon 2007 11 23 10 48 52 Closed by ISO CS on 2008 01 25 00 00 30 Status Closed Voting stage Approv
23. 8 3 Performing maintenance and other non task related operations ZR POE CS ET Os ICT equipment and services should minimize the need for maintenance set up and other support A snae up UGS eU Ups etr eU ner
24. 5 6 5 1 5 2 5 2 1 5 2 2 5 3 5 3 1 5 4 fuh spe a ae ES 4 1 4 2 4 3 4 4 4 4 4 T 5 6 7 5 5 5 5 1 5 5 2 6 6 1 oe p e 2 val Cis di 2 2 3 1 3 2 3 3 3 4 3 5 3 3 vw 6 2 UL eq JIS L
25. GE an 1 3 3 Size Shape Location A JIS Instructions provided for understanding and Corb CVC KES n operating content do not rely on shape size 25 1 WCAG 2 0 Level visual location or orientation of components 1 4 Make it easier for people with disabilities to see and hear content including separating foreground from background 1 4 DNS 1 4 1 A 1 4 2 Audio Turnoff A JIS 3 If any audio plays automatically for more than 3 second
26. 3 l ae 9 5 5 Disconnecting equipment It should be easy to logically and physically disconnect the equipment e g from power supplies peripheral devices and networks 7 2 7 Adjusting contrast of displayed objects The capability to adjust the contrast of displayed user interface objects should be provided 7 1 2 Supporting multiple interaction mechanisms ICT equipment and services should support as many alternate means of interaction as possible to support the accessibility needs of different gTOUDS of users 7 1 3 Supporting simultaneous use of alternate interaction mechanisms ICT equipment and services should support simultaneous use of alternative means of interaction to meet the accessibility needs of users in different or changing contexts 7 1 7 Saving and retrieving customized configurations Where possible a means should be provided to save and retrieve a user s customized configuration i 1
27. uos T CC 3 ES Tes n AR 4
28. SC35 1 15 SC35 WG6 a WD 2 10 WG 4 JTC1 SC35 b JTC1 SC35 2008 2 18 22 ISO IEC JTC1 SC35 JIS X8341 2 ISO IEC29316 19 SC35 WG6 auc POE gt Introduction Shall Should
29. JIS X8341 X 8341 2 4 2 2 4 2 1 1 WG WG JIS X8341 AWG X8341 H20 Partl 2 4 2 2
30. 1 2 2 Audio Description or Full Text Alternative A JIS cla prerecorded live Audio description of video or a full text alternative for multimedia including any interaction is provided for prerecorded 23 WCAG 2 0 4 9 122 4 2 0 12 0 D 1 multimedia Captions Live AA Captions are provided for live multimedia Audio Description AA Audio description of video is provided for prerecorded multimedia S1gn Language AAA Sign language interpretation is provided for multimedia
31. Xx 7 19 0 1 Fo HRE 3 JE Fe JE 4 ae 6 0 gt gt ee ye a 8 20
32. JIS JISX8341 1 1 JIS X8341 JIS INSTAC Part2 PC JIS WG3
33. 200 25 PIX 50 RA T bs UPA ATE ds Contrast Enhanced Text and images of text have a contrast ratio of at least 7 1 except if the text is pure decoration Larger scale text or images of text can have a contrast ratio of 5 1 7 1 5 1 Low or No Background Audio Audio content that contains speech in the not contain foreground does background sounds background sounds can be turned off or background sounds are at least 20 decibels lower than the foreground speech content with the exception of occasional sound effects 20
34. User Needs Summary Standards Inventory User Needs Summary Guidance 2007 10 JTC1 TR 2008 2 29 PDTR PDTR 2008 6 SWG A 2008 6 19 SWG A ISO IEC JTC1 SC35 WG6 User interfaces for disabled and elderly people DS ISO IEC FCD 24786 Information Technology User Interfaces Accessible User Interface for Accessibility Setting on Information Devices FCD 2008 2 FCD FDIS CIE Ace c 5 JIS Brit E
35. ISO IEC JTC1 SC TISO0 TC WG 2 1 2 a JIS X8341 1 JIS X8341 1 IS0 TC159 SC4 Ergonomics of human system interaction ISO 9241 20 2008 1 23 FDIS 2008 2 4 IS0 60 00 International Standard under publication 2008 2 JIS X8341 2 JTC1 SC35 User Interface 2007 7 NWIP 5 8 SC35
36. 1 3 JIS X 8341 JISZ8071 wen F71 1 JISX8341 1 INSTAO 2 JISX8341 2 JEITA 3 JISX8341 3 INSTAC 4 JISX8841 4 CIAJ 5 JISX8341 5 JBMIA HE O JTS 1 1 JISX8341 2 WC4 WVG03 2 JIS X8341 JIS INSTAC 1 3 1 ISO TC159 SC4 IS09241 20 INSTAC 2 ISO IEC JTC1 SC35
37. T 65 T OD HEU A 65 74 2 75 85 AE Eo ee 85 D 4 Cf 5 3 5 3 1
38. c JIS X8341 1 d 5 2 5 2 1 JIS X8341 ICF JIS S0024 ICF 2001 International Classification of Functioning Disability and Health ICF
39. 3 11 4 5 6 7 8 9 10
40. 2 WAG Level JER 2 0 2 4 Make all functionality available from a keyboard 2 1 2 1 1 Keyboard A X ch BF BRE without All functionality of the content is operable requiring specific timings for through a keyboard interface without individual keystrokes 2 HAAR requiring specific timings for individual keystrokes except where the underlying function requires input that depends on the path of the user s movement and not just the endpoints I 2 1 2 Keyboard No Exception AAA without All functionality of the content is operable requiring specific timings for 28 WCAG 2 0 2 2 292 DD 2 9 2 dd 2 Level through
41. 2 la C amp A xf 7 ea LI 8 9 gt Lo 10 1
42. Qus 2 3 2 Three Flashes AAA Content does not contain anything that flashes more than three times in any one second period 3 1 3 2 Provide ways to help users with disabilities navigate find content and determine where they are 2 4 2 4 1 2 4 2 2 4 3 Focus Order A Understandin g Common Failures If a Web page can be navigated sequentially focusable components receive focus in an order 5 2 d that follows information and relationships conveyed through presentation SC sequential navigation device Web independ IC DV TMA TWA 5 3 a
43. Resize and Wrap Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or 27 Level AA AAA AAA AAA 200 AH 50 zB JIS JIS 20 200 509 1 WCAG 2 0 Level functionality and in a way that does not require the user to scroll horizontally VAAL TI XI 2009 50 Principle 2 Operable User interface components must be operable by users 2
44. 1 1809241 20 e JIS X8341 1 WG2 19 e JIS X 8341 3 Zh YA EM AI WA OE e JIS X8341 3 WG3 19 e JIS X8341 WG4 19 e JIS X 8341 2 2 1 2 19 1 4 1 4 1
45. 6 3 3 2 6 3 4 a b c d 1 2
46. 5 3 b JIS Tab order o UNO a 26 6 JIS WCAG WG label ues YO elas SEE GE HOMO aes 2 4 4 2 4 5 Multiple Ways 1 2 More than one way is available to locate content within a set of Web pages where content is not the result of or a step in a process l WCAG 2 0 2 4 2 4 2 4 2 4 2 Level 1 Web Labels Descriptive AA Headings and labels are descriptive AAA AAA AAA Principle 3
47. 6 1 1 X8341 1 5 2 5 3 6 1 2 X8341 1 JE XB Tee Ce 6 1 3 6 2 6 2
48. H 9 2 13 6 3 5 6 3 5 1 6 3 5 2 LU 6 3 6 63 3
49. 9 1 5 Providing interoperability IICT equipment and services intended to work with other ICT equipment or services should not interrupt or invalidate any accessibility related functions of these other ICT equipment and services EXAMPLE A device has a large number of USB ports so that it can support the independent connection of a variety of devices simultaneously including multiple assistive technologies 9 3 2 Supporting combinations of assistive technologies Combinations of multiple assistive technologies should not disturb the functions of individual assistive technologies 46 REFE DTT EERI o 9 3 1 Connecting assistive technologies The connection of assistive technologies should be supported to provide modes of interaction which are not provided by the ICT equipment or service b 8 2 Providing alternate ways of performing tasks ICT equipment and services should enabl
50. 14 60cm 5m
51. 3 C ae 5 3 2 i NN EE ea C 5 4 5 4 1 1 1 1
52. ZE ha 700 9e Sea eo De 3 1 15 T 4000Hz r3 2000Hz 2 UT
53. 2 AI 3 BO 7 6 1 Limitations in cognitive capabilities ICT equipment and services should support users who have limitations in their cognitive capabilities 7 6 2 Avoiding unnecessarily high cognitive demands ICT equipment and services should avoid unnecessarily high cognitive demands on users by ensuring that the basic activities required to operate the equipment or to use the service are as straightforward and simple as possible 7 6 3 Aiding understanding Information should be presented and organized in a manner that will aid understanding by users 7 6 4 Using understandable vocabulary The vocabulary used to describe and operate ICT equipment and services should use expressions and terminology that are as easy as possible to understand irrespective of the level of expertise and cognitive capabilities of users 7 6 5 Providing information pictorially Where possible information should be provided in symbolic or pictorial form to enhance the user s ability to comprehend the information
54. Part 5 JIS JISA 2005 4 2 4 2 3 JIS S0024 1 2 4 2 4 JIS Z8301 6 3 6 JIS 28530 18013407
55. JIS X8341 2 2 2 WG1 ICT 2 2 1 JISX8341 1 ICT ISO TC159 SC4 b 9241 20 2 2 2 JIS X 8341 1 ISO 9241 20 IS0 TC159 SC4 FDIS IS0 1S09241 20 JIS 2 2 2 1 DIS
56. JIS X8341 1 2 JIS X 8341 1 5 O JIS JIS X8341 JIS X 8341 1 3 19 19 1 2 x WG WG1 ICT 19 0 e JIS X 8341 1
57. 40 In the second bullet does 80 characters apply to the Japanese characters The character in Japanese are double byte character in general For the Japanese content would 40 characters be appropriate for this e Accessibility Support OD ZOFARI TA NVOMKEOI Avy Accessibility Support Understanding Accessibility Support http www w3 org TR 2007 WD UNDERSTANDING WCAG20 20071211 conformance html uc acces sibility support head Documenting Accessibility Support for a Web Technology http www w3 org TR 2007 WD UNDERSTANDING WCAG20 20071211 appendixB html DocumentedLists Documented Lists
58. c d e f JIS g h i 6 3 2 2
59. 508 255 Access Board TEITAC Telecommunications and Electronic and Information Technology Advisory Committee 2006 9 TEITAC 2006 9 11 2007 2 5 7 9 6 2007 11 2008 1 2008 4 3 1 TEITAC 508 undue burden 355 readily available Section 119
60. IS0 IEC29136 We 3 JIS X8341 3 W3C WAI WCAG2 0 JIS WCAG2 0 2 2007 12 Ni 4 JIS X8341 4 ITU T SG16 2007 1 F 790 MEC E II M M ME MEE E 5 JIS X8341 5 ISO IEC JTC1 2007 11 A DIS ISO IEC JTC1 SC28 Ofiice equipment sien ida ISO IEC10779 2008 b 1 ISO TC159 WG2 Ergonomics for people with special requirements TR22411 Ergonomic data and guidelines for the application of ISO IEC Guide 71 in standards related to products and services to address the needs of older persons and persons with disabilitie
61. FDIS 2007 3 ISO 15 FDIS 2007 11 23 2008 1 24 FDIS FDIS NOTE NOTE FDIS 1 1 1 2 2 2 2 2 JIS X8341 1 JIS X8341 1 2004 5 2009 IS09241 20 a 1S09241 20 X IS0
62. IS0 TC159 AGA ISO TC159 11 Advisory Group for Accessible Design IS0 TC159 SC4 Ergonomics of human system interaction SCA WG1 1S09241 20 IERD FDIS ISO 9241 151 Ergonomics of human system interaction Part 151 Guidance on World Wide Web user interfaces WCAG FDIS FDIS ISO 9241 171 Ergonomics of human system interaction Part 171 Guidance on software accessibility FDIS ISO IEC JTC1 SWG A Special Working Group on accessibility 2007 4 SWG A SWG A 3 TR
63. ISO IEC Guide71 JIS S0024 4 ICF body functions
64. Int A 10 2 Designing environments lb layout and use of space EXAMPLE Sufficient space is provided for needs of users when designing wheelchair users to manoeuvre 4 8 4 1 Principles b Equitable use Achieving equitable use will ensure that solutions designed to increase accessibility do not result in loss of privacy increased risks to personal safety or security or the stigmatisation of individuals and that solutions provide the same means of use for all users that are identical whenever possible equivalent when not 9 1 9 Biometric data Alternative means should be provided for users who cannot supply specified biometric data 4 9
65. JIS X 8341 3 2004 5 2009 WCAG2 0 JIS 3 2 3 2 1 WCAG2 0 WCAG2 0 W3C WAI WCAG2 0 WCAG2 0 JIS JIS a WCAG2 0 WCAG2 0 Candidate Recommendation 34 Proposed Recommendation 2008 12 e 2006 4 WCAG2 0 1500 WD e 2007 5 WD e 200
66. ISO IEC JTC1 SC35 2 5 2 2 5 2 1 NP New Work ItemProposal 4 1 SC35 2007 4E 3 ISO IEC JTC1 SC35 NWIP 7 12 4 12H NWIP 8 JTC1 SC35 lt gt NWIP 10 1 HHS 5 TYPE3 TR a JTC1 SC35 WG 6 ISO TC159 SC4 WG4 2007 8 JTC1 SC35 1S0 TC159 SC4 WG4 JIS X8341 2
67. Te 6 Timing AAA Timing is not an essential part of the event 29 individual keystrokes HAAR JIS5 8a JIS 3 V 0 0 eque XU O e JIS 5 8a JIS HA ZTE PEG WCAG 2 0 5 2 2 0 D8 3 dsl 2 Level or activity presented by the content except for non interactive multimedia and real time eveT HA CIN Vx de ef 0 Interruptions AAA Interruptions such as updated content can be postponed or suppressed by the user except interruptions involving an emergency
68. 39 3 1 GE Appendix3 1 Evaluation Method for Information Accessibility 1 2 3 3 1 JIS X8341 1 2 2 body functions SENS body structures 3 4 impairments 3 5 JIS Z8301 3 6
69. 2 X 5155887 01K 4 iis ew 6 3 18 oe 5 I P 2 ERRORS OFX wee PEPE SRS RS
70. CEN BT WG185 2007 10 1 CEN BTWG185 2007 10 PT 2007 12 PT BTWG 2008 1 2 2008 2 BTWG 2008 3 CEN CENELEC PT BTWG 2008 4 3 2008 5 PT 2008 5 2008 7 4 2009 1 H CEN CENELEC EFTA 2 4 6 3 A URL http www verva se english it procurement accessibility conformance 2 508
71. JIS X8341 1 ISO 9241 20 5 5 1 JIS X8341 1 lt
72. WCAG 2 0 2008 12 rt 2008 12 2009 1 2009 3 JISC 2009 6 JIS WCAG2 0 JIS Accessibility Support WCAG2 0 DEY JIS 2 4 WG3 2 4 1 508 PR ERK TII Testability JIS X8341 JIS X8341 JIS
73. WD JISX8341 2 TC159 SC4 WG4 PC 508 EU Mandate376 WD 11 15 2 CD 12 15 TC159 SC4 WG4 1 IB WD 2 c JTC1 SC35 SC35 NWIP RESOLUTION 29 Appointment of project editor on new work item titled Information Technology User Interfaces Accessibility functions for personal computers WG6 SC35 appoints Mr Shigetoyo Nomura as editor for Information Technology User Interfaces Accessibility functions for personal computers Adopted unanimously RESOLUTION 30 Progress of new work
74. X8341 3 OPC FZAD Sie CHB W3C WAT WCAG WG WCAG 2 0 WCAG2 0 JIS X 8341 3 JIS WCAG2 0 b JIS 2009 JIS X8341 3 WCAG2 0 WCAG2 0 JIS JIS 2 3 4 a WCAG2 0 WCAG2 0 Web WCAC UAAG ATAG UAAG ATAG Ver2 JIS 20 b JIS 2009 6
75. OT Consistent Navigation AA Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated unless a change is initiated by the user Web Web AU CWO ee AA Change on Request AAA Changes of context are initiated only by user request Help users avoid and correct mistakes Wen Error Identification A If an input error is automatically detected the item that is in error is identified and described to the user in text 34 JIS 5 3e le
76. press a button or type information within a limited time in order for that response to be valid the time range should be adjustable by the user including the option to turn off all timing requirements d 19 1 4 Providing safety information Information about hazards related to equipment and services and their components and their use should be presented using formats that allow this information to be understandable by users EXAMPLE If materials that are poisonous or likely to cause allergic reactions are used in the equipment a permanent warning label that can be read and understood by users e g text and Braille are affixed to the equipment ACT oA oo s 7 6 10 Supporting cultural and linguistic differences 2 The vocabulary used to describe and operate ICT lequipment and services should use expressions on that can be understandable by users with differences in culture or language
77. V O FA D 4 La 4 2 Ar dE 16 0 XA PAYERS L 5 3 17 Levi
78. 4 X JIS X8341 Informative
79. WG1 WG8 WG6 e OL WG 2 WG 3 WC 4 WG 5 WG 6 WET juu mE e WCG8 P 15 W6 WGI WG LPG CY Peep WO OS Ye Hay CARE usce Cres P WG6 ire SC35 P NP
80. Fae Fi Tables 1n PDF format can be difficult for assistive Please issue the tables in Word format so that as technology users assistive technology users can change the font size in order to complete it ge There are nO There are no requirements in the document in the document Consider using shall instead of should ta 4 2 There is no feedback path from users the market place Amend figure to incorporate feedback path Figure 1 back into the design process Clause 9 4 1 The clauses covering the communication of how Consider an approach where red amber green is comprehensive accessibility 1s 1s poorly covered used in order to summarise for consumers how well visual issues hearing etc are addressed JIS 3 1 te Heading of the text interactive system is not easy to Remove interactive system C understand for standard users Add note Note this definition is applicable for interactive system JIS 4 2 paragraph te In 1s sentence it is not clear the range of users Remove the first sentence in the 1 paragraph especially the population of capability d 4 2 d It is not clear the populations Change such populations to a population B 1st paapa bs It is not clear all group users Change all groups users to the widest possible e grange of users Missing of in the text The accessibility of user guidance The accessibility of user guidance should be s
81. 19 20 3 Ln Leh ORR AR RR A ER OE Ale a Je EN A ER JEU A oie aed A A RA el Bh ch did 2 ED o XE gene ee ee Cee er SE CR 9 3 ALE uer 1l D EET 9 4 E Bo n B ONDE toe Eee Cee ee aU ree HEURE PEU Edda 4 l 4 1 eee 4 kaa eea oea e EE E SEE 5 Tor WG2 8 1 4 4 WG3 e III Icio WG4 8 5 EE Tm eee mm IIIA IIIA I I hl 9 6 DS RN Re ee ee ee ee 6 10 1 6 1 WG1 ICT eee 10 1 6 2 WG2
82. X8341 JIS X8341 Part 2 JEITA JIS JEITA Part 3 JIS WCAG2 0 X8341 3 Part 4 JIS 4 IS013407
83. 9 4 1 Providing accessibility information FEO LAA TR Information about the accessibility of ICT Y lequipment or services should be available in formats that can be used by people with widest AT 5 7 RANCATE E RII ISO v ensure accessibility range of capabilities 2 1 WCAG2 0 Lastcall Comment 1 about Accessibility Supported source http lists w3 org Archives Public public comments wcag20 2007 Jun 0317 html Issue ID 2172 In the description of Accessibility Supported in the section of Important New Terms Used in WCAG 2 0
84. 2 7 1 6 Returning to default configuration A method that does not require users to reconfigure or restart the equipment or service should be provided to allow users to reset an ICT equipment or service to its default configuration 9 1 6 Providing error tolerance All users should be protected from the consequences of accidental or unintended actions 7 5 4 Limiting physical force requirements Controls should be movable with the minimum force required within the constraints of the operation being performed 7 5 2 Providing adjustable location of controls The placement of controls and displays should be adjustable to heights and locations that the users can reach 7 5 7 Providing user control of response timing If a task requires users to make responses e g press a button or type information within a limited time in order for that response to be valid the time range should be adjustable by the user including the option to turn off all timing requirements 9 7 Providing undo or confirm a Users should be able to reverse undo actions made by the system in response to their commands b For actions that are impossible to undo the user should be required to confirm the action before it is performed by the system
85. gt D JIS JIS JIS WCAG2 0 9241 20 6 XX JIS WCAG 2 0 4 JIS WCAG2 0 ae 2 1WCAG2 0 WCAG2 0 JIS Shall Should Should JIS JIS AA AAA WCAG 2 0 testability JIS 3 WCAG2 0 WCAG2 0 WCAG2 0 JIS 4 W3C Understanding JIS WCAG
86. JIS I80 9241 20 873 7A E LA IDTC 0 5 LTJIS X8341 1 JIS X8341 1 2004E ISO 9241 20 1 6 2 WG2 a WCAG2 0 2 2 nd Last Call Working Draft WCAG2 0 2 JIS b JIS X8341 3 WCAG2 0 JIS 1 6 3 WG3 a JIS X8341 X8341 b JISX8341 1 6 4 WG4 ISO IEC JTC1 SC35
87. NWIP JIS X8341 2 2 NWIP IS0 IEC29136 b WD 8 WD SC35 WG6 2 WD NY a 1 6 5 KERZAS TEITAC TEITAC TO 1 6 6 WG WG CEN BT WG185 2 2 1 2 1 1
88. 3 3 3 ya M WCAG 2 0 H PIS Ow y EY 7 ae 27 Vie CE s 1 2 v BEA 3 Level Principle 4 Robust Content must be robust enough that it can be interpreted reliably by a wide variety of user agents 4 including assistive technologies 4 WAG Level JER 2 0 4 1 WCAG 2 0 WD GL 4 1 Maximize compatibility with current and future user agents including assisti
89. body structures 5 2 2 JIS Z8071 JIS 80024 4 11 4 JIS Z8071
90. CD WD JIS S0011 IS0 TC159 SC4 ISO AWI 24503 Ergonomics Marking tactile dots on consumer products Guidelines for all people including elderly persons and persons with disabilities JIS 80013 REDE PEE RO TRE MH Et LEE Bann C KA TC159 SC5 ISO AWI 24500 Guidelines for all people including elderly persons and persons with disabilities Auditory signals on consumer products JIS S0014 TC159 SC5 ISO AWI 24501Guidelines for all people including elderly persons and persons with disabilities Auditory signals on consumer products Sound pressure levels of signals for the elderly and in noisy conditions JIS S0021 TC122 ISO AWI 11156Guidelines for all people including elderly persons and persons with disabilities Packaging and receptacles JIS S0031 TC159 SC5 ISO AWI 24502 Guidelines for all people including elder
91. INSTAC 3 W3C WAI WCAG2 0 INSTAC 4 ITU T SG16 CIAJ 5 ISO IEC JTC1 SC28 JBMIA EU Mandate376 3 CEN CENELEC ETSI 508 255 BO TEITAC 2006 9 2008 4 INSTAC JIS X8341 TEITAC
92. fad 4 ISO JIS 4 5
93. Y JY IN JN IN IN 1 tnt Y JY N WN IN_ IN tnt Q amp Cs ROS eee 1 NO This is a valuable application profiling on existing standard provisions mostly on 9241 171 This should be a TR not an IS Q2 NO This would change to a YES if the proposal changed to an NP for a TR type 3 E UT PESE Bit 19 20 3 T 100 0014 2 13 5 03 3592 1408 T107 8440 4 1 24 03 3585 4558
94. 3 BE Labels or Instructions AA Labels or instructions are provided when content requires user input AU EJ Help AAA Context sensitive help is available Error Prevention A11 AAA For forms that require the user to submit information at least one of the following is true 1 Reversible Transactions are reversible 2 Checked Submitted data 1s checked for input errors before going on to the next step in the process 3 Confirmed A mechanism is available for reviewing confirming and correcting information before finalizing the transaction 36 e MV JIS Ci e OUT S Bic ick Cicty77
95. Audio Description Extended AAA Extended audio descriptions of video are provided for prerecorded multimedia Full Text Alternative AAA For prerecorded multimedia a full multimedia text alternative including any interaction is provided 24 Level JIS cla prerecorded live JIS chk prerecorded F live JIS JIS prerecorded live JIS JIS chk prerecorded F live JIS JIS la full multimedia text alternative including any interaction 1 WCAG 2 0
96. Level 1529 Create content that can be presented in different ways for example spoken aloud simpler layout etc without losing information or structure 1 3 Aloe NA ante Cees Ee Ce eae pu 1 3 1 Info and Relationships A JIS clk relationships Information and relationships conveyed Die through presentation can be programmatically determined or are available in text and notification of changes to these is available to user agents including assistive technologies L C qo iC Cao eee 1 3 2 Meaningful Sequence A JIS chk sequence When the sequence in which content is presented affects its meaning a correct reading sequence can be programmatically determined and sequential navigation of interactive components is consistent with that sequence 0
97. 4 1 NWIP New Work ltem Proposal PROPOSAL FOR A NEW WORK ITEM Date of presentation of proposal Proposer 2007 02 20 JISC JAPAN Secretariat ISO IEC JTC 1 8C35 N XXX National Body AFNOR FRANCE A proposal for a new work item shall be submitted to the secretariat of the ISO IEC joint technical committee concerned with a copy to the ISO Central Secretariat Presentation of the proposal to be completed by the proposer Title Information Technology User Interfaces Accessibility functions for personal computers Scope This standard provides requirements and recommendations for the design of accessibility functions regarding personal computers PCs This standard specifies accessibility requirements and recommendations for the designing of PC functions that are implemented by hardware or combination of hardware and software This standard will refer requirements and recommendations for the design of the PC software specified in coming ISO 9241 171 Purpose and justification This standard clarifies accessibility functions for personal computers especially for elderly and disabled persons Programme of work If the proposed new work item is approved which of the following document s is are expected to be developed X a single International Standard more than one International Standard expected number a multi part International Standard consisting of parts an amendm
98. UAAG User Agent Accessibility Guidelines ATAG Authoring Tool Accessibility Guidelines Ver 2 TR 2 3 2 3 a 2007 5 International Cross Disciplinary Conference on Web Accessibility W4A Experimenta1 evaluation of usability and accessibility of heading elements Best Paper Award 19 Task completion times of sighted and blind users were measured with two kinds of Web sites sites marked up appropriately with heading elements and sites with the same visual appearance but with no heading elements marked up The experiment was carried out with user agents that could navigate through heading elements The results showed that 1 task completion time was reduced by as much as one h
99. TIDT JIS X8341 1 JIS X8341 1 2004 ISO 9241 20 IS0 FDIS9241 20 2 4 JIS X8341 1 2009 2008 12 2009 1 2009 3 JISC 2009 5 JIS 3 WG2 3 1 JIS X8341 3 REDE ERA Sac Et aa ICH ORR VT hoe 3 W3C JIS IS0 AEM DEO IVIT lt S VY W3C WAI Web Accessibillity Initiative W3C WCAG2 0 W3C
100. PC JIC SC35 WG6 IS0 TC159 SC4 WG4 ISO 9241 171 Ergonomics of human system interaction Part 171 Guidance on software accessibility JTC1 SC35 SC35 WG6 TC159 SC4 WG4 TC159 SC4 WG4 PC SC35 gt PC PC PDA PC Shall 24 b JTC1 SC35 WG6 TC159 SC4 WG 4
101. m 54 S ra Ml gn X x XI i X FH H D gt a Ma St Ba xm um m RESJA em E ni fam e JEITA CH JES RESJA JISA FE CIA JBMIA 1 4 2 WG1 ICT Mee eem NT 1 4 83 WG2 W3C XJ lH IER A A bl iH gt N H WE h IB UR usu T se fr F an xm ma AM O RA MA ERA D D A lez AXE g 7 kil 3 1 4 4 WG3 s ZH ee em A um
102. 5 gt JTC1 SC35 AFNOR P 15 M es qo ONIS 060 PE SAG rata ON Da 7 ASRS DIN ELOT BIS JISC KATS AVY uU SIS UND DSU UNL 0 9 WS GZ SAL KEBS NEN PKN ASRO GOST AENOR 3 ICT ICT 19 JIS X8341
103. 9 5 3 Switching off equipment It should be easy to switch off equipment 9 5 4 Storing equipment It should be easy to store equipment 4 3 2 b 3 MERITS E BRDC T SE 9 ACE Vie ROD a Aaa S C 1 PAVE ODE f 2 E
104. 19 10 4 15 00 17 00 14 00 17 00 9 30 12 00 E JSA202 JSA202 ee pk 19 4E 11 H 29 B 19 10 19 14 00 17 00 14 00 17 00 Bang P REP CM QE qM JSA201 JSA 3 19 12 27 19 10 26 15 00 17 00 10 00 12 00 JOARE JSA 3 20 1 17 19 11 1 14 00 17 00 14 00 17 00 Li el il JSA802 JSA202 nm Pr RW ed EGER ILS S CSI EDEE 14 00 17 00 10 00 12 00 ec JSA202 JBMIA UC 19 12 11 10 00 12 00 JBMIA UC 20 2 12 10 00 12 30 JBMIA UC 1 6 1 6 1 WG1 ICT a ISO FDIS9241 20007K 8 JIS X8341 1 TS0 9241 20 HEHE 2008471 23 H ICFDISH EA MMOD bt BARBRA CHR LE 2008 2 4 IS0 60 00 International Standard under publication 2008 b JIS X8341 1
105. JIS JIS Z 8071 JIS X 8341 1 JIS JIS JIS JIS e JIS JIS JIS JIS JIS JIS JIS e JIS JIS JIS e JIS JIS JIS JIS e JIS JIS JIS JIS P lt An na oa P lt Anna nan MN CD c o g 8341 2 8341 3 8341 4 8341 5 0011 0012 0013 0014 0021 0022 0022 3 0022 4 0024 0014 0026 0031 0032 0033 9201 9203 6910 8513 1 SS ae 2 UU qoe Moses SE TT IT bee aa SA ea at RET TH Sus C39 0 O aa ABD 5
106. 7 10 1 6 3 WG3 10 1 6 4 WG4 ED SBDERMEMEERA fI 10 1 6 5 Sg ska E AERP A onesie A Staus 10 1 6 6 NS en bate eam beni rane ober ba e ee re 11 N EN eee ee ee EE NE EE EA ee eee i 1 11 2 1 1 11 9 1 2 SE ht ee ce ci NN NN bet abaco cle tiga 11 Tine HH I hh 15 2 1 4 Se a ee IS ee ee ee ee TR ee ee 15 2 WG1 ICT e II 15 2 2 1 rd 15 D 9 9 WR ce S 15 DD AH m I hh 17 2 9 4 2 tb 17 3 WG2 eee eR ii 2 cl mE 17 D 3 9 PS ZS 17 RC EEREE 20 D 8 riri LI 20 4 WG3 3 amp SERR RIESSAEEBAR n HIR 2 2 4 1 SM 21 2 4 9 US espere e cee bri E ee RC od ud oq equ 21 2 4 8 293 2 4 4 els 22 2 5 WG4 24 2 5 1 NI E see 24 2 5 Ve S A ee ee AA ee Eh 24 DEO LUE 27 Dice A Sp i EET 27 PGE EH ER i CE ge MERE OEY NR HERE RKC henna 28 f ee ee ee ee 0 MA dali ka er Rt qa ee ce 29 ii 1 1 1 2 1
107. there is an Editorial Note which reads The W3C WAI will be compiling existing information on its technologies It is expected that other organizations will compile such information for their technologies There will undoubtedly be others who create documented lists as well It is irresponsible of WCAG WG to rely on the other organizations WCAG 2 0 is a guidelines which would be recommended by W3C WAT If WCAG 2 0 require authors to consult documented lists of technologies that are known to have accessibility support WCAG 2 0 itself should provide the documented lists If WCAG 2 0 would rely on other organizations WCAG WG should create the test files for each technologies so that other organizations will be able to compile such information based on the same level of the measure The documented lists for any languages should be created by using the same test files and the same test procedure with the same measure Without those materials JIS WG or any other organization in Japan won t be able to do anything Even if some organization would create the lists it could be unreliable information and the sites based on such information could be inaccessible to the users in reality For any other languages than English this must be one of the big concerns Additionally the format for the documented lists should be provided to ensure the consistency across the languages Proposed Change Develop and Provide the test files and
108. 2 2006 4 14 2007 5 2 1 JIS 6 29 WCAG 2 2 2 3 2007 12 2 4 2 4 2 3 2 2 JIS WCAG2 0 2008 12 JISX8341 3 2009 WCAG2 0 JIS X8341 3 WCAG2 0 JIS WCAG2 0 JIS
109. relate to common user experiences to minimize the need for special training 4 2 HINA LL CWS DIF TIER DS CT 43 1 0 0 O Be CE Aue AS E
110. 2004 X8341 1 2009 EFA 9241 20 2 9241 20 3 Terms definitions and abbreviated terms BHA X8341 1 2004 X8341 1 2009 9241 20 DARZ OUTS WC 1S09241 20 ISO JIS AnnexB 16 2 Zi RO N P 2 2 2 2 3 JIS X8341 1 ISO 9241 20 IDT JIS X8341 1 JIS X8341 1 2004 ISO 9241 20 1S0 FDIS9241 20 JIS X8341 1 2004 1 3 2 3 a IS09241 20 FDIS 2008 b JIS X8341 1 ISO 9241 20
111. 7 6 6 Providing appropriate cues ICT equipment and services should provide appropriate cues to assist users in paying attention to important information e g control status 7 1 7 Saving and retrieving customized configurations Where possible a means should be provided to save and retrieve a user s customized configuration 7 1 6 Returning to default configuration A method that does not require users to reconfigure or restart the equipment or service should be provided to allow users to reset an ICT equipment or service to its default configuration 7 1 7 Saving and retrieving customized configurations Where possible a means should be provided to save and retrieve a user s customized configuration 4 17 6 8 Enabling pausing or stopping Whenever moving blinking scrolling or lauto updating information is presented the fied Oo Sg A user should be enabled to pause or stop this dynamic presentation D 7 5 1 Limited physical movement ICT equipment and services should support users ewer who have limited physical movement Providing adj
112. This success criterion is based on common pixel sizes available today Users who have low vision would be responsible for choosing appropriate settings Comment 5 Rationale for 200 and 50 Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0321 html Issue ID 2176 We need more concrete reason rationale on why 200 percent and 50 percent were chosen by the WCAG WG Without the reason rationale we won t be able to determine if 200 percent and 50 percent can be applied to the Japanese characters Proposed Change Add more concrete rationale for why 200 and 50 Response from Working Group As text is scaled larger and larger it becomes impossible to prevent loss of content or functionality When horizontal text is enlarged beyond a certain level text wrapping algorithms turn the text into a vertical column of words possibly clipped if the word itself is too large to fit into the available horizontal space on screen For vertical text similar problems occur Arbitrary resizing also introduces problems with testing How does an author know when he has satisfied the success criterion particularly for more sophisticated web pages that may change their layout based on the text size to produce more readable results An example would be a page that switches between single and multiple column text so that line widths stay within the 16 word range recommended f
113. A 5 Cie 38 Level A name role states properties value JIS JIS5 1a 2 4 WCAG2 0 2 nd Lastcall e 1 4 5 Images of Text Limited We need to clarify the intent of this SC In the first bullet it reads Customizable d The image of text can be visually customized to the user s requirements What do you mean by visually customized Does it include all of the following Font family Font weight Font color Font size Need more clarification on what visually customized means e 1 4 5 Images of Text Limited SVG Does text of image include text generated by SVG e 1 4 8 Visual Presentation 1 80
114. CKE shall Terms and definitions sentence phrase Shall Should Soft WD ISO Directives SC35 WG6 CD WG6 c 7 WG6 WMG6 686 2008 9 SC35 WG6 26 RESOLUTION 18 Progress of project ISO IEC 29136 titled Information Technology User Interfaces Accessibility functions for personal computers WG6 SC35 requests the editor of ISO IEC 29136 to make the required changes discuss
115. Secretariat and ISO IEC JTC 1 SC 35 P members Related SC 35 Questions for this ballot Q 1 Do you accept the proposal in documentsc35n1161 as a sufficient definition of the new work item Q 2 Do you support the addition of the work item to the programme of work of the joint technical committee Not yetvotedl3 YES NOH ABSTAIN 1 Q 3 Do you commit yourself to participate the development of this new work item Not yet voted 3 NO 6 jr Q 4 Are you able to offer a project editor who will dedicate his her efforts to the DEA IO and maintenance of this project If YES please identify ee ABSTAIN 1 Q 6 Will you have such a contribution in ninety days 3 Country Organisation Q1 Q2 Q3 Q4 Q5 a6 Austria ON TT Canada SCC LY Y Y N IN IN China SAC YY IN N IN IN WW Czech Republic CNI YY Y IN _ IN IN IN pe interest to this project Greece ELOT Y Y Y IN _ IN _ IN Finland SFS TE jJ T T opo ooo o France AFNOR LY Y Y IN N JN India BIS IY Y JN JN IN N m Japan JISC Y Y y Y Y Y Q4 Japan nominates Mr Shigetoyo Nomura as a project editor when this proposal will be approved and assigned to 5C35 WG6 Korea KATS Romania ASRO Sweden SIS Ukraine DSSU USA ANSI shigetoyo nomura kp hitachi com Hitachi Ltd Y Y Y IN IN IN d 1 5
116. expected to install ICT equipment the information necessary to complete this task should be provided in alternative formats available to all types of users ee MO ay FARE 2 25 C GR SICA 2 gee my B MERI UE gt i Os 3 EHE 4 5 7 6 3 Aiding understanding Information should be presented and organized in a manner that will aid understanding by users 7 6 3 Aiding understanding Information should be presented and organized
117. is a matter of negotiation and 9 4 3 Maintaining compatibility in replacement equipment or service A new version e g an upgrade or new model of an ICT equipment or service should be capable of being used by at least the same range of users as the existing version d 7 1 2 Supporting multiple interaction mechanisms ICT equipment and services should support as Mlk many alternate means of interaction as possible Ito support the accessibility needs of different gTOUDS of users 7 1 8 Supporting assistive technologies Standard interface mechanisms should be provided to support assistive technology 9 4 1 Providing accessibility information Information about the accessibility of ICT equipment or services should be available in formats that can be used by people with widest range of capabilities 7 1 8 Supporting assistive technologies k Standard interface mechanisms should be provided to support assistive technology 9 1 5 Providing
118. the measure for the documented lists on Accessibility supported technologies Provide the format for the documented lists Not rely on the other organizations than W3C as WCAG 2 0 is one of the W3C guidelines WCAG will be providing the format for a documented list We cannot document all versions of all technologies for all languages by ourselves however It is simply too much work and there are not sufficient resources Also it would not make sense to duplicate or turn away good research by others It is beyond the WCAG WG charter to document all technologies in particular proprietary technologies that are not maintained by an open standards body such as the W3C The Web Content Accessibility Guidelines set guidelines to determine if a technology is accessibility supported Comment 2 Discussion of Documented lists needs clarification Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0318 html Issue ID 2173 In the section of Understanding Documented lists of Web technologies with Accessibility Support it reads There is no requirement in WCAG that a documented list be used or that technologies from such a list be used It is confusing because it can also be read as the authors don t need to refer and or use the documented lists when choosing the technologies in order to conform to WCAG 2 0 Then the Documented lists of Web technologies with Accessibility Support won t b
119. w3 org Archives Public public comments wcag20 and may also include links to the relevant changes in the WCAG 2 0 Editor s Draft of May October 2007 at http www w3 org WAT GL WCAG20 WD WCAG20 20071102 Thank you for your time reviewing and sending comments Though we cannot always do exactly what each commenter requests all of the comments are valuable to the development of WCAG 2 0 Regards Loretta Guarino Reid WCAG WG Co Chair Gregg Vanderheiden WCAG WG Co Chair Michael Cooper WCAG WG Staff Contact On behalf of the WCAG Working Group Comment 1 about Accessibility Supported Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0317 html Issue ID 2172 In the description of Accessibility Supported in the section of Important New Terms Used 12 in WCAG 2 0 there is an Editorial Note which reads The W3C WAI will be compiling existing information on its technologies It is expected that other organizations will compile such information for their technologies There will undoubtedly be others who create documented lists as well It is irresponsible of WCAG WG to rely on the other organizations WCAG 2 0 is a guidelines which would be recommended by W3C WAI If WCAG 2 0 require authors to consult documented lists of technologies that are known to have accessibility support WCAG 2 0 itself should provide the documented lists If WCAG 2 0 would rely on other organization
120. 17011 e JIS Q 17021 JIS Q 17024 JIS Q 17030 JIS Q 17040 wield arcc PR ida JIS Q 17050 1 1 JIS Q 17050 2 2 JIS Q 9006 JIS X 0133 1 1 e JIS X 0133 2 2 JIS X 0133 3 3 JIS X 0133 4 4 JIS X 0133 5 5 JIS X 0133 6 6 JISZ9080 23
121. 4 1 Purpose Section 1194 2 Application 508 255 URL http teitac org wiki Task253 Functiona1 Performance Criteria FPC 14 IS09241 20 FPC FPC
122. 7 12 WCAG2 0 2 2 2008 2 1 W3C WAI 2 lt gt W3C WC H MER WCAG2 0 o 3 BN Stet Candidate Recommendation Call for Implementations Candidate Recommendation Last Call Working Draft 4 So 2 3 1 W3C 2 3 1 Proposed Recommendation b WCAG2 0
123. 9241 JIS Z85XX JIS 9241 20 JIS X JISC JISC X8341 1 TC159 JIS 9241 20 JENC INSTAC b JIS X8341 1 8341 4 D9241 20 X8341 1 2004 29241 20 X8341 1 2009 JIS X8341 1 2004 3 X8341 1 2004 2 X8341 1
124. Because individual authors will not usually be able to do all of the research necessary to determine which features of which Web technologies are actually supported by which versions of assistive technologies and user agents authors will usually rely on public documented lists of Web technologies that document which assistive technologies support which features of which Web technologies By public we only mean that the list and its documentation are public Anyone can create a publicly documented list of Web Technologies and their Accessibility Support People may create recommended documented lists of technologies and give them a name e g the XYZ Accessibility Coalition s 2007 Supported Technologies List that authors can use 14 As long as they are publicly documented authors or customers etc can easily select lists that meet their needs Customers or others can pick lists that fit their environment or language at any point in time and specify those to be used in creating their content Authors are strongly encouraged to choose lists that have an established reputation for accuracy and usefulness Developers are strongly encouraged to provide information about the accessibility support for their technologies The Working Group anticipates that only lists that provide accurate information and benefit both authors and users will achieve market recognition in the long term There is no requirement in WCAG that a public documente
125. UE Aud qo lib NN 2 4 2 5 3 1 f ME Jtr 2 4 3 bui M E MN Ln pic eM b 2 4 4 JIS X8341 JIS 23 JIS WG JIS X8341 2 5 WG4 2 5 1 JIS X834 2 2
126. Understandable Information and operation of user interface must be understandable by users 3 3 WCAG Level 2 0 H 3 1 Make text content readable and understandable De ls Dub 3 L 3 1 3 1 TS OU Ee Gila qe JJ np Sg TR lt We ici iF e ea xe Bll cR uS 1 A 2 AA 3 AAA 4 AAA 5 Reading Level AAA When text requires reading ability more advanced than the lower secondary education level supplemental content or an alternate version is available that does not require 32 PIS Ow NE WCAG Level 2 0 H reading ability more advanced than the lower secondary education level 3 1 6 Pronunciation AAA JIS A mechanism is available for identifying specific pronunciation of words where meaning is amb
127. Work B 1 Completion Maintenance of cibis standards B 2 Commitment to other organisation B 3 Other Source of standards ISO DIS 9241 20 ISO DIS 9241 171 C Technical Status C 3 Models Tools D Conformity Assessment and Interoperability D 1 Conformity Assessment D 2 Interoperability E Cultural and Linguistic Adaptability F Other Justification es __ No Xx Yes No Xx Yes Xx Localization is a one of the central issue TRA 4 2 NWIP BEER AS ISO IEC J TC 1 SC 35 N 1176 DATE 2007 08 20 ISO IEC JTC 1 SC 35 User Interfaces Secretariat AFNOR DOC TYPE NP BALLOT RESULTS TITLE NP BALLOT RESULTS New Work Item Proposal on Information Technology User Interfaces Accessibility functions for personal computers SOURCE SC 35 Secretary STATUS The NP is approved The Working Group to which this item is assigned will be responsible for preparing a disposition of the comments for the NP ballot ACTION ID DUE DATE DISTRIBUTION P and O members of JTC1 SC35 MEDIUM E NO OF PAGES 3 Reply to Secretariat ISO IEC JTC1 SC35 AFNOR Philippe Magnabosco 11 rue Francis de Pressens 93571 La Plaine Saint Denis Cedex France Telephone 33 1 41628502 Facsimile 33 1 49179305 E Mail philippe magnabosco afnor org Ballot Title New Work Item Proposal on Information Technology Accessibility functions for PCs Source SC35 Secretariat Distribution JTC 1
128. Xm 1 4 5 WG4 bp A Ml ci AL Zi DER m 20 3 L 1 4 ni JSA JBMIA fE EE iis 19 5 17 19 6 21 19 5 24 19 5 22 19 7 12 15 00 17 00 14 00 17 00 15 00 17 00 15 00 17 00 10 00 12 00 JSA802 JSA8O1 JSA201 JSA802 JBMIA UC e Iu D sc M i i uL i 9 20 2 29 19 10 12 19 10 1 CERE I9 4E 7 H 10H 19 9 6 14 00 17 00 14 00 17 00 15 00 17 00 14 00 17 00 195 30 15 230 Hi JSA203 JSA201 JSA201 Jsasol JSA202 ARE 19 12 6 19 12 27 19 9 20 19 9 21 14 00 16 30 10 00 12 00 14 00 17 00 9 30 12 00 20 2 26 19 10 18
129. a keyboard interface without requiring specific timings for individual keystrokes Provide users with disabilities enough time to read and use content vd IS Da Dn SO Eve Uis 5 OD A Blinking AA Content does not blink for more than three seconds or a method is available to stop all blinking content in the Web page TFET 3 Web Pausing AA Moving blinking scrolling or auto updating information can be paused by the user unless it is part of an activity where timing or movement is essential Moving content that is pure decoration can be stopped by the user my ec NE AT DU Biel A ON ar
130. accessibility design solutions of TM AME ICT equipment and services with users whose lcharacteristics reflect the targeted user a COA HME hl lgroups 4 4 Conformance If equipment or service is claimed to have met Ithe applicable recommendations in this ue International Standard then the procedures used to establish requirements and to evaluate the equipment or service shall be specified The level of detail of the specification is a matter of negotiation between the involved parties Annex B provides assistance in documenting conformance EZA a 5 3 Process The following activities should be performed to NOTE 3 Evaluation of accessibility design lsolutions includes obtaining user test results and other available forms of user feedback 5 6 C
131. al Version number 1 Vote in parallel with Joint technical work Committee interested in with technical work Note P Members voting 17 in favour out of 18 94 requirement gt 66 66 P Members having abstained are not counted in this vote Member bodies voting 1 negative votes out of 19 5 requirement lt 25 Approved Country Member Status Approval Disapproval Abstention Australia SA O Member X Belgium NBN P Member X Brazil ABNT P Member X Canada SCC P Member X China SAC P Member X Czech Republic CNI P Member X Denmark DS P Member X Finland SFS P Member X France AFNOR P Member X Germany DIN P Member X Ireland NSAI P Member X Italy UNI P Member X Japan JISC P Member X Korea Republic of KATS P Member X Malaysia DSM P Member X Netherlands NEN P Member X Poland PKN P Member X Portugal IPQ X Spain AENOR P Member X Sweden SIS P Member x Switzerland SNV P Member X Turkey TSE P Member X United Kingdom BSI Secretariat X USA ANSI P Member X P Member TOTALS 17 1 4 Total of P Members voting 18 TOTALS 18 I 5 A comment file was submitted with this vote France AFNOR P Member France AFNOR doc Japan JISC P Member Japan JISC doc Sweden SIS P Member Sweden SIS doc United Kingdom BSI Secretariat UnitedKingdom B SI doc 1 2 FDIS
132. alf with marked up heading elements 2 the benefits of markup on task completion time were greater for blind users and 3 the overall difference in response time between sighted and blind users diminished with sites that were appropriately marked up WCAG IBM Becky Gibson Web Becky Web http www comm twcu ac jp nabe UAI 20070519 nabe html Ajax Web b W3C WAT WCAG2 0 2007 12 WCAG2 0 2 INSTAC Vic Ca ics URL http www jsa or jp stdz instac commitee acc index html 2 3 3 a WCAG2 0 Last Call Working Draft JIS WCAG 2 0
133. d list be used or that only technologies from such a list be used The public documented lists are described only as a method to make an otherwise critical but somewhat complicated aspect of conformance easier for authors who are not themselves experts on assistive technology support or who just don t have the time to keep up with advances in mainstream and assistive technology support for each other Authors companies or others may wish to create and use their own lists of accessibility supported technologies and this is allowed in meeting WCAG Customers companies or others may however specify that technologies from a custom or public list be used See Appendix B Documenting Accessibility Support for a Web Technology Comment 3 What does accessibility support mean Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0319 html Issue ID 2174 In the Note 2 within the section of Understanding Accessibility Support it reads When a Web Technology is accessibility supported it does not imply that the entire technology must be supported Most technologies lack support for at least one feature When referring to accessibility support for a technology the support for specific aspects features and extensions should be cited if the technology as a whole is not accessibility supported We couldn t understand what WCAG WG want to mean by this It can also be read as if the
134. dapted for accessibility FR 7 6 Te The problems related with the memory are not taken into Add an item on memory named Memory account be The system should provide a way of recognising the user without having him or her writing a password example iris fingerprints and vocal recognition FR 9 1 4 Te If safety belongs to the scope of this document the section should be expanded if not it should be removed 1 3 JIS X8341 1 1809241 20 JIS X8341 1 Iso 9241 20 Sidi onn En H LL it M B x 3 1 a Design for accessibility should follow the principles of a Suitability for the widest range of use Suitability for the widest range of use involves designing with the objective of producing solutions that will be useful acceptable and available to the widest range of users within the user population taking account of their special abilities variations in their capabilities the diversity of their tasks and their differing environmental economic and social circumstances I i I b 1 Principles Design for accessibility should f
135. e needed at all In the last paragraph within the same section at the same time it reads Authors companies or others may wish to create and use their own lists of accessibility supported technologies This is the contradictory statements Proposed Change Add more clarification on what the documented lists are and for what they are needed We have added a section Understanding Documented Lists to the Understanding WCAG 2 0 document and provided a link from WCAG 2 0 to this section We clarified this section as well It now reads Understanding Documented lists of Web technologies with Accessibility Support Because individual authors will not usually be able to do all of the research necessary to determine which features of which Web technologies are actually supported by which versions of assistive technologies and user agents authors will usually rely on public documented lists of Web technologies that document which assistive technologies support which features of which Web technologies By public we only mean that the list and its documentation are public Anyone can create a publicly documented list of Web Technologies and their Accessibility Support People may create recommended documented lists of technologies and give them a name e g the XYZ Accessibility Coalition s 2007 Supported Technologies List that authors can use As long as they are publicly documented authors or customers etc can easily selec
136. e users to choose between alternate ways of performing tasks if appropriate 9 1 3 Providing user guidance The accessibility of user guidance should be comparable to the accessibility other functions of the ICT equipment or service 17 1 2 Supporting multiple interaction mechanisms ICT equipment and services should support as many alternate means of interaction as possible to support the accessibility needs of different lgroups of users 6 7 Adjusting speed of interaction Where possible the speed of interaction should be adjustable by the user AT o 10 2 Designing environments Special care should be taken to consider the
137. ed in the WG6 meeting and to have a suitable draft distributed to members of WG6 by the end of July 2008 The members of WG6 will then be asked to review it and provide comments by the end of August 2008 The new draft and any related comments will be discussed at the next meeting of WG6 in September 2008 Adopted by consensus Germany abstains 2 5 3 NWIP JTC1 SC35 NWIP ISO0 IEC29136 2 5 4 JIS X8341 2 PC GR AAO JIS JIS lt gt JTC1 SC35 JTC1 SC35
138. ed skins of the media players Aadditionally the authors can create the original interfaces without the volume controls for example by using Flash 1 2 Having stop button is not necessarily sufficient since the volume can be too loud In this case it is not an user agent issue but a web content issue which is under the authors control For the customized interface without the volume controls on them is it still unnecessary for WCAG 2 0 to require the mechanism of the audio volume control We just want to confirm that or a mechanism is available to control audio volume which can be set independently of the system volume in 1 4 2 addresses our concern or not 1 http www jvcmusic co jp tarako 2 http www kewpie co jp tarako Source http www w3 org mid 20060623095914 FE78 NABEG1ab twcu ac jp Issue ID LC 1322 Comment JIS X 8341 3 also addresses the importance of volume control It allows the users who are hard of hearing to adjust the volume of the audio Is it unnecessary for WCAG 2 0 to require the mechanism of the audio volume control JUS b b dass b Sound should be controllable by users Information Hearing impaired users cannot detect that sound is being played Also there are cases where louder volume is preferred Example To enable users to adjust volume play and stop provides controls for play stop and volume adjustment When using plugins they can be used for t
139. een magnifiers Other success criteria ensure that assistive technology can access the content successfully These new success criteria identify the author s responsibility when supporting users where direct access is more effective Note by the way that the success criteria don t require just scaling to 200 and 50 but to all the values between Our expectation is that solutions that work across that range will continue to work as well as possible beyond those limits This is explained in the Intent Section of Understanding SC 1 4 4 The Working Group welcomes suggestions for ways to make this information clearer Comment 6 How to measure dB A SPL and Tools Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0322 html Issue ID 2177 There should be the instructions on how to measure the volume in dB A SPL ItY 11 be helpful and useful if the working group could introduce any tools for the authors to measure the volume Proposed Change Add the instructions on how to measure the volume in dB A SPL Add the links to the tools Comment 7 Responsible for 200 and 50 Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0323 html Issue ID 2178 Original Comment It can be read as Authors have to provide a mechanism which allows the users to resize text up to 200 percent and down to 50 percent If it is NOT what the WCAG WG wa
140. ent and services should support users who cannot hear 7 3 7 Users with limited hearing ICT equipment and services should support users with limited hearing 7 4 3 Users that cannot speak ICT equipment and services should support users who cannot speak 7 4 4 Users with limited speech capabilities ICT equipment and services should support users with limited speech capabilities 7 5 1 Limited physical movement ICT equipment and services should support users who have limited physical movement 7 5 2 Providing adjustable location of controls The placement of controls and displays should be adjustable to heights and locations that the users can reach 7 5 4 Limiting physical force requirements Controls should be movable with the minimum force required within the constraints of the operation being performed 7 5 1 Limited physical movement ICT equipment and services should support users who have limited physical movement 7 5 2 Providing adjustable location of controls The placement of controls and displays should be adjustable to heights and locations that the users can reach 10 2 Designing environments Special care should be taken to consider the needs of users when designing b layout and use of space EXAMPLE Sufficient space is provided for wheelchair users to manoeuvre 7 5 3 Supporting either or only one hand Controls should be operable using either hand and should avoid the need for simultaneous use of both hand
141. ent or amendments to the following International Standard s a technical report type And which standard development track is recommended for the approved new work item X a Default Timeframe b Accelerated Timeframe c Extended Timeframe Relevant documents to be considered ISO DIS 9241 20 ISO DIS 9241 171 Co operation and liaison ISO TC159 SC4 Preparatory work offered with target date s already done Will the service of a maintenance agency or registration authority be required No f yes have you identified a potential candidate f yes indicate name Are there any known requirements for coding No If yes please specify on a separate page Does the proposed standard concern known patented items No f yes please provide full information in an annex Comments and recommendations of the JTC 1 or SC 35 Secretariat attach a separate page as an annex if necessary Comments with respect to the proposal in general and recommendations thereon lt is proposed to assign this new item to JTC 1 SC 35 Voting on the proposal Each P member of the ISO IEC joint technical committee has an obligation to vote within the time limits laid down normally three months after the date of circulation Date of circulation Closing date for voting Signature of Secretary 2007 XX XX 2007 XX XX NEW WORK ITEM PROPOSAL PROJECT ACCEPTANCE CRITERIA A 1 Market Requirement B B Related
142. es Public public comments wcag20 2007 Jun 0319 html 3 Issue ID 2074 In the Note 2 within the section of Understanding Accessibility Support it reads When a Web Technology is accessibility supported it does not imply that the entire technology must be supported Most technologies lack support for at least one feature When referring to accessibility support for a technology the support for specific aspects features and extensions should be cited if the technology as a whole is not accessibility supported We couldn t understand what WCAG WG want to mean by this It can also be read as if the one of the features for a technology is supported by a assistive technology the technology can be recognized as accessibility supported It could lead many conformant websites to be inaccessible in the reality Proposed Change Add more understandable clarification Received on We do not have any requirements for platforms per se but the description of accessibility support for a technology should note which platforms the technology has AT support on This is described in the section Understanding Accessibility Support in Understanding Conformance We have tried to make this clearer in the current version of Understanding Conformance in Understanding WCAG 2 0 in the section Documenting Accessibility support for a Web Technology Most Web technologies have some aspects that are not su
143. g is true 1 Reversible Transactions are reversible 2 Checked Submitted data is checked for input errors before going on to the next step in the process 3 Confirmed A mechanism is available for reviewing confirming and correcting information before finalizing the transaction 30 Level AA EO 949 EU S WAT JIS 3 5i AA WCAG 2 0 H 3 3 4 3 3 b 3 3 6 3 Level 2 my 0 0 4 eX
144. ggestions for ways to make this information clearer Comment 6 How to measure dB A SPL and Tools Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0322 html 18 Issue ID 2177 There should be the instructions on how to measure the volume in dB A SPL It 11 be helpful and useful if the working group could introduce any tools for the authors to measure the volume Proposed Change Add the instructions on how to measure the volume in dB A SPL Add the links to the tools Comment 7 Responsible for 200 and 50 Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0323 html Issue ID 2178 It can be read as Authors have to provide a mechanism which allows the users to resize text up to 200 percent and down to 50 percent If it is NOT what the WCAG WG wanted to say the documents need more clarification on this If it is what the WCAG WG wanted to say the user agents should be responsible for it Proposed Change Add the clarification on who should be responsible for 200 and 50 and what the authors have to do 19 This is explained in Understanding SC 1 4 7 see The scaling of content is primarily a user agent responsibility User agents that satisfy UAAG 1 0 Checkpoint 4 1 allow users to configure text scale The author s responsibility is to create Web content that does not prevent the user agent from scaling the content and
145. hanism To make it clearer what is meant by controlling the volume we have also reworded it as follows 1 4 2 Audio Turnoff If any audio plays automatically for more than 3 seconds either a mechanism is available to pause or stop the audio or a mechanism is available to control audio volume which can be set to a different level from the system volume level Level A 10 11 2 2 WCAG2 0 5 WD Dear JIS Thank you for your comments on the 17 May 2007 Public Working Draft of the Web Content Accessibility Guidelines 2 0 WCAG 2 0 http www w3 org TR 2007 WD WCAG20 20070517 The WCAG Working Group has reviewed all comments received on the May draft and will be publishing an updated Public Working Draft shortly Before we do that we would like to know whether we have understood your comments correctly and also whether you are satisfied with our resolutions Please review our resolutions for the following comments and reply to us by 19 November 2007 at public comments wcag20 w3 org to say whether you are satisfied Note that this list is publicly archived Note also that we are not asking for new issues nor for an updated review of the entire document at this time Please see below for the text of comments that you submitted and our resolutions to your comments Each comment includes a link to the archived copy of your original comment on http lists
146. his purpose Control of volume is a user agent issue Most players already have volume controls on them Content due to security issues usually cannot directly access the hardware volume control and thus can only turn volume down not up We therefore do not include a recommendation for content to also include a volume control though user agents should This belongs to the domain of User Agents and is covered in the User Agent guidelines UAAG 1 0 which reads as follows Guideline 4 Ensure user control of rendering User agents rendering audio have to allow the user to control the audio volume globally and to allow the user to control distinguishable audio tracks Proposed Change Response from Working Group said Control of volume is a user agent issue But 1 4 2 reads or a mechanism is available to control audio volume which can be set independently of the system volume Need more clarification on this issue Yes the situation that you describe is covered by SC 1 4 2 The author is responsible for making sure that there is some mechanism for the user to control the sound Often the mechanism is provided by the default behavior of the user agent In this example because the media player has been customized the volume controls on the media player are not available to the user so the author cannot rely on the default user agent provided mechanism to satisfy SC 1 4 2 The author would need to provide some other mec
147. hould be comparable to the accessibility other functions comparable to the accessibility of other functions of the ICT equipment or service of the ICT equipment or service the usage of the term all members is wrong Change all members to the widest possible range of users para second SE AnnexB Paragraph 5 both sentences FR Ge Considering that most of previous general and technical comments were not accepted for the DIS enquiry France maintains its previous negative vote for the FDIS vote FR Ge Too many sections are not specific to accessibility either in their recommendations and examples FR 4 2 Ed Encourages not applying for wrong design reasons Replace design objectives solutions by human center design objectives FR 5 1 After 1 Ed Add a note on the other hand it should be compatible alinea with the connection of assistive technologies FR 7 2 1 Te This section should start by stressing that graphical interfaces Start with graphical user interfaces are obviously not are huge problem for blind people an appropriate design solution for users with no vision 7 2 6 Limited colour vision has several facets Add a note explaining the various cases of limited colour visions Sign language interactions very useful for such populations are Include recommendations on sign language not mentioned All sign language interaction technologies are not necessarily part of assistive technologies and can be a
148. iguous without knowing the pronunciation oe MENU ENDE SG gt Make Web pages appear and operate in predictable ways Ui se pend EC 3 2 1 On Focus A qe mA Leur UD When any component receives focus it does not initiate a change of context lhover IEIR Ajax I 3 2 2 On Input A IH Changing the setting of any user interface 500 2 241 Level 1720 component does not automatically cause a JIS change of context unless the user has been advised of the behavior before using the component 33 WCAG 2 0 H 2 2 d 3 24 502 070 3 3 29 Level YER
149. in a manner that will aid understanding by users 7 6 6 Providing appropriate cues ICT equipment and services should provide appropriate cues to assist users in paying attention to important information e g control status 9 1 2 Maintaining consistency Related equipment or services should have common accessibility functions and specifications 8 2 Providing alternate ways of performing tasks ICT equipment and services should enable users to choose between alternate ways of performing tasks if appropriate 7 1 4 Supporting individualization ICT equipment and services should support individualization by users 7 1 5 Changing configurations A method that does not require users to reconfigure or restart the equipment or service should be provided to allow users to utilize alternative available means of interacting with ICT equipment or services and to select accessibility related settings 7 1 6 Returning to default configuration A method that does not require users to reconfigure or restart the equipment or service should be provided to allow users to reset an ICT equipment or service to its default configuration 7 1 7 Saving and retrieving customized configurations Where possible a means should be provided to save and retrieve a user s customized configuration c 6
150. interoperability ICT equipment and services intended to work with interrupt or invalidate any Z laccessibility related functions of these other ICT equipment and services D 9 9 4 1 Providing accessibility information So a Information about the accessibility of ICT I ear other ICT equipment or services should not equipment or services should be available in formats that can be used by people with widest range of capabilities ar 5 4 IEEE JJ MEAM 5 3 Process ld Evaluate
151. into a vertical column of words possibly clipped if the word itself is too large to fit into the available horizontal space on screen For vertical text similar problems occur Arbitrary resizing also introduces problems with testing How does an author know when he has satisfied the success criterion particularly for more sophisticated web pages that may change their layout based on the text size to produce more readable results An example would be a page that switches between single and multiple column text so that line widths stay within the 16 word range recommended for some cognitive learning and language disabilities So we felt that some choice of explicit values was necessary to make these success criteria testable 200 was chosen after experimenting with various web pages that the working group felt were well designed to see when scaling started to introduce problems We also looked at the scaling supported directly by popular browsers IE s largest text scaling factor is only about 180 And we looked at the support provided by screen magnifiers For older screen magnifiers 200 was the smallest scale factor that could be chosen 50 was chosen to provide symmetry in the ranges The ability to scale in both directions is desirable We believe that there is a range of visual disabilities that can best be addressed directly 6 and a range where the most effective solutions rely on assistive technology such as scr
152. item titled Information Technology User Interfaces Accessibility functions for personal computers WG6 SC35 requests the editor of Information Technology User Interfaces Accessibility functions for personal computers to create a new working draft and circulate it to the members of WG6 by January 15 2008 The new draft is to e Have all software guidelines removed from it e Have all non accessibility specific guidelines removed from it e Have a single clause requiring conformance with ISO 9241 20 and ISO 9241 171 e Have a comprehensive set of hardware specific accessibility requirement and recommendation clauses added to it e Be formatted and worded according to ISO Directives Part 2 It 1s expected that each of the requirements and recommendations in this draft will be able to be tested for conformance 25 Adopted by consensus Germany abstains 2 5 2 2 WD JTC1 SC35 PC
153. ly persons and persons with disabilities Visual signs and displays Specification of age related relative luminance and its use in assessment of light 2 JIS S0032 IS0 TC159 SC5 WG5 JIS 1S0 TC159 SC5 WG5 d a 1 NO O Me ured cu oak MR CENELEC ETSI Mandate376 CEN CENELBC fex ETSI Hi TB 1 1 2006 9 2007 7 Se CEN CENELEC WC CEN BT WG185
154. nt Magnetic Field and Acoustic Gain Requirements for Handset Telephone Intended for use by the Hard of Hearing ITU T P 130 FCC Acts to promote accessibility of digital wireless phones to individuals with hearing disabilities ANSI C63 19 Method of measurement for hearing aid compatibility with wireless communications status ANSI C63 20 Limits for hearing aid compatibility with wireless communications ITU T V 18 e ITU T E121 Pictograms symbols and icons to assist users of the telephone service ITU T E 134 Human factors aspects of public terminals generic operating procedures ITU T E 135 Human factors aspects of public telecommunication terminals for people with disabilities JBMS 71 JBMIA TR 10 22 JIS Q 0060 JIS Q 0067 JIS Q 1000 JISQ1001 JIS Q 17000 JIS Q
155. ntained by an open standards body such as the W3C The Web Content Accessibility Guidelines set guidelines to determine if a technology is accessibility supported 13 Comment 2 Discussion of Documented lists needs clarification Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0318 html Issue ID 2173 In the section of Understanding Documented lists of Web technologies with Accessibility Support it reads There is no requirement in WCAG that a documented list be used or that technologies from such a list be used It is confusing because it can also be read as the authors don t need to refer and or use the documented lists when choosing the technologies in order to conform to WCAG 2 0 Then the Documented lists of Web technologies with Accessibility Support won t be needed at all In the last paragraph within the same section at the same time it reads Authors companies or others may wish to create and use their own lists of accessibility supported technologies This is the contradictory statements Proposed Change Add more clarification on what the documented lists are and for what they are needed We have added a section Understanding Documented Lists to the Understanding WCAG 2 0 document and provided a link from WCAG 2 0 to this section We clarified this section as well It now reads Understanding Documented lists of Web technologies with Accessibility Support
156. nted to say the documents need more clarification on this If it is what the WCAG WG wanted to say the user agents should be responsible for it Proposed Change Add the clarification on who should be responsible for 200 and 50 and what the authors have to do This is explained in Understanding SC 1 4 7 see The scaling of content is primarily a user agent responsibility User agents that satisfy UAAG 1 0 Checkpoint 4 1 allow users to configure text scale The author s responsibility is to create Web content that does not prevent the user agent from scaling the content and that allows the reflow of the content within the current width of the viewport Comment 8 Sound Volume Control Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0330 html Issue ID 2185 In 1 4 2 now it reads or a mechanism is available to control audio volume which can be set independently of the system volume This seems to address our comment which said Is it unnecessary for WCAG 2 0 to require the mechanism of the audio volume control But Response from Working Group seems to reject our sugestion Just to confirm JIS WG still would like WCAG 2 0 to require the mechanism of the audio volume 8 control Most media players already have volume controls on them However most of their interfaces can also be customized by the developers and the volume controls can be hidden in such customiz
157. ollow the principles of b Equitable use Achieving equitable use will ensure that solutions designed to increase accessibility do not result in loss of privacy increased risks to personal safety or security or the stigmatisation of individuals and that solutions provide the same means of use for all users that are identical whenever possible a ICT equipment and services should support users who do not have vision or who are unable to see due to environmental conditions 7 2 6 Users with limited vision ICT equipment and services should support users with limited vision b h Oa 7 3 3 Users that cannot hear ICT equipm
158. one of the features for a technology is supported by a assistive technology the technology can be recognized as accessibility supported It could lead many conformant websites to be inaccessible in the reality Proposed Change Add more understandable clarification 15 Received on We do not have any requirements for platforms per se but the description of accessibility support for a technology should note which platforms the technology has AT support on This is described in the section Understanding Accessibility Support in Understanding Conformance We have tried to make this clearer in the current version of Understanding Conformance in Understanding WCAG 2 0 in the section Documenting Accessibility support for a Web Technology Most Web technologies have some aspects that are not supported So complete support is rare if it occurs at all The description of accessibility support will provide information on how much support is provided for various features within technologies Decisions about which features of technologies can be used are accessibility supported can then be made based on these reports Comment 4 Why 18 point or 14 point bold Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0320 html Issue ID 2175 It reads 18 point text or 14 point bold text is judged to be large enough to require a lower contrast ratio in the second paragraph of the In
159. or some cognitive learning and language disabilities So we felt that some choice of explicit values was necessary to make these success criteria testable 200 was chosen after experimenting with various web pages that the working group felt were well designed to see when scaling started to introduce problems We also looked at the scaling supported directly by popular browsers IE s largest text scaling factor is only about 180 And we looked at the support provided by screen magnifiers For older screen magnifiers 200 was the smallest scale factor that could be chosen 50 was chosen to provide symmetry in the ranges The ability to scale in both directions is desirable We believe that there is a range of visual disabilities that can best be addressed directly and a range where the most effective solutions rely on assistive technology such as screen magnifiers Other success criteria ensure that assistive technology can access the content successfully These new success criteria identify the author s responsibility when supporting users where direct access is more effective Note by the way that the success criteria don t require just scaling to 200 and 50 but to all the values between Our expectation is that solutions that work across that range will continue to work as well as possible beyond those limits This is explained in the Intent Section of Understanding SC 1 4 4 The Working Group welcomes su
160. pported So complete support is rare if it occurs at all The description of accessibility support will provide information on how much support is provided for various features within technologies Decisions about which features of technologies can be used are accessibility supported can then be made based on these reports Comment 4 Why 18 point or 14 point bold source http lists w3 org Archives Public public comments wcag20 2007 Jun 0320 html Issue ID 2175 It reads 18 point text or 14 point bold text is judged to be large enough to require a lower contrast ratio in the second paragraph of the Intent of this Success Criterion But we couldn t understand the reason why the working group judge that 18 point text or 14 point bold text is large enough to require a lower contrast ratio Are these sizes applied to the characters in any other languages such as CJK languages We need the rationale or the ground on 18 point text or 14 point bold text in order to determine if it would also make sense in the Japanese characters Proposed Change Add the more concrete reason why 18 point text or 14 point bold text is judged to be large enough to require a lower contrast ratio These numbers were worked out with assistance from the Lighthouse International http lighthouse org an organization in the US that does research on low vision To handle other languages we have changed the note to read la
161. rger scale text with at least 18 point or 14 point bold or font size that would yield equivalent stroke width for Chinese Japanese and Korean CJK fonts Note 1 Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read especially at lower contrast levels Note 2 Font size is the size when the content is delivered It does not include resizing that may be done by a user Note 3 The actual size of the character that a user sees in dependent both on the author defined size and the users display or user agent settings This success criterion is based on common pixel sizes available today Users who have low vision would be responsible for choosing appropriate settings Comment 5 Rationale for 200 and 50 Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0321 html Issue ID 2176 We need more concrete reason rationale on why 200 percent and 50 percent were chosen by the WCAG WG Without the reason rationale we won t be able to determine if 200 percent and 50 percent can be applied to the Japanese characters Proposed Change Add more concrete rationale for why 200 and 50 As text is scaled larger and larger it becomes impossible to prevent loss of content or functionality When horizontal text is enlarged beyond a certain level text wrapping algorithms turn the text
162. s i F a 4 4 1 i 7 5 1 Limited physical movement ICT equipment and services should support users who have limited physical movement 7 5 2 Providing adjustable location of controls The placement of controls and displays should be adjustable to heights and locations that the users can reach 7 6 1 Limitations in cognitive capabilities ICT equipment and services should support users who have limitations in their cognitive ICT equipment and services should avoid unnecessarily high cognitive demands on users by ensuring that the basic activities required to operate the equipment or to use the service are as straightforward and simple as possible 7 6 10 Supporting cultural and linguistic differences The vocabulary used to describe and operate ICT equipment and services should use expressions that can be understandable by users with differences in culture or language 7 6 9 Minimizing the need for training Design of ICT equipment and services should
163. s ISO IEC Guide71 DE 2 3 4 5 DTR 2006 12 8 gt DIR 2006 12 8 10 2 1 2007 3 7 BS 0 SEMEL DTR 22411 822 TC 159 221 TC159 N544 221 TC 159 WG 2 TR 22411 2007 10 31 B DTR 22411 amp TC 159 ISO
164. s WCAG WG should create the test files for each technologies so that other organizations will be able to compile such information based on the same level of the measure The documented lists for any languages should be created by using the same test files and the same test procedure with the same measure Without those materials JIS WG or any other organization in Japan won t be able to do anything Even if some organization would create the lists it could be unreliable information and the sites based on such information could be inaccessible to the users in reality For any other languages than English this must be one of the big concerns Additionaly the format for the documented lists should be provided to ensure the consistency across the languages Proposed Change Develop and Provide the test files and the measure for the documented lists on Accessibility Supported technologies Provide the format for the documented lists Not rely on the other organizations than W3C as WCAG 2 0 is one of the W3C guidelines WCAG will be providing the format for a documented list We cannot document all versions of all technologies for all languages by ourselves however It is simply too much work and there are not sufficient resources Also it would not make sense to duplicate or turn away good research by others It is beyond the WCAG WG charter to document all technologies in particular proprietary technologies that are not mai
165. s either a mechanism is available to pause or stop the audio or a mechanism is available to control audio volume which can be set independently of the system volume 3 1 4 3 Contrast Minimum AA JIS Text and images of text have a contrast ratio of at least 5 1 except if the text is pure decoration Larger scale text or images of text can have a contrast ratio of 3 1 5 1 3 1 26 1 WCAG 2 0 1 4 4 1 4 5 1 4 6 1 4 7 Resize text Visually rendered text can be resized without assistive technology up to 200 percent and down to 50 percent without loss of content or functionality
166. set independently of the system volume in 1 4 2 addresses our concern or not 20 1 http www jvcmusic co jp tarako 2 http www kewpie co jp tarako Comment 9 Source http www w3 org mid 20060623095914 FE78 NABE lab twcu ac jp Issue ID LC 1322 Comment JIS X 8341 3 also addresses the importance of volume control It allows the users who are hard of hearing to adjust the volume of the audio Is it unnecessary for WCAG 2 0 to require the mechanism of the audio volume control JIS 5 7 b says b Sound should be controllable by users Information Hearing impaired users cannot detect that sound is being played Also there are cases where louder volume is preferred Example To enable users to adjust volume play and stop provides controls for play stop and volume adjustment When using plugins they can be used for this purpose Control of volume is a user agent issue Most players already have volume controls on them Content due to security issues usually cannot directly access the hardware volume control and thus can onlyturn volume down not up We therefore do not include a recommendation for content to also include a volume control though user agents should This belongs to the domain of User Agents and is covered in the User Agent guidelines UAAG 1 0 which reads as follows Guideline 4 Ensure user control of rendering User agents rendering audio have to allow 21 the user
167. t lists that meet their needs Customers or others can pick lists that fit their environment or language at any point in time and specify those to be used in creating their content Authors are strongly encouraged to choose lists that have an established reputation for accuracy and usefulness Developers are strongly encouraged to provide information about the accessibility support for their technologies The Working Group anticipates that only lists that provide accurate information and benefit both authors and users will achieve market recognition in the long term There is no requirement in WCAG that a public documented list be used or that only technologies from such a list be used The public documented lists are described only as a method to make an otherwise critical but somewhat complicated aspect of conformance easier for authors who are not themselves experts on assistive technology support or who just don t have the time to keep up with advances in mainstream and assistive technology support for each other Authors companies or others may wish to create and use their own lists of accessibility supported technologies and this is allowed in meeting WCAG Customers companies or others may however specify that technologies from a custom or public list be used See Appendix B Documenting Accessibility Support for a Web Technology Comment 3 What does accessibility support mean source http lists w3 org Archiv
168. tent of this Success Criterion But we couldn t understand the reason why the working group judge that 18 point text or 14 point bold text is large enough to require a lower contrast ratio Are these sizes applied to the characters in any other languages such as CJK languages We need the rationale or the ground on 18 point text or 14 point bold text in order to determine if it would also make sense in the Japanese characters Proposed Change Add the more concrete reason why 18 point text or 14 point bold text is judged to be large enough to require a lower contrast ratio 16 These numbers were worked out with assistance from the Lighthouse International http lighthouse org an organization in the US that does research on low vision To handle other languages we have changed the note to read larger scale text with at least 18 point or 14 point bold or font size that would yield equivalent stroke width for Chinese Japanese and Korean CJK fonts Note 1 Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read especially at lower contrast levels Note 2 Font size is the size when the content is delivered It does not include resizing that may be done by a user Note 3 The actual size of the character that a user sees in dependent both on the author defined size and the users display or user agent settings
169. that allows the reflow of the content within the current width of the viewport Comment 8 Sound Volume Control Source http lists w3 org Archives Public public comments wcag20 2007 Jun 0330 html Issue ID 2185 In 1 4 2 now it reads or a mechanism is available to control audio volume which can be set independently of the system volume This seems to address our comment which said Is it unnecessary for WCAG 2 0 to require the mechanism of the audio volume control But Response from Working Group seems to reject our sugestion Just to confirm JIS WG still would like WCAG 2 0 to require the mechanism of the audio volume control Most media players already have volume controls on them However most of their interfaces can also be customized by the developers and the volume controls can be hidden in such customized skins of the media players Aadditionally the authors can create the original interfaces without the volume controls for example by using Flash 1 2 Having stop button is not necessarily sufficient since the volume can be too loud In this case it is not an user agent issue but a web content issue which is under the authors control For the customized interface without the volume controls on them is it still unnecessary for WCAG 2 0 to require the mechanism of the audio volume control We just want to confirm that or a mechanism is available to control audio volume which can be
170. to control the audio volume globally and to allow the user to control distinguishable audio tracks Proposed Change Response from Working Group said Control of volume is a user agent issue But 1 4 2 reads or a mechanism is available to control audio volume which can be set independently of the system volume Need more clarification on this issue Yes the situation that you describe is covered by SC 1 4 2 The author is responsible for making sure that there is some mechanism for the user to control the sound Often the mechanism is provided by the default behavior of the user agent In this example because the media player has been customized the volume controls on the media player are not available to the user so the author cannot rely on the default user agent provided mechanism to satisfy SC 1 4 2 The author would need to provide some other mechanism To make it clearer what is meant by controlling the volume we have also reworded it as follows 1 4 2 Audio Turnoff If any audio plays automatically for more than 3 seconds either a mechanism is available to pause or stop the audio or a mechanism is available to control audio volume which can be set to a different level from the system volume level Level A 22 2 3 WCAG2 0 JIS 2007 5 1 WCAG2 0WD 2007 5 17 JIS e Web Content Accessibility Guidelines 2 0 W3C Working Draft 17 Ma
171. ustable location of controls The placement of controls and displays should be adjustable to heights and locations that the users can reach 7 5 4 Limiting physical force requirements Controls should be movable with the minimum force required within the constraints of the operation being performed 1 5 6 Compensating for limitations in fine motor control capabilities Controls should be designed to compensate for limitations in fine motor control e g tremors capabilities 2 8 2 Providing alternate ways of performing tasks IICT equipment and services should enable users to choose between alternate ways of performing tasks if appropriate 3 All 17 1 7 Saving and retrieving customized lconfigurations Where possible a means should be provided to save and retrieve a user s customized lconfiguration 7 5 7 Providing user control of response timing GS 915 x If a task requires users to make responses e g
172. ve technologies 41 4 1 1 Parsing A Content implemented using markup languages has elements with complete start and end tags except as allowed by their specifications and are nested according to their specifications 37 JIS5 la 1 EFK WCAG 2 0 d 1 JR sla Name Role Value For all user interface components the name and role can be programmatically determined states properties and values that can be set by the user can be programmatically determined and programmatically set and notification of changes to these items is available to user agents including assistive technologies lt No PR eR nee
173. y 2007 e Diff marked version showing revisions since 27 April 2006 Principle 1 Perceivable Information and user interface components must be perceivable by users 1 1 WCAG 2 0 Level JER 1 1 Provide text alternatives for any non text content so that it can be changed into other forms people need such as large print braille speech symbols or simpler language 1 1 5 0 0 GRAM GERD S SM il A 1 2 Provide synchronized alternatives for multimedia 1 2 1 2 1 Captions Prerecorded A JIS chk prerecorded live Captions are provided for prerecorded DX 81 23 Z2 V v multimedia except for multimedia alternatives to text that are clearly labeled as such
Download Pdf Manuals
Related Search