Prttype f EN 301 549 Decisin tree Lïc Martínez Nrmand. Universidad Plitécnica de Madrid. lic@fi.upm.es 1 Intrductin EN 301 549 cntains accessibility requirements that can be applied t any type f ICT prduct and service. Fr that it has been structured accrding t a feature-based apprach, and each requirement (and recmmendatin) cntains applicability language ( self-scping r pre-cnditins). This language is intended t identify whether each clause applies t any given ICT prduct r service. This feature-based apprach can be used as a supprt mechanism t determine the applicability f the EN requirements and recmmendatins. A decisin tree has been designed fr that purpse. Initially, the tree cntained a questin fr any self-scping text, but it was discvered, after a usability test, that the resulting tree was t large t be useful. The prttype presented as a demnstratin in the ETSI HF Wrkshp shws the result f refining this decisin tree s that it nly cntains questins that have effect n the applicability f at least tw requirements r recmmendatins. This apprach has cnsiderably reduced the size f the tree t a maximum f 25 questins. The prttype shws the behaviur f the decisin tree. It is nt intended t represent a prper user interface with gd levels f usability. The user interface is being develped in the Technical University f Madrid and will include the decisin tree shwn here. 2 The decisin tree The decisin tree has been designed t minimize the number f questins that need t be answered in rder t btain a set f requirements t be cnsidered fr a given ICT prducts f services. By design, the decisin tree nly cntains questins related t at least tw requirements. This implies that the list f applicable requirements resulting frm the use f the decisin tree will prbably cntain sme requirements that might nt apply t a particular ICT prduct r services. Belw is an verview f the current versin f the decisin tree, which may cntain sme mistakes as it is still under testing prcesses. This decisin tree represents wrk in prgress, that culd be refined in the future. 2.1 Always applicable requirements There are sme generic requirements that have t be cnsidered fr any ICT prduct r services, as the decisin tree cntains n questins fr them: 5.2 Activatin f accessibility features 5.3 Bimetrics 5.4 Preservatin f accessibility infrmatin during cnversin 5.7 Key repeat 5.8 Duble-strike key acceptance 5.9 Simultaneus user actins 2.2 Clsed functinality Sme requirements and recmmendatins f clause 5 apply if the system has clsed functinality, that is, if assistive technlgies cannt be cnnected r installed. In that case the applicability f requirements and 1
recmmendatins depends n whether visual infrmatin is needed, n whether there are auditry r speech utputs used t replace visual infrmatin, and n whether the functinality is clsed t keybards. The decisin tree fr clsed functinality is the fllwing (questins are highlighted in bld and have an identifier t enable crss-referencing): Des the ICT have clsed functinality? [Q1] 5.1.2.1 Clsed functinality 5.1.2.2 Assistive technlgy 5.1.4 Functinality clsed t text enlargement 5.1.5 Visual utput fr auditry infrmatin Is visual infrmatin needed t enable the use f thse functins f ICT that are clsed t assistive technlgies fr screen reading? [Q1.1] 5.1.3.1 General (nn-visual access) 5.1.3.16 Receipts, tickets and transactinal utputs Is auditry utput prvided as nn-visual access t clsed functinality? [Q1.1.1] 5.1.3.2 Auditry putput delivery including speech 5.1.3.3 Auditry utput crrelatin 5.1.3.8 Masked entry 5.1.3.9 Private access t persnal data 5.1.3.10 Nn-interfering audi utput 5.1.3.11 Private listening vlume 5.1.3.12 Speaker vlume 5.1.3.13 Vlume reset Is speech utput prvided as nn-visual access t clsed functinality? [Q1.1.1.1] 5.1.3.4 Speech utput user cntrl 5.1.3.5 Speech utput autmatic interruptin 5.1.3.6 Speech utput fr nn-text cntent 5.1.3.7 Speech utput fr vide infrmatin 5.1.3.14 Spken languages 5.1.3.15 Nn-visual errr identificatin Is ICT functinality clsed t keybards r keybard interfaces? [Q1.2] 5.1.6.1 Clsed functinality (peratin withut keybard interface) 5.1.6.2 Input fcus (peratin withut keybard interface) The first questin (Q1) is very imprtant fr the decisin tree, as its answer is als used as an answer fr sme derived questins related t tw-way vice cmmunicatin and sftware. 2.3 Operable parts and lcking r tggle cntrls The requirements under clause 5.5 apply if the ICT has perable parts (hardware- r sftware-based) and the requirements under clause 5.6 apply if the ICT has lcking r tggle cntrls: Des the ICT have perable parts? [Q2] 5.5.1 Means f peratin 5.5.2 Operable parts discernibility Des the ICT have a lcking r tggle cntrl? [Q3] 5.6.1 Tactile r auditry status (lcking r tggle cntrls) 5.6.2 Visual status (lcking r tggle cntrls) 2
2.4 Tw-way vice cmmunicatin If the ICT prvides tw-way vice cmmunicatin, then the requirements and recmmendatins f clause 6 apply as well as the requirements related t access t relay and emergency systems. The applicability f requirements and recmmendatins f clause 6 depends n whether the ICT has RTT capabilities and whether it includes real-time vide cmmunicatin. And there is ne questin (whether r nt the ICT supprts assistive technlgies, Q4.1.1) whse answer is derived as the negatin f the answer t Q1 (see sectin 2.2) and that will nt be asked t the user. Des the ICT prvide tw-way vice cmmunicatin? [Q4] 6.1 Audi bandwidth fr speech 6.2.1.1 RTT Prvisin 6.2.1.2 Cncurrent vice and text 6.3 Caller ID 6.4 Alternatives t vice-based services 13.2 Access t relay services 13.3 Access t emergency services Des the ICT have RTT capabilities? [Q4.1] 6.2.2.1 Visually distinguishable display 6.2.3 Interperability 6.2.4 Real-time text respnsiveness Des the ICT supprt assistive technlgies (i.e. it is nt clsed)? [Q4.1.1 = nt Q1)] 6.2.2.2 Prgrammatically determinable send and receive directin Des the ICT include real-time vide functinality? [Q4.2] 6.5.2 Reslutin 6.5.3 Frame rate 6.5.4 Synchrnizatin between audi and vide 6.6 Alternatives t vide-based services 2.5 Vide functinality The requirements and recmmendatins f clause 7 nly apply if the ICT has vide capabilities, such as playing, transmitting, cnverting r recrding vide cntent: Des the ICT have vide capabilities (playing, transmitting, cnverting r recrding)? [Q05] 7.1.1 Captining playback 7.1.2 Captining synchrnizatin 7.1.3 Preservatin f captining 7.2.1 Audi descriptin playback 7.2.2 Audi descriptin synchrnizatin 7.2.3 Preservatin f audi descriptin 7.3 User cntrls fr captins and audi descriptin 2.6 Hardware The requirements and recmmendatins f clause 8 f the EN apply if the ICT is hardware r if the ICT has hardware cmpnents. There are three subsets f requirements and recmmendatins: fr ICT that has speech utput, fr ICT that has physical dimensins that are integral t the ICT and that may restrict physical access, and finally, fr ICT that has mechanically perable parts. Is the ICT hardware r des the ICT has hardware? [Q6] 8.1.2 Standard cnnectins 3
8.1.3 Clur 8.3.5 Installatin instructins 8.4.3 Keys, tickets and fare cards 8.5 Tactile indicatin f speech mde Has the ICT hardware speech utput? [Q6.1] 8.2.1.1 Speech vlume range 8.2.1.2 Incremental vlume cntrl 8.2.2.1 Fixed-line devices 8.2.2.2 Wireless cmmunicatin devices Des the ICT have physical dimensins that are integral t the ICT and that may restrict physical access? [Q6.2] 8.3.2.1 Change in level? 8.3.2.2 Clear flr r grund space 8.3.2.3.1 General (apprach) 8.3.2.3.2 Frward apprach 8.3.2.3.3 Parallel apprach 8.3.2.4 Knee and te clearance width 8.3.2.5 Te clearance 8.3.2.6 Knee clearance 8.3.3.1.1 Unbstructed high frward reach 8.3.3.1.2 Unbstructed lw frward reach 8.3.3.1.3.1 Clear flr space (bstructed reach) 8.3.3.1.3.2 Obstructed (<510 mm) frward reach 8.3.3.1.3.3 Obstructed (< 635 mm) frward reach 8.3.3.2.1 Unbstructed high side reach 8.3.3.2.2 Unbstructed lw side reach 8.3.3.2.3.1 Obstructed (<= 255 mm) side reach 8.3.3.2.3.2 Obstructed (<= 610 mm) side reach 8.3.4 Visibility Des the ICT have mechanically perable parts? [Q6.3] 8.4.1 Numeric keys 8.4.2.1 Means f peratin f mechanical parts 8.4.2.2 Frce f peratin f mechanical parts 2.7 Web The requirements f clause 9 apply t web pages, including dcuments and sftware that are web pages, r that are part f web pages. The requirements f clause 9 are the level A and AA success criteria frm the W3C Web Cntent Accessibility Guidelines (WCAG 2.0): Is the ICT a web page r des the ICT have web pages? [Q7] 9.2.1 Nn-text cntent 9.2.2 Audi-nly and vide-nly (pre-recrded) 9.2.3 Captins (pre-recrded) 9.2.4 Audi descriptin r media alternative (pre-recrded) 9.2.5 Captins (live) 9.2.6 Audi descriptin (pre-recrded) 9.2.7 Inf and relatinships 9.2.8 Inf and relatinships 4
9.2.9 Sensry characteristics 9.2.10 Use f clur 9.2.11 Audi cntrl 9.2.12 Cntrast (minimum) 9.2.13 Resize text 9.2.14 Images f text 9.2.15 Keybard 9.2.16 N keybard trap 9.2.17 Timing adjustable 9.2.18 Pause, stp, hide 9.2.19 Three flashes r belw threshld 9.2.20 Bypass blcks 9.2.21 Page titled 9.2.22 Fcus rder 9.2.23 Link purpse 9.2.24 Multiple ways 9.2.25 Headings and labels 9.2.26 Fcus visible 9.2.27 Language f page 9.2.28 Language f parts 9.2.29 On fcus 9.2.30 On input 9.2.31 Cnsistent navigatin 9.2.32 Cnsistent identificatin 9.2.33 Errr identificatin 9.2.34 Labels r instructins 9.2.35 Errr suggestin 9.2.36 Errr preventin (legal, financial, data) 9.2.37 Parsing 9.2.38 Name, rle, value 9.3 WCAG 2.0 cnfrmance requirements 2.8 Nn-web dcuments The requirements and recmmendatins f clause 10 apply t nn-web dcuments. Clause 10 cntains WCAG-derived requirements and tw additinal recmmendatins related t psitining f captins and t timing f audi descriptins: Is the ICT a nn-web dcument r des the ICT have nn-web dcuments? [Q8] 10.2.1 Nn-text cntent 10.2.2 Audi-nly and vide-nly (pre-recrded) 10.2.3 Captins 10.2.4 Audi descriptin r media alternative (pre-recrded) 10.2.5 Captins (live) 10.2.6 Audi descriptin (pre-recrded) 10.2.7 Inf and relatinships 10.2.8 Meaningful sequence 10.2.9 Sensry characteristics 10.2.10 Use f clur 5
10.2.11 Audi cntrl 10.2.12 Cntrast (minimum) 10.2.13 Resize text 10.2.14 Images f text 10.2.15 Keybard 10.2.16 N keybard trap 10.2.17 Timing adjustable 10.2.18 Pause, stp, hide 10.2.19 Three flashes r belw threshld 10.2.21 Dcument titled 10.2.22 Fcus rder 10.2.23 Link purpse (in cntext) 10.2.25 Headings and labels 10.2.26 Fcus visible 10.2.27 Language f page 10.2.28 Language f parts 10.2.29 On fcus 10.2.30 On input 10.2.33 Errr identificatin 10.2.34 Labels r instructins 10.2.35 Errr suggestin 10.2.36 Errr preventin (legal, financial, data) 10.2.37 Parsing 10.2.38 Name, rle, value 10.2.39 Captin psitining 10.2.40 Audi descriptin timing 2.9 Sftware The requirements f clause 11 apply in principle t any type f sftware. Clause 11.2 applies t nn-web sftware, with sme requirements applying r nt depending n whether the nn-web sftware has clsed functinality. Then there are requirements in clause 11.3 dealing with the interperability with assistive technlgies. Finally, there are sme requirements that nly apply t sftware that is an authring tl. Is the ICT sftware r des the ICT have sftware? [Q9] 11.3.2.04 Assistive technlgies 11.4.2 N disruptin f accessibility features 11.5 User preferences Is it nn-web sftware that prvides a user interface? [Q9.1] 11.2.1.03 Captins (pre-recrded) 11.2.1.05 Captins (live) 11.2.1.06 Audi descriptin (pre-recrded) 11.2.1.09 Sensry characteristics 11.2.1.10 Use f clur 11.2.1.11 Audi cntrl 11.2.1.12 Cntrast (minimum) 11.2.1.17 Timing adjustable 11.2.1.18 Pause, stp, hide 11.2.1.19 Three flashes r belw threshld 6
11.2.1.22 Fcus rder 11.2.1.23 Link purpse (in cntext) 11.2.1.25 Headings and labels 11.2.1.26 Fcus visible 11.2.1.29 On fcus 11.2.1.30 On input 11.2.1.34 Labels r instructin 11.2.1.35 Errr suggestin 11.2.1.36 Errr preventin (legal, financial, data) Des the nn-web sftware have functinality that supprts access t assistive technlgies (i.e. it is nt clsed)? [Q9.1.1 = nt Q1)] 11.2.1.1 Nn-text cntent (screen reading supprted) 11.2.1.2 Audi-nly and vide-nly (pre-recrded) 11.2.1.4 Audi descriptin r media alternative (pre-recrded) 11.2.1.7 Inf and relatinships 11.2.1.8 Meaningful sequence 11.2.1.13 Resize text 11.2.1.14 Images f text 11.2.1.15 Keybard 11.2.1.16 N keybard trap 11.2.1.27 Language f sftware 11.2.1.33 Errr identificatin 11.2.1.37 Parsing 11.2.1.38 Name, rle, value Des the nn-web sftware have clsed functinality? [Q9.1.2 = Q1)] 11.2.2.1 Nn-text cntent 11.2.2.2.1 Pre-recrded audi-nly 11.2.2.2.2 Pre-recrded vide nly 11.2.2.4 Audi descriptin r media alternative (pre-recrded) 11.2.2.7 Inf and relatinships 11.2.2.8 Meaningful sequence 11.2.2.13 Resize text 11.2.2.14 Images f text 11.2.2.15 Keybard 11.2.2.27 Language f sftware 11.2.2.33 Errr Identificatin 11.2.2.37 Parsing 11.2.2.38 Name, rle value Is it platfrm sftware? [Q9.2] 11.3.2.1 Platfrm accessibility service supprt fr sftware that prvides a user interface 11.3.2.2 Platfrm accessibility service supprt fr assistive technlgies 11.4.1 User cntrl f accessibility features Des the sftware supprts access t assistive technlgies (i.e. it is nt clsed)? [Q9.3 = nt Q1] 11.3.2.03 Use f accessibility services 11.3.2.05 Object infrmatin 7
11.3.2.06 Rw, clumn, and headers 11.3.2.07 Values 11.3.2.08 Label relatinships 11.3.2.09 Parent-child relatinships 11.3.2.10 Text 11.3.2.11 List f available actins 11.3.2.12 Executin f available actins 11.3.2.13 Tracking f fcus and selectin attributes 11.3.2.14 Mdificatin f fcus and selectin attributes 11.3.2.15 Change ntificatin 11.3.2.16 Mdificatins f states and prperties 11.3.2.17 Mdificatins f values and text Des the nn-web sftware have clsed functinality? [Q9.4 = Q1] 11.3.1 Clsed functinality (interperability with assistive technlgy) Is the ICT an authring tl? [Q9.5] 11.6.1 Cntent technlgy 11.6.2 Accessible cntent creatin 11.6.3 Preservatin f accessibility infrmatin in transfrmatins 11.6.4 Repair assistance 11.6.5 Templates In this sectin f the decisin tree, there are questins whse answer is derived frm the answer t Q1 (see sectin 2.2) and that will nt be asked t the user. Questins Q9.1.1 and Q9.4 will have the same answer as Q1. Questins Q9.1.2 and Q9.3 will have the ppsite answer. 2.10 Dcumentatin and supprt services The requirements in clause 12.1 apply t prduct dcumentatin and the requirements in clause 12.2 apply t the supprt services f the ICT: Des the ICT have prduct dcumentatin? [Q10] 12.1.1 Accessibility and cmpatibility features 12.1.2 Accessible dcumentatin Des the ICT have supprt services? [Q11] 12.2.2 Infrmatin n accessibility and cmpatibility services 12.2.3 Effective cmmunicatin 12.2.4 Accessible dcumentatin 2.11 Relay services The requirements in clause 13.1 apply t ICT that is intended t prvide relay services: Is the ICT intended t prvide relay services? [Q12] 13.1.2 Text relay services 13.1.3 Sign relay services 13.1.4 Lip-reading relay services 13.1.5 Captined telephny services 13.1.6 Speech t speech relay services 8
3 The prcess f using the implemented decisin tree The tree described in sectin 2 has been implemented in a sftware prttype. The flw f actins using the prttype is very simple: 1. The user writes the name f an ICT prduct r service 2. The user answers each questin f the decisin tree. At each step, the next questin t be presented depends n the answer given t the current questin. The system will be displaying the answers given by the user and the set f applicable clauses (requirements r recmmendatins). 3. Once all questins have been answered, the system cpies the data (answers and applicable clauses) t the clipbard and stps. 4 An example The user defines MyApp as the ICT prduct r service (Figure 1). It is a mbile app (develped with native cde) that des nt prvide tw-way vice cmmunicatin and that des nt have vide capabilities. Figure 1. Prduct r service name written by the user Then the user is shwn the first questin: Des the ICT have clsed functinality? (Figure 2). There are already sme applicable clauses, as they shuld always be cnsidered because they dn t depend n any questin f the decisin tree (see sectin 2.1 abve). The user answers that first questin (in this case the mbile app is nt clsed) and the system shws the next questin (Figure 3). The prcess cntinues until there are n mre questins t be presented t the user. At that mment the system explains t the user that there are n mre questins and that the results f the prcess have been cpied t the clipbard (Figure 4). There is als a buttn that pens a new windw displaying the results f the decisin prcess (Figure 5). Sectin 5 belw shws the result f the prcess, which has been cpied t the system s clipbard in HTML frmat. Sme f the answers are shwn as derived. This means that they were nt presented t be user but that their answer was derived instead frm the answers given t previus questins. 9
Figure 2. First questin presented t the user Figure 3. Secnd questin presented if the prduct r system is nt clsed 10
Figure 4. End f the questinnaire. All questins have been answered Figure 5. End f the questinnaire. Windw shwing the results f the decisin prcess 5 Example f results Here is the resulting infrmatin cpied int the clipbard by the prttype. 5.1 EN 301 549. Decisin tree results Prduct r service: MyApp 5.1.1 Answers t questins N <-- Des the ICT have clsed functinality? 11
Yes <-- Des the ICT have perable parts? Yes <-- Des the ICT have a lcking r tggle cntrl? N <-- Des the ICT prvide tw-way vice cmmunicatin? N <-- Des the ICT have vide capabilities (playing, transmitting, cnverting r recrding)? N <-- Is the ICT hardware r des the ICT has hardware? N <-- Is the ICT a web page r des the ICT have web pages? N <-- Is the ICT a nn-web dcument r des the ICT have nn-web dcuments? Yes <-- Is the ICT sftware r des the ICT have sftware? Yes <-- Is it nn-web sftware that prvides a user interface? Yes <-- [derived] Des the nn-web sftware have functinality that supprts access t assistive technlgies (i.e. it is nt clsed)? N <-- [derived] Des the nn-web sftware have clsed functinality? N <-- Is it platfrm sftware? Yes <-- [derived] Des the sftware supprt access t assistive technlgies (i.e. it is nt clsed)? N <-- [derived] Des the nn-web sftware have clsed functinality? N <-- Is the ICT an authring tl? N <-- Des the ICT have prduct dcumentatin? N <-- Des the ICT have supprt services? N <-- Is the ICT intended t prvide relay services? 5.1.2 Applicable clauses 05.2 Activatin f accessibility features 05.3 Bimetrics 05.4 Preservatin f accessibility infrmatin during cnversin 05.5.1 Means f peratin 05.5.2 Operable parts discernibility 05.6.1 Tactile r auditry status 05.6.2 Visual status 05.7 Key repeat 05.8 Duble-strike key acceptance 05.9 Simultaneus user actins 11.2.1.01 Nn-text cntent (screen reading supprted) 11.2.1.02 Audi-nly and vide-nly (pre-recrded 11.2.1.03 Captins (pre-recrded) 11.2.1.04 Audi descriptin r media alternative (pre-recrded) 11.2.1.05 Captins (live) 11.2.1.06 Audi descriptin (pre-recrded) 11.2.1.07 Inf and relatinships 11.2.1.08 Meaningful sequence 11.2.1.09 Sensry characteristics 11.2.1.10 Use f clur 11.2.1.11 Audi cntrl 11.2.1.12 Cntrast (minimum) 11.2.1.13 Resize text 11.2.1.14 Images f text 11.2.1.15 Keybard 12
11.2.1.16 N keybard trap 11.2.1.17 Timing adjustable 11.2.1.18 Pause, stp, hide 11.2.1.19 Three flashes r belw threshld 11.2.1.22 Fcus rder 11.2.1.23 Link purpse (in cntext) 11.2.1.25 Headings and labels 11.2.1.26 Fcus visible 11.2.1.27 Language f sftware 11.2.1.29 On fcus 11.2.1.30 On input 11.2.1.33 Errr identificatin 11.2.1.34 Labels r instructins 11.2.1.35 Errr suggestin 11.2.1.36 Errr preventin (legal, financial, data) 11.2.1.37 Parsing 11.2.1.38 Name, rle, value 11.3.2.03 Use f accessibility services 11.3.2.04 Assistive technlgy 11.3.2.05 Object infrmatin 11.3.2.06 Rw, clumn, and headers 11.3.2.07 Values 11.3.2.08 Label relatinships 11.3.2.09 Parent-child relatinships 11.3.2.10 Text 11.3.2.11 List f available actins 11.3.2.12 Executin f available actins 11.3.2.13 Tracking f fcus and selectin attributes 11.3.2.14 Mdificatin f fcus and selectin attributes 11.3.2.15 Change ntificatin 11.3.2.16 Mdificatins f states and prperties 11.3.2.17 Mdificatins f values and text 11.4.2 N disruptin f accessibility features 11.5 User preferences 13