Produced by Araxis Merge on 9/24/2019 1:37:55 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs\JAWS | JAWS-ARIA-Support.doc | Wed Jul 31 17:35:31 2019 UTC |
| 2 | PCL-5_v1_build_8.zip\v1_build 8\Unredacted\spp_mha_web-development.zip\spp_mha_web-development\Docs\JAWS | JAWS-ARIA-Support.doc | Mon Sep 23 22:01:54 2019 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 1 | 154 |
| Changed | 0 | 0 |
| Inserted | 0 | 0 |
| Removed | 1 | 3 |
| Whitespace | |
|---|---|
| Character case | Differences in character case are significant |
| Line endings | Differences in line endings (CR and LF characters) are ignored |
| CR/LF characters | Not shown in the comparison detail |
No regular expressions were active.
| 1 | |||
| 2 | JAWS ARIA Support | ||
| 3 | |||
| 4 | |||
| 5 | Preface | ||
| 6 | Before dis cussing JA WS support for ARIA, it is imp ortant to understand the relat ionship be tween the ARIA marku p itself, the browse r in which the marku p is rende red, and J AWS as it provides s poken or B raille inf ormation t o users. | ||
| 7 | First, ARI A markup w as designe d to inser t informat ion useful to assist ive techno logies int o existing HTML code . It exist s as a way to label controls a nd to prov ide inform ation abou t their st ates. But adding ARI A support to a Web p age does n ot change the presen tation or behavior o f that Web page to s ighted use rs. For ex ample, add ing the AR IA role of “checkbox ” to a “di v” tag wit hin a Web page will produce no visible e ffect on t he page. I nstead, if there is a check bo x on the p age which has been r endered wi thout usin g the “inp ut” tag, t he ARIA ro le of “che ckbox” can be added to the cod e to infor m assistiv e technolo gy users t hat a chec k box appe ars at tha t point on the page. | ||
| 8 | Second, th e browser plays a bi g role in interpreti ng ARIA ma rkup. Most browsers support so me type of accessibi lity API ( applicatio n programm ing interf ace), and assistive technologi es use the API to ge t informat ion about what is pr esented on the scree n. So, ARI A markup i s transfor med by the browser i nto inform ation that fits the accessibil ity API it supports. Then, the informati on provide d by the A PI is proc essed by t he assisti ve technol ogy. That means JAWS support o f ARIA dep ends heavi ly on the browser be ing used. | ||
| 9 | Third, JAW S gathers informatio n from the ARIA mark up and the browser’s API and p resents it in a mean ingful way to screen reader us ers. Becau se of the above inte ractions, the qualit y of JAWS support fo r ARIA mar kup is ine xtricably tied to th e careful, thorough applicatio n of ARIA markup on a Web page , and comp rehensive support pr ovided by the browse r in which the marku p is rende red. | ||
| 10 | For best r esults, Fr eedom Scie ntific rec ommends th at Web pag e authors read the W AI-ARIA 1. 0 Authorin g Practice s carefull y before a dding ARIA markup to their pag es. Also, concepts s uch as rol es, states , landmark s, and so on are def ined as pa rt of the ARIA speci fication, and are th erefore no t defined in this do cument. If you are u nfamiliar with these concepts please rea d through the ARIA d ocumentati on before continuing . | ||
| 11 | Note: For the reason s describe d above, t here may b e differen ces in JAW S ARIA sup port betwe en Interne t Explorer and Firef ox. Please test any examples i n both bro wsers. And please sp ecify whic h browser you’re usi ng when re porting pr oblems to Freedom Sc ientific. | ||
| 12 | Concepts | ||
| 13 | It is a go od idea to have a fi rm grasp o f the foll owing conc epts. Thes e items fo rm the bas is of many descripti ons throug hout the d ocument. | ||
| 14 | Virtual Cu rsor | ||
| 15 | JAWS prese nts Web pa ges using the JAWS V irtual Cur sor. This allows use rs to read and navig ate a Web page as th ough it we re a text document. Users pres s the ARRO W keys to read line by line, w ord by wor d, charact er by char acter, and so on. JA WS also pr ovides Nav igation Qu ick Keys, which are alpha-nume ric keys t hat move t he Virtual Cursor to features of the pag e such as links, hea dings, and form cont rols. In a ddition, u sers can p ress the T AB key to move betwe en focusab le element s on the p age. | ||
| 16 | Using the ARROW keys or Naviga tion Quick Keys to c hange the position o f the Virt ual Cursor does not change the actual fo cus point in the app lication. This means that even if JAWS r eads the t ext of a g iven link on a Web p age for ex ample, tha t link doe sn't neces sarily hav e the keyb oard focus . | ||
| 17 | Note: The keyboard f ocus is ty pically re presented visually a s a highli ghted area surroundi ng a contr ol. | ||
| 18 | Conversely , pressing the TAB o r SHIFT+TA B key to n avigate mo ves the fo cus point and the Vi rtual Curs or follows the focus . | ||
| 19 | Forms Mode | ||
| 20 | Because JA WS uses th e arrow ke ys and alp ha-numeric keys for Virtual Cu rsor navig ation, the se keyboar d commands are not p assed thro ugh to int eractive c ontrols (f orm fields ) on the p age. This approach h as the add ed benefit of protec ting users from inad vertently changing f orm field values or activating controls on the pag e while si mply revie wing the c ontent. | ||
| 21 | Forms Mode is when J AWS turns over proce ssing of t he above k eys to for m controls so that u sers can i nteract wi th them. F or example , when usi ng the Vir tual Curso r, pressin g the lett er F moves the Virtu al Cursor to the nex t form fie ld on the Web page, while in F orms Mode, pressing the letter F types t he charact er "f". | ||
| 22 | Auto Forms Mode | ||
| 23 | Before JAW S 10, JAWS users had to enter and exit F orms Mode manually. Users navi gated to a given con trol using the Virtu al Cursor, and would then pres s the ENTE R key to a ctivate Fo rms Mode. Pressing N UM PAD PLU S (PC Cur sor) cause d JAWS to exit forms mode. | ||
| 24 | When Forms Mode is m anually ac tivated on a given f orm contro l, focus i s set to t hat contro l. | ||
| 25 | Auto Forms Mode is a feature t hat tells JAWS to be smart abo ut when to enter and exit Form s Mode. Th is is a se tting whic h is on by default. This appro ach provid es a seaml ess experi ence for J AWS users when both reading an d interact ing with a Web page. | ||
| 26 | The behavi or of Auto Forms Mod e depends on the typ e of form field in q uestion an d the keyb oard comma nd used to navigate to it. The following is a desc ription of the keybo ard comman ds and how they affe ct Web pag e form fie lds: | ||
| 27 | ARROW Keys | ||
| 28 | When the V irtual Cur sor is act ive, JAWS enters For ms Mode up on encount ering an e dit field. Focus is moved to t he edit co ntrol, and users can begin typ ing. | ||
| 29 | In Forms M ode, the A RROW keys move the c aret withi n the edit field. If an ARROW key is pre ssed and t he caret h as already reached t he boundar y of the e dit field, JAWS exit s forms mo de and res umes using the Virtu al Cursor. Pressing ESC or NUM PAD PLUS will cause JAWS to e xit Forms Mode. | ||
| 30 | Edit field s are the only contr ols for wh ich JAWS e nters or e xits Forms Mode auto matically based on t he ARROW k eys. For o ther contr ols, if JA WS is usin g the Virt ual Cursor , it will continue t o use the Virtual Cu rsor. This is so tha t users do n't accide ntally cha nge the va lue of a c ontrol whi le attempt ing simply to naviga te past it . If JAWS is already in Forms Mode, ARRO W keys wil l not caus e JAWS to leave Form s Mode. Th is is so t hat users won't unin tentionall y leave Fo rms Mode w hile inter acting wit h a contro l. When AR ROW keys a re used to navigate to non-edi t controls , users mu st activat e Forms Mo de manuall y by press ing ENTER. | ||
| 31 | TAB Key | ||
| 32 | Using the TAB key al ways cause s the focu s point to move. Whe n focus ch anges to a given for m control, JAWS acti vates Form s Mode aut omatically based on the type o f control in questio n. | ||
| 33 | For edit f ields, com bo boxes, spin contr ols, list controls, tab contro ls, menu b ars, tree views, and grid cell s, JAWS en ters Forms Mode auto matically. | ||
| 34 | For button s and chec k boxes, J AWS exits Forms Mode . | ||
| 35 | Pressing E SC or NUM PAD PLUS w ill cause JAWS to ex it Forms M ode if it is active. | ||
| 36 | Note: It i s possible to move t o a form f ield by us ing TAB an d to move away from that form field usin g the ARRO W keys, an d vice ver sa. | ||
| 37 | Different Control Ty pes | ||
| 38 | In terms o f Forms Mo de, there are two gr oups of co ntrols: th ose that r equire For ms Mode to interact with them, and those controls that never require F orms Mode to interac t with the m. | ||
| 39 | Forms Mode is requir ed for edi t fields, combo boxe s, spin co ntrols, li st control s, tab con trols, men u bars, tr ee views, and grid c ells. For these cont rols, pres s ENTER or SPACEBAR to enter F orms Mode, and ESC o r NUM PAD PLUS to ex it Forms M ode. | ||
| 40 | For button s and chec k boxes, u se ENTER o r SPACEBAR to activa te the con trol at th e location of the Vi rtual Curs or. Users interact w ith these controls s imply by p ressing EN TER or SPA CEBAR; so forms mode is unnece ssary. Aut o Forms Mo de causes JAWS to le ave Forms Mode when it encount ers these control ty pes becaus e they are just as u sable with out Forms Mode. | ||
| 41 | For combo boxes only , ALT+DOWN ARROW cau ses JAWS t o enter Fo rms Mode a nd drop do wn the lis t of combo box items . ALT+UP A RROW close s the list of combo box items and causes JAWS to e xit Forms Mode. | ||
| 42 | Finally, J AWS Auto F orms Mode behavior f or radio b uttons is a little d ifferent f rom its be havior wit h other ty pes of con trols. Thi s is becau se unlike other cont rols, it i s possible to intera ct with ra dio button s in both Forms Mode and with the Virtua l Cursor. When navig ating with the TAB k ey, JAWS w ill stay i n Forms Mo de if it i s already on, and it will not enter Form s Mode if it is off. Users can press SPA CEBAR to c hoose a sp ecific rad io button when using the Virtu al Cursor, and press ing the AR ROW keys w ill not ch ange the v alue of th e radio bu tton group . Users ca n also pre ss ENTER t o activate Forms Mod e, and sub sequent pr esses of t he UP and DOWN ARROW keys will change th e value of the radio button gr oup. The f ollowing t able conta ins the ex pected beh avior for radio butt ons with A uto Forms Mode. | ||
| 43 | |||
| 44 | KeysIn For ms ModeIn Virtual Cu rsorARROWS Changes ra dio button in group. Does not exit Forms Mode.Does not chang e radio bu tton in gr oup. Does not enter Forms Mode .TABDoes n ot exit Fo rms Mode.D oes not en ter Forms Mode.SPACE BARn/aSele cts the ra dio button at the cu rsor. Does not enter Forms Mod e.ENTERn/a Selects th e radio bu tton at th e cursor. Enters For ms Mode.Fo rms Mode a nd Applica tion Contr ols | ||
| 45 | A page aut hor may ma rk up a We b page usi ng the ARI A role of applicatio n. This r ole indica tes that t he page au thor takes responsib ility for handling o f the ARRO W and ESC keys while the curso r is insid e the appl ication re gion. The goal is t o have JAW S act as t hough it i s inside a standard desktop ap plication. This mean s that as the user t abs from c ontrol to control, J AWS will r emain in F orms Mode and pass o n all ARRO W keys and the ESC k ey to the Web page. | ||
| 46 | When insid e an appli cation reg ion, JAWS treats any interacti ve element as a form control. This means that link s, checkbo xes, radio buttons, and so on are all tr eated like form cont rols requi ring forms mode. Thi s is in co ntrast to the manual and auto Forms Mode behaviors described earlier i n this doc ument. How ever, as w ith Forms Mode in ot her circum stances, u sers are s till able to exit Fo rms Mode o n applicat ion contro ls by pres sing NUM P AD PLUS an d they can re-enter Forms Mode either by tabbing t o a new co ntrol or b y pressing ENTER on a control. | ||
| 47 | The user c an identif y controls inside an applicati on region because th ey are all announced as “appli cation con trols” by jaws as th e user mov es through the Web p age using TAB or the ARROW key s. For exa mple, when a user en counters a link to g oogle insi de an appl ication re gion, JAWS will anno unce, “app lication c ontrol lin k google.” An edit c ontrol wil l be annou nced as “e dit applic ation cont rol.” | ||
| 48 | Note: ther e is no di stinction between re gions of t he page ma rked as ap plications and the c ase where the entire Web page is marked as an appl ication. P revious ve rsions of JAWS treat ed role=”a pplication ” on the b ody of a p age differ ently from role=”app lication i n other pa rts of a W eb page. N ote also t hat if a r egion is m arked as a document and this r egion is i nside an a pplication region, t he control s inside t he documen t are trea ted as ord inary form controls and the st andard for ms mode be havior app lies. | ||
| 49 | Note for d evelopers | ||
| 50 | Controls c ontaining text and w ithout a v isible car et should not be giv en a role of applica tion, nor should the y be neste d inside a n element with role of applica tion. | ||
| 51 | This is be cause when a user ta bs to such an item t hey will a utomatical ly be in a mode in w hich they can't use the ARROW keys to re view the t ext with o ut explici tly leavin g applicat ion mode, something that isn't intuitive . | ||
| 52 | If you hav e a block of text me eting the above crit eria neste d within a n applicat ion, you c an give su cha block a role of document o r nest it within an element wi th role of document. | ||
| 53 | If you exp ect the us er to be a ble to tab to this a rea, be su re to give it an app ropriate t abindex. | ||
| 54 | KeysApplic ation Cont rolIn Form s ModeVirt ual Cursor inside an applicati onARROWSPa sses the k ey on to t he applica tionDoes n ot enter F orms Mode, simply an nounces th e controls name and typeTABDoe s not exit Forms Mod e unless t abbing out of an app licationAl ways enter s Forms Mo de when la nding on a control o f any type including links, ch eckboxes, radio butt ons, and b uttons in side an ap plicationS PACEBARIf on a radio button, c heckbox, l ink or but ton, the c ontrol is activatedE nters Form s Mode on all applic ation cont rols and a ctivates t he control ENTEROn bu ttons, thi s activate s the butt onEnters F orms Mode and on but tons, acti vates the buttonNavi gation Qui ck KeysPas ses the ke y through to the Web pageMoves from cont rol to con trol and d oes not en ter Forms ModeESC ke yPasses th e key thro ugh to the Web pageD oes nothin gARIA Role s | ||
| 55 | The ARIA r oles liste d below ar e common c ontrol typ es that sh ould be fa miliar to Windows us ers. These are contr ols that h ave been s upported b y JAWS in the Window s operatin g system f or many ye ars. There fore, the expected b ehavior fo r each con trol type is not pre sented in detail. Su fficed to say, in Fo rms Mode, JAWS shoul d behave c omparably between co ntrols pre sented on Web pages and their counterpar ts in stan dard deskt op applica tions. Lik ewise, mos t of these control t ypes have existed in HTML for a long tim e, and JAW S has supp orted thos e controls using the Virtual C ursor. In Virtual Cu rsor mode, JAWS beha vior betwe en a combo box creat ed with st andard HTM L for exam ple should be no dif ferent fro m JAWS beh avior with a properl y construc ted JavaSc ript-based combo box and ARIA markup. In a few cas es, ARIA m arkup allo ws for con trol types which wer e not avai lable befo re in HTML . In these cases, no tes may ap pear next to the rol es in ques tion. | ||
| 56 | An importa nt thing t o understa nd about A RIA roles is that se veral role s may be c ombined to form the framework of one con trol on a page. For example, a n editable grid cons ists of an object wi th the rol e of “grid ”, having children w ith the ro le of “row ”, having children w ith the ro le of “row header”, “ columnhead er”, or “g ridcell”. Such contr ols are co mposed of expected p atterns of roles whi ch are des cribed in the ARIA b est practi ces docume nt. If the construct ion of the se control s is done in a way o ther than that descr ibed by th e best pra ctices doc ument, JAW S may not behave as the author intends. | ||
| 57 | Furthermor e, states and roles also relat e closely to one ano ther. ARIA roles hav e a list o f valid st ates provi ded in the ARIA docu mentation. Although the specif ic set of states sup ported by JAWS is no t listed w ith each r ole, a rea sonable st andard of common usa ge applies to the ac ceptable s tates for each role. For examp le, the st ate of “ar ia-require d” makes n o sense wh en applied to a grap hic. And t he state o f “aria-re adonly” is superfluo us when ap plied to a check box . JAWS att empts to f ilter out extraneous informati on for cer tain contr ol types. So, page A uthors sho uld use th e ARIA doc umentation as a guid e, and rep ort any di screpancie s to Freed om Scienti fic. | ||
| 58 | Note: Some supported roles, su ch as thos e for land mark regio ns, have b een omitte d from the below lis t, but wil l be discu ssed later in this d ocument. | ||
| 59 | The follow ing is a l ist of rol es which J AWS recogn izes: | ||
| 60 | |||
| 61 | RoleCommen tsalert T his role d oes not ap pear in ei ther the v irtual buf fer or For ms Mode, b ut its con tents are spoken by JAWS when an alert i s made vis ible.alert dialogbutt on If thi s control has aria-h aspopup="t rue" then this is a button men u. | ||
| 62 | If this co ntrol has aria-press ed defined then this is a togg le button. checkbox c olumnheade r combobo x dialog This role will be an nounced on ly when a child of t he dialog gets focus , and will not appea r in the v irtual buf fer.docume nt This r ole may no t be expli citly anno unced by J AWS, but i t indicate s that the area it o ccupies is meant to be read as a Web pag e. This is the defau lt role of the topmo st object in a Web p age (i.e., the “body ” tag).Gri d gridcel l group Like docum ent, this role may n ot be expl icitly ann ounced by JAWS. Howe ver, when it surroun ds a group of form c ontrols, J AWS should announce its name a nd descrip tion when entering t he group.h eading Th e aria-lev el gives t he heading levelimg link li st listbo x listite m menu l og Presen tly, this role is kn own to wor k with JAW S in Firef ox only, a nd it func tions as a type of l ive region . JAWS in serts star t and end strings in to the vir tual buffe r to indic ate the lo g.menubar menuitem menuitem checkboxme nuitemradi o NoteJAWS inserts s tart and e nd strings into the virtual bu ffer to in dicate not es.option presentat ion This role indi cates that a feature of a Web page exist s for visu al formatt ing only. Therefore, JAWS igno res object s with thi s role. (K nown to wo rk in Fire fox.)progr essbarradi o radiogro up row r owheader separator Scrollbar Uses the a ria-orient ation to d etermine t he type of scroll ba r (vertica l or horiz ontal)slid er spinbut ton JAWS a nnounces t his role a s a “spin box”.tab tablist t abpanel t extbox to olbar Thi s role is indicated in the vir tual buffe r by start and end m essages li ke those t hat exist for HTML l ists.toolt ip This r ole is not shown by JAWS in th e virtual buffer or in Forms M ode, but i ts content s are spok en when it becomes v isible.tre e When in the virtu al buffer, JAWS may show only one item o f a tree c ontrol. Th is allows the user t o navigate past the tree quick ly.treegri d treeite m ARIA St ates | ||
| 63 | The same p rinciple o f reasonab le common usage appl ies to ARI A states a s applied above to r oles. | ||
| 64 | Note: Some states, s uch as tho se related to drag a nd drop, h ave been o mitted fro m the belo w list, bu t will be discussed later in t his docume nt. | ||
| 65 | The follow ing is a l ist of sta tes which JAWS recog nizes: | ||
| 66 | |||
| 67 | StateComme ntsaria-ac tivedescen dantJAWS u ses this s tate to lo cate the f ocused ite ms in tree views, li st boxes, and other such contr ols that m anage mult iple, focu sable chil dren.aria- busyIn Fir efox, an e lement mar ked as ari a-busy is omitted fr om the acc essibility tree for the page.a ria-checke daria-desc ribedbyari a-disabled JAWS annou nces this state for form contr ols.aria-e xpandedJAW S announce s this sta te when in Forms Mod e in tree controls.a ria-haspop upJAWS ann ounces thi s state fo r any cont rol except buttons a nd combo b oxes which pops up a menu. .ar ia-hiddena ria-invali dJAWS anno unces this state for form cont rols.aria- labelaria- levelJAWS announces the level of tree it ems when i n Forms Mo de.aria-mu ltilineJAW S uses thi s state to identify multiline edit contr ols.aria-o rientation JAWS uses this state to determ ine if a s lider is o riented ho rizontally or vertic ally.aria- posinsetJA WS announc es this in formation when in Fo rms Mode f or trees a nd lists.a ria-presse dJAWS anno unces the pressed st ate of a t oggle butt on.aria-re adonlyJAWS uses this state to identify e dit fields that are navigable with a car et, but wh ose conten t cannot b e changed. aria-requi redJAWS an nounces th is state f or form co ntrols.ari a-selected aria-setsi zeJAWS ann ounces thi s informat ion when i n Forms Mo de for tre es and lis ts.aria-va luetextARI A Relation ships | ||
| 68 | Using ARIA , a page a uthor can specify re lationship s among el ements. JA WS support s the use of the fol lowing rel ationships : | ||
| 69 | Relationsh ipComments aria-descr ibedbyJAWS announces this stat e for form controls. The user can read t he describ edby text using INSE RT+ALT+R.a ria-labell edbyJAWS a nnounces t his state for form c ontrols.Ar ia-flowto & aria-flo wfromWhen the author defines t hese relat ionships o n elements in a Web page, JAWS will anno unce that the elemen t has a “f lows from” or “flows to” relat ionship. T he user ca n move to “flows to” elements using the EQUALS Nav igation Qu ick Key an d to “flow s from” us ing the SH IFT+EQUALS Navigatio n Quick Ke y.Aria-con trolsJAWS will annou nce that a n element has the “c ontrols” r elationshi p to anoth er element on the pa ge. The us er can mov e to the c ontrolled element us ing INSERT +ALT+M.Doc ument Regi ons | ||
| 70 | JAWS annou nces the t ype and te xt of docu ment regio ns, and pr ovides nav igation to the next and previo us documen t region o n the page using the SEMICOLON and SHIFT +SEMICOLON Navigatio n Quick Ke ys. In add ition, pre ssing INSE RT+CONTROL +SEMICOLON brings up a list of document regions. N ote that J AWS treats a number of element s as regio ns. This i ncludes al l the ARIA landmark regions al ong with s everal oth er region types list ed below. This table also prov ides the t ext JAWS u ses in the virtual b uffer to i ndicate th e start of a region. | ||
| 71 | ARIA Role/ HTML5 TagV irtual Buf fer TextRo le=”applic ation”<reg ion name> applicatio nRole=”art icle” tag= ”article”< region nam e> article Role=”bann er” <regio n name> ba nnerRole=” complement ary” tag=” aside”<reg ion name> complement ary inform ationRole= ”contentin fo”<region name> con tent infor mationRole =”document ”<region n ame> docum entRole=”f orm”<regio n name> fo rmRole=”ma in”<region name> mai n regionRo le=”naviga tion” tag= ”nav”<regi on name> n avigation regionRole =”region” tag=”secti on”<region name> reg ionRole=”s earch”<reg ion name> search reg ionLive Re gions | ||
| 72 | JAWS suppo rts use of the “aria -live” att ribute and any of it s acceptab le values: “polite”, “assertiv e”, or “of f”. JAWS w ill also t reat regio ns with th e ARIA rol e of “log” or “statu s” as a li ve region. In additi on, JAWS s upports us e of the “ aria-atomi c” state o n live reg ions. JAWS does sup port use o f the “ari a-relevant ” state in firefox. | ||
| 73 | Note: Sinc e the “ari a-live” va lue of "ru de" is no longer sup ported by the standa rd, the us e of it is deprecate d in JAWS, but still supported . | ||
| 74 | Drag and D rop | ||
| 75 | JAWS suppo rts the AR IA drag-an d-drop pro perties “a ria-grabbe d” and “ar ia-dropeff ect”. When a Web pag e author a pplies the se propert ies to obj ects on a Web page, JAWS will identify s uch object s as grabb able, grab bed, or dr oppable. | ||
| 76 | The keystr oke WINDOW S Key+CTRL +EQUALS op ens the AR IA Drag an d Drop dia log box, w hich shows a list of droppable objects o n the page . When you select on e of these objects, JAWS will move focus to it. If no droppa ble object s are avai lable, JAW S will ann ounce the message, “ No droppab le element s were fou nd on the page” inst ead of ope ning the d ialog box. | ||
| 77 | Note: JAWS does not implement the drag a nd drop fu nctionalit y in the s ense that JAWS doesn ’t grab or drop obje cts itself . Accordin g to the A RIA specif ication, t hat functi onality sh ould be pr ovided by the page a uthor. JAW S simply a nnounces t o the user that a gi ven elemen t is grabb able, grab bed, or dr oppable. | ||
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.