digital library design guidelines to support blind and visually ...€¦ · bvi user studies that...

1

DigitalLibraryDesignGuidelinestoSupportBlindandVisuallyImpaired

Users INTRODUCTION Background An estimated 253 million people in the world live with significant vision loss (World Health Organization, 2018). Blind and visually impaired (BVI) individuals comprise an atypical group of users who rely on screen readers to interact with digital libraries (DLs). BVI users face unique needs, challenges, strategies, and preferences in their interactions with DLs. To design DLs that meet the needs of BVI users, DL developers must first understand these special needs. BVI users exhibit unique help-seeking situations in Web interactions. A help-seeking situation is characterized by a problem that arises during a user’s interaction with a DL, which motivates them to seek some form of assistance in order to complete an information retrieval task. Prior literature reveals that these users face multiple cognitive and physical constraints during online information retrieval, including: 1) avoidance of pages due to dynamic content; 2) browsing difficulty due to structural problems and the linear nature of screen reading; 3) sequential interaction and loss of contextual information; 4) lack of important navigational and interpretive cues; 5) cognitive overload; and 6) improper labeling of interface objects (Babu, 2011; Bigham, Cavender, Brudvik, Wobbrock, & Ladner, 2007; Chandrashekar, 2010; Craven, 2003; Lazar, Allen, Kleinman, & Malarkey, 2007; Leuthold, Bargas-Avila, & Opwis, 2008; Salampasis, Kouroupetroglou, & Manitsaris, 2005; Theofanos & Redish, 2003). Although a few studies investigate BVI users’ problems and coping strategies (Vigo & Harper, 2013), a systematic examination of their help-seeking situations and associated factors in diverse DL environments has not yet been conducted. This creates a gap in research on BVI users’ help needs for effective DL interactions. Addressing this gap is the first step toward building a BVI user-friendly DL. DL research has primaily paid attention to accessibility and usability (Carlo Bertot, Snead, Jaeger, & McClure, 2006; Isfandyari-Moghaddam & Bayat, 2008), with the most commonly used guidelines focusing on Web accessibility (Lazar, Allen, Kleinman, & Malarkey, 2007). The problem is that these guidelines do not address many of the interaction problems and help-seeking situations that BVI users face in their use of DLs (Power, Freire, Petrie, & Swallow, 2012; Southwell & Slater, 2012; Vigo & Harper, 2013). Stages of the Creation of the Guidelines The intent of the project is to develop guidelines based on BVI users’ special needs. It consists of four stages. At each stage, feedback from consultants was incorporated into the project. At Stage 1, a thorough and comprehensive search and review of literature from the past 20 years were conducted along with related document analysis to identify a list of help-seeking situations that BVI users encounter in their Internet interactions. Two document analyses were provided to: 1) address help-seeking situations and needs of BVI users in DLs; and, 2) identify existing

2

design guidelines on accessibility, usability, and utility in digital environments, and their limitations. Simultaneously, two types of analyses were conducted to identify the current status and problems with the existing guidelines as they relate to accessibility and usability. At Stage 2, sixty-four participants were recruited representing BVI users across the U.S. with a variety of characteristics. Thirty-two of these participants completed the onsite study, while another 32 participants finished the diary study. All participants searched multiple DLs representing different types of content and design. Data, derived from a series of user studies, including previous BVI user studies conducted by the research team (Xie, Babu, Castillo, & Han, 2018; Xie, Babu, Joo, & Fuller, 2015), were used to identify the help-seeking situations that BVI users encounter in DLs and their associated help needs, and to develop the draft of the guidelines. At Stage 3, the in-depth survey was administered to 150 participants who represented three groups of stakeholders (DL developers, accessibility and usability scholars/experts, and end users) to assess the importance, clarity, relevance, usefulness, and feasibility of guidelines. The findings of the survey further refined the guidelines. At Stage 4, thirty DL developers will use the guidelines to assess six of the leading DLs and test the feasibility of the guidelines. In addition, the outcomes of the assessment will also be used to assess the current status and conformance levels of these DLs in terms of whether they meet conformance criteria for accessibility and usability for BVI users. Four focus groups, comprised of 7-8 participants each, will then be formed to discuss the problems of the guidelines they find in the assessment process. Based on suggestions and feedback, the DL design guidelines will be enhanced. Moreover, feedback from advisory board members will also be solicited before finalizing the guidelines. Focus These Guidelines were created based on the types of help-seeking situations identified by several BVI user studies that investigate BVI users’ interactions with existing DLs. The inclusion criteria are: 1) Design guidelines are developed for each individual type of help-seeking situation encountered in DLs by BVI users during user studies; and 2) These Guidelines only focus on supporting BVI users who rely on screen readers to interact with DLs. Audiences These Guidelines’ primary audiences are DL designers, facilitating increased accessibility and usability for BVI users. At the same time, these Guidelines are also for DL researchers, teachers, and graduate students who are interested in digitization, DL development, DL management, DL evaluation, and accessibility issues in the DL environment. The secondary audience could also include researchers and practitioners who work on the accessibility and usability of electronic information retrieval systems. Glossary In order to prepare the audiences to better understand and use the guidelines, a glossary was created to present the definitions of the key terms used in the guidelines. It consists of terms that relate to the situations, factors, guidelines, techniques, recommended features, and elements of DLs. The glossary is organized alphabetically and can be found in Appendix A.

3

Guidelines structure Multiple access points are provided for the Guidelines. These Guidelines are organized by categories and types of help-seeking situations, including:

• Difficulty accessing information • Difficulty identifying current status, path, or cursor mode • Difficulty locating specific information, items, or features • Confusion about multiple programs or DL structures • Difficulty constructing or refining searches • Difficulty with help • Avoidance tendency • Difficulty evaluating information • Difficulty with compatibility issues

The Guidelines can also be accessed based on their nature: perceivable, operable, understandable, and robust. The third index approach is created according to types of DL functions. Under each type of help-seeking situation, the following components are presented:

• Definition of the type of help-seeking situation • Factors that lead to the situation • Guideline or Design Recommendations • Rationale and Objective • Techniques and Methods • Recommended Features • Examples • Related Resources • See Also

Table of Contents Table1. Types of Help seeking situations

Main level Help-seeking

situations (32, unique 27)

Definitions Sub level Help-seeking situations

4

Difficulty accessing

information (5)

Problems related to detecting or recognizing an item(s) or receiving information.

• Difficulty accessing a clickable element http://sites.uwm.edu/guidelines/accessing/difficulty-accessing-a-clickable-element/

• Difficulty accessing content of a scanned document http://sites.uwm.edu/guidelines/accessing/difficulty-accessing-content-of-a-scanned-document/

• Difficulty locating or accessing information related to visual items http://sites.uwm.edu/guidelines/accessing/difficulty-locating-or-accessing-information-related-to-visual-items/

• Difficulty locating or accessing multimedia controls http://sites.uwm.edu/guidelines/accessing/difficulty-locating-or-accessing-multimedia-controls/

• Difficulty locating or accessing search features http://sites.uwm.edu/guidelines/accessing/difficulty-locating-or-accessing-search-features/

Difficulty evaluating

information (2)

Difficulty making sense of search results, collections, or subject organization criteria; difficulty understanding the relevance of search results or identifying relevant collections or subjects.

• Difficulty assessing relevance of an item http://sites.uwm.edu/guidelines/evaluating/difficulty-assessing-relevance-of-an-item/

• Difficulty assessing format of an item http://sites.uwm.edu/guidelines/evaluating/difficulty-assessing-format-of-an-item/

Difficulty with help (5)

Difficulty understanding labels; problems understanding how to use a specific function; inability to understand help information.

• Difficulty recognizing or interpreting a label http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-recognizing-or-interpreting-a-label/

• Difficulty understanding how to use a DL http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-understanding-how-to-use-a-DL/

• Difficulty locating or understanding help information http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-locating-or-understanding-help-information/

• Difficulty understanding or using a specific feature http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-understanding-or-using-a-specific-feature/

• Difficulty detecting or using dynamic features and content http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-detecting-or-using-a-dynamic-features-and-content/

5

Difficulty locating specific

information, items or features

(7)

Difficulty finding specific information or type of an item or format of an item or features

• Difficulty detecting or locating search results http://sites.uwm.edu/guidelines/identifying/difficulty-detecting-or-locating-search-results/

• Difficulty locating a specific word, phrase, or related term http://sites.uwm.edu/guidelines/locating/difficulty-locating-a-specific-word-or-phrase-or-related-term/

• Difficulty locating metadata http://sites.uwm.edu/guidelines/locating/difficulty-locating-metadata/

• Difficulty locating or accessing information related to visual items http://sites.uwm.edu/guidelines/accessting/difficulty-locating-or-accessing-information-related-to-visual-items/

• Difficulty locating or accessing multimedia controls http://sites.uwm.edu/guidelines/accessing/difficulty-locating-or-accessing-multimedia-controls/

• Difficulty locating or accessing search features http://sites.uwm.edu/guidelines/accessing/difficulty-locating-or-accessing-search-features/

• Difficulty locating or understanding help information http://sites.uwm.edu/guidelines/difficulty-with-help/difficulty-locating-or-understanding-help-information/

Difficulty identifying

current status, path, or cursor

mode (6)

Problems identifying the current location, returning to home or a previous page, getting started or proceeding, recognizing page loading status, or monitoring searches.

• Difficulty detecting or locating search results http://sites.uwm.edu/guidelines/identifying/difficulty-detecting-or-locating-search-results/

• Difficulty identifying current location or tracking paths http://sites.uwm.edu/guidelines/identifying/difficulty-identifying-current-location-or-tracking-paths /

• Difficulty identifying items that require downloading before viewing http://sites.uwm.edu/guidelines/identifying/difficulty-identifying-items-that-require-downloading-before-viewing/

• Difficulty navigating through a DL http://sites.uwm.edu/guidelines/identifying/difficulty-navigating-through-a-dl/

• Difficulty recognizing current status of a DL http://sites.uwm.edu/guidelines/identifying/difficulty-recognizing-current-status-of-a-DL/

• Difficulty recognizing pre-existing text in an input box http://sites.uwm.edu/guidelines/identifying/difficulty-recognizing-pre-existing-text-in-an-input-box/

Confusion about multiple programs, DL structures, or search results structure (2)

Confusion resulting from complex DL structures or difficulties distinguishing the

• Confusion about digital library structure or browse categories http://sites.uwm.edu/guidelines/confusion/confusion-about-digital-library-structure-or-browse-categories/

• Difficulty understanding results structure or layout http://sites.uwm.edu/guidelines/confusion/difficulty-

6

DL from other programs

understanding-results-structure-or-layout/

Avoidance tendency

(1)

Avoidance of visual items, browsing approaches, in-depth exploration, or search input fields.

• Avoidance of format, approach, or features http://sites.uwm.edu/guidelines/avoidance/avoidance-of-format-approach-or-features/

Difficulty constructing or

refining searches

(3)

Difficulty formulating and reformulating searches

• Difficulty to construct search queries http://sites.uwm.edu/guidelines/constructing/difficulty-to-construct-search-queries/

• Difficulty refining search queries http://sites.uwm.edu/guidelines/constructing/difficulty-refining-search-queries/

• Difficulty tracking searches http://sites.uwm.edu/guidelines/constructing/difficulty-tracking-searches/

Difficulty with compatibility issues

(1)

Problems related to compatibility issues such as incompatible browser or keyboard

• Situations related to compatibility issues http://sites.uwm.edu/guidelines/compatability/situations-related-to-compatibility-issues/

REFERENCES Babu, R. (2011). Developing an understanding of the accessibility and usability problems blind

students face in web-enhanced instruction environments. (Doctoral Dissertation). ProQuest Dissertations and Theses. (Accession Order No. AAT 3473492)

Bigham, J. P., Cavender, A. C., Brudvik, J. T., Wobbrock, J. O., & Ladner R. E. (2007). WebinSitu: A comparative analysis of blind and sighted browsing behavior. Computers and Accessibility Proceedings of the 9th International ACM SIGACCESS Conference (pp. 51-58). New York, NY: ACM.

Carlo Bertot, J., Snead, J. T., Jaeger, P. T., & McClure, C. R. (2006). Functionality, usability, and accessibility: Iterative user-centered evaluation strategies for digital libraries. Performance Measurement and Metrics, 7, 1: 17-28.

Chandrashekar, S. (2010). Is Hearing Believing? Perception of Online Information Credibility by Screen Reader Users who are Blind or Visually Impaired. (Doctoral dissertation). Retrieved from https://tspace.library.utoronto.ca/bitstream/1807/26157/6/Chandrashekar_Sambhavi_201011_PhD_thesis.pdf

Craven, J. (2003, July). Access to electronic resources by visually impaired people. Information Research, 8 (4). Retrieved from http://informationr.net/ir/8-4/paper156.html

7

Isfandyari-Moghaddam, A., & Bayat, B. (2008). Digital libraries in the mirror of the literature: issues and considerations. The Electronic Library, 26 (6), 844-862.

Lazar, J., Allen, A., Kleinman, J., & Malarkey, C. (2007). What frustrates screen reader users on the web: A study of 100 blind users. International Journal of Human-computer Interaction, 22(3), 247-269.

Leuthold, S., Bargas-Avila, J. A., & Opwis, K. (2008). Beyond web content accessibility guidelines: Design of enhanced text user interfaces for blind internet users. International Journal of Human-Computer Studies, 66(4), 257-270.

Power, C., Freire, A., Petrie, H., & Swallow, D. (2012). Guidelines are only half of the story: accessibility problems encountered by blind users on the web. Human Factors in Computing Systems Proceedings of the SIGCHI Conference (pp. 433-442). New York, NY: ACM.

Salampasis, M., Kouroupetroglou, C., & Manitsaris, A. (2005). Semantically enhanced browsing for blind people in the WWW. Hypertext and Hypermedia Proceedings of the Sixteenth ACM Conference (pp. 32-34). New York, NY: ACM.

Southwell, K. L., & Slater, J. (2012). Accessibility of digital special collections using screen readers. Library Hi Tech, 30 (3), 457-471.

Strauss, A., & Corbin J. M. (1990). Basics of qualitative research: Grounded theory procedures and techniques. Newbury Park, CA: Sage.

Theofanos, M. F., & Redish, J. (2003). Guidelines for accessible and usable web sites: observing users who work with screen readers. Interactions, 10 (6), 38-51.

Vigo, M., & Harper, S. (2013). Coping tactics employed by visually disabled users on the web. International Journal of Human-Computer Studies, 71(11), 1013-1025.

World Health Organization. (2018, October 11). Blindness and visual impairment. Retrieved from http://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment

Xie, I., Babu, R., Castillo, M. D., & Han, H. (2018). Identification of factors associated with blind users' help‐seeking situations in interacting with digital libraries. Journal of the Association for Information Science and Technology, 69(4), 514-527.

Xie, I., Babu, R., Joo, S., & Fuller, P. (2015, June). Using digital libraries non-visually: understanding the help-seeking situations of blind users. Information Research: An International Electronic Journal, 20(2). Retrieved June 15, 2018 from http://InformationR.net/ir/20-2/paper673.html

8

DifficultyAccessingInformation

DifficultyaccessingaclickableelementDefinition:Asituationthatarisesfromthedifficultyinaccessinganactiveelement,suchasalink,push-button,orwidgetthatactivateswithamouseclickbutnotwithakeystroke.

Factor(s):• • Lackoflabels• Unclearlabels• Lackofkeyboardsupport• BrokenlinksGuidelineorDesignRecommendation:1. Ensurethelabelsforallclickableelementsareunderstandable2. Ensureactiveelementsareabletobeactivatedviakeyboard3. Provideinstructiononhowtoaccessitemsusingakeyboard4. ProvideamappingofprimaryDLfunctionsanddesignatedscreencontrolsto

correspondingscreenreadercommandsRationaleandObjective:BVIusersrelyonkeyboardfunctionsratherthanusingavisualpointingdevicesuchasamouse.Thissituationinvolvesaccessinginterfacedesignelementswithoutusingamouseaswellastheavailabilityoflinks(brokenornot.)Somevisual/multimediacontentorapplicationprogramsthatincludewidgetsonlyworkwithmouseoperations.ARIAfeaturescanbehelpfulforBVIuserstorecognizethechangesofapplications/contentandaccessthem.AlllinksmustbeoperablefromthekeyboardbasedonWCAGrequirements.Itisrecommendednottouseinaccessibleapps,suchasJavaScriptframeworks.

TechniquesandMethods:1.1.Providemeaningfullabelsforallclickableelementsspecifyingtheirfunctions2.1.UsestandardHTMLcontrolstobuildactiveelements2.2.Setupascheduletoverify,update,orremovemissingorbrokenlinks2.3.Provideafeedbackformtoenableuserstoreportabrokenlink3.1.Providetipsand/orinstructionabouthowtoactivateelementsbykeyboardoperations4.1.CreatewebapplicationsandinterfacesusingARIAsotheywillbecompatiblewithscreenreaders

9

RecommendedFeatures:1.1Meaningfullabels2.1.A.Livelinks2.1.B.Keyboardaccessibleactiveelements2.3.Feedbackform3.1.Helpfunction4.1.ARIA-compliantinterfaceandfeatures

Examples:2.1.B1.AddCSS“a:focus”toselectorswith“a:hover”toensurekeyboardaccess.2.1.B2.Useasimpleimage-basedcheckboxwidgetusingtabindextoallowkeyboardaccess.(https://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgets)

RelatedResources:Flood,B.(2018).Keyboard-navigableJavaScriptwidgets.Retrievedfromhttps://developer.mozilla.org/en-US/docs/Web/Accessibility/Keyboard-navigable_JavaScript_widgetsMelnyk,V.,Ashok,V.,Puzis,Y.,Soviak,A.,Borodin,Y.,&Ramakrishnan,I.V.(2014,July).Widgetclassificationwithapplicationstowebaccessibility.InInternationalConferenceonWebEngineering(pp.341-358).Cham:Springer.Starr,J.(2016).EZIDIntroducesLinkChecking.Retrievedfromhttps://www.cdlib.org/cdlinfo/2016/10/17/ezid-introduces-link-checking/.

10

W3C.(2016).AccessibleUIComponentsList–Frameworks,Snippets,Themes,andWidgetsforaBetterWeb.Retrievedfromhttps://www.w3.org/blog/wai-components-gallery/WAI-ARIAAuthoringPractices1.1(2017)–5.1FundamentalKeyboardNavigationConventions.Retrievedfromhttp://www.w3.org/TR/wai-aria-practices/#kbd_generalnav.WCAGUnderstandingGuideline2.1KeyboardAccessiblehttps://www.w3.org/TR/UNDERSTANDING-WCAG20/keyboard-operation.html

Seealso:Help-seekingSituations>DifficultyAccessingInformation

DifficultyaccessingcontentofascanneddocumentDefinition:Asituationthatarisesfromthedifficultyreadingascanneddocumentthatisimproperlyscannedorformatted.

Factor(s):• • Lackoflegibletranscriptbecauseoflowquality• Inabilitytodetectthecontentofatranscriptbyscreenreadersbecauseofimproper

formattingGuidelineorDesignRecommendation:1. Ensurethefulltextofascanneddocumentisreadable2. ProvideessentialinformationforascanneddocumentwithreadabilityissuesRationaleandObjective:AtranscriptisaconvenientinformationsourceforBVIusers.Oneissueresultsfrompoorcontentquality,whichmakesthetranscriptdifficulttoreadbyscreenreadersoftware.ThecauseofthisdifficultyisdifferentthanmostinthatitarisesnotbecauseoftheDLinterfacebutratherbecauseofthequalityoftheitemswithintheDL.Theguidelinesandtechniquespresentedheremustlargelybeimplementedatthetimethatanitemisdigitized.Ifrescanning

11

ofpoorlydigitizeditemswithbetterOCRmethodsisnotpossible,thenmanualeditingandcorrectionoftranscriptscanbehelpful.

TechniquesandMethods:1.1.Choosethemostappropriateandeffectivesoftwaretoscandocumentsbasedontheircontent(e.g.OCRforprintedortypedtext,HRTforhandwrittentext,missingletterprediction,ornaturallanguage)1.2.SettheOCRorHRTsoftwareand/orhardwareforthehighestqualityrecognitionpossible1.3.Scanthematerialathighresolution(Morethan600dpi).1.4.Establishqualitycontrolproceduresforthedigitizationprocess1.5.UseText-to-speechfunction(e.g.readloudfunctioninPDF)totestthereadabilityofthescanneddocument1.6.ManuallyreviewandcorrectpoorqualityitemsgeneratedthroughOCRorHTR1.7.Transcribeoriginalsourcesmanuallyifcharacterrecognitionsoftwareisnotavailableoreffective2.1.ProvidesummariesandkeywordsfordocumentswithpoorqualitytranscriptsgeneratedbyOCRorHTR

RecommendedFeatures:1.1.Appropriatedocumentscanningandtranscriptgenerationsoftware(e.g.OCRsoftwareforprintortypedtext,HRTsoftwareforhandwrittentext)1.3.High-resolutionscanning1.4.Qualitycontrolprocedures1.5.Text-to-speechfunction1.6.Manualevaluationofscanneddocuments1.7.Manualcreationofadocumenttranscript2.1.Summariesandkeywords

Examples1.1.Exampleofatranscriptgeneratedforahandwrittenletter.UniversityofCambridge,DarwinCorrespondenceProject.Retrievedfromhttps://www.darwinproject.ac.uk/letter/DCP-LETT-9247.xml

13

1.2.OCRFastmodeoption(disablingthisfeaturerecommendedforpoorqualitymaterial)(OCLC,2017)

14

RelatedResources:DGM2120.(n.d.).AccessibiltyandCollatedTextTranscript.Retrievedfromhttp://desource.uvu.edu/dgm/2120/in/steinja/lessons/08/08_08.html.Macentee,T.(2017).WordforWord:DocumentTranscribingTechnology.Retrievedfromhttps://abundantgenealogy.com/word-word-document-transcribing-technology/OCLC.(2017).OCRSettings.Retrievedfromhttps://www.oclc.org/support/services/contentdm/help/project-client-help/entering-metadata/ocr-settings.en.htmlTranskribus.(2017).Retrievedfromhttps://transkribus.eu/wiki/images/a/ad/HowToTranscribe_SimpleMode.pdfSeeAlso:Help-seekingSituations>Difficultyaccessinginformation

15

DifficultylocatingoraccessinginformationrelatedtovisualitemsDefinition:Asituationthatarisesfromthedifficultytofindandgainaccesstoalternativetext,transcriptsordescriptionforvisualitemsinadigitallibrary.

Factor(s):

• Unavailabilityorlackoftranscriptsforvisualitems• Unclearlabelingofcontrolsformediaplayers• Complexinformationpresentation• Toomanyclicksrequiredtoaccessatranscript• Lackofashortcuttoatranscript(e.g.headingorinvisiblelinks)GuidelineorDesignRecommendation1. Provideconciseandmeaningfulalternativetextforallvisualitems2. Providetranscriptsforimagesoftextdocuments3. Provideaudiodescriptionsforvideomaterials4. Providedescriptivemetadataforeachimageorvideoitem5. Ensurealternativetext,transcriptsanddescriptionsforvisualitemscanbeeasilylocated6. Ensurealternativetext,transcriptsanddescriptionsforvisualitemscanbeeasilyaccessed7. Providehelpinformationregardingalternativetext,transcript,ordescriptionaccessRationaleandObjective:ProvidingatexttranscriptforanimageoravideoitemishelpfulforBVIuserstosearchforakeywordorscanoverallcontent.Specifically,sinceDLsincludearangeofheterogeneouscontent,includingillustratedbooks,photos,maps,manuscripts,etc.,itisnecessarytoincludeatexttranscriptinadocumentformthatisaccessible.Preferably,thetranscriptshouldbeinmarkuplanguageforwebpages,suchasHTML/XMLdocumentformat,asitisconsideredtobemosteasilyaccessiblebyscreenreaders.Regardingdownloadableformats,becausePDFformattypicallyrequiresup-to-dateassistivetechnologyandaplug-inforaccessingthePDFfiles,MicrosoftWordformatmightbemoreappropriate.Acaptionandmetadatashouldalsobeprovidedtoofferadditionalinformationalongwiththetranscript.Also,providingaclearlabelforthetranscriptisimportantbecause“text”metadatareferstotexttype,butBVIusersmaymistakethistermtomean“transcript.”ItmightbebeneficialtoaddinvisibleheadingsforBVIuserstosupporteaseofnavigation.

TechniquesandMethods:

16

1.1.Provideasupplementarydescriptionforavisualitemnexttotheitemwithaclearlabel2.1.Provideanoptiontodownloadatranscriptofavisualitem2.2.Providepartialtranscriptsiffulltranscriptsareunavailable,andclearlyindicateapartialtranscriptisavailableforavisualitem3.1.Offeraudiodescriptionforscenesofvideosbetweendialogues4.1.Provideaclearandconcisedescriptionofavisualitemsinmetadata5.1.Provideanoptionfortranscriptdisplaynexttoavisualitem5.2.Add“Transcript”asinvisiblepartofthetitleforaheading5.1./6.1.Addaninvisible“Skiptotranscript”link7.1.Provideacontext-sensitivedescriptionforinformationembeddedinavisualitem.Forexample,iftheimageportraysprotestorsholdingasignfortheirprotest,BVIaudiencesshouldbeprovidedwithcontextualinformationonthebroadermeaningofthesigninadditiontothetextorthevisualimage.

RecommendedFeatures:1.1.A.Alttext1.1.B.Meaningfullabels2.1.Downloadabletranscriptfeature2.2.Transcriptdisplayfeature3.1.Invisibleaudiodescriptioncontrols4.1.Descriptionelementinmetadata5.1./6.1.Skip-to-transcriptlinks5.2.Invisibleheadings7.1.Context-sensitivedescription

Examples:1.1.A.Enabledtranscriptfeaturethatprovidesatext-basedrepresentationofthevisualcontent

1.1.B.Use“accessinterview”,“viewmovie”,or“listentoaudiorecording.”Inthemediaexample,linkstothemediaopenedinanewbrowsertab,butthisbehaviorwasnotindicatedwiththelink.Anattributetitle=“Opensinnewwindow”wouldhaveaddressedtheissue.

1.1.C.Replacethefirstimagewiththesecondimagewiththe“image”tabselected,sothatreaderscanseebothversionsofthecontent

17

2.1.Makethetranscriptdownloadablein.txtformat(e.g.“downloadtranscripthere”)similartotheHathiTrustdigitallibrarywheremetadataisdownloadableintextformat(.txt).(HathiTrust,2018)

18

3.1.Audiodescription(ArtBeyondSight,n.d.)

19

4.1.Clearlabelingformetadata(confusionbetweentranscriptandmetadata):Objectdescription->Folderlevelmetadata&Description->Itemlevelmetadata.

20

5.1.A.Invisibleheadings–aheadingnotvisibletosightednotvisibletosightedusersbutreadablebyscreenreaders

5.1.B/6.1Invisiblelinkadded:SkiptoTranscriptlinktoactivatetexttabiflinktotranscriptisavailable

21

RelatedResources:Bitstreams(2018).InteractiveTranscriptshavearrived.Retrievedfromhttps://blogs.library.duke.edu/bitstreams/2018/02/16/interactive-transcripts-arrived/Griffin,E.(2015).Tipsformakingwebvideo&audioaccessible.http://www.3playmedia.com/2015/07/13/tips-for-making-web-video-audio-accessible/Graves,A.,Mohamed,A.R.,&Hinton,G.(2013).Speechrecognitionwithdeeprecurrentneuralnetworks.InAcoustics,speechandsignalprocessing(ICASSP),2013IEEEInternationalConference(pp.6645-6649).IEEE.

Hathitrust.(2018).Retrievedfromhttps://babel.hathitrust.org/cgi/mb?a=listis;c=464226859;sort=title_a;pn=1;lmt=ftIngle,R.R.,Fujii,Y.,Deselaers,T.,Baccash,J.,&Popat,A.C.(2019).AScalableHandwrittenTextRecognitionSystem.arXivpreprintarXiv:1904.09150.

Muehlberger,G.,Seaward,L.,Terras,M.,Oliveira,S.A.,Bosch,V.,Bryan,M.,…&Gatos,B.(2019).Transformingscholarshipinthearchivesthroughhandwrittentextrecognition.JournalofDocumentation.

PennState.CaptionGuidelinesandpolicy.Retrievedfromhttps://accessibility.psu.edu/video/captions/

22

Transcripts.(2019).Retrievedfromhttps://www.w3.org/WAI/media/av/transcripts/#where-to-put-transcripts.VideoCaptions.(2019).Retrievedfromhttps://www.w3.org/WAI/perspective-videos/captions/.WCAG2.1.(2018).2.4.6HeadingsandLabels.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.htmlXie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.

Zhong,Y.,Raman,T.V.,Burkhardt,C.,Biadsy,F.,&Bigham,J.P.(2014,April).JustSpeak:enablinguniversalvoicecontrolonAndroid.InProceedingsofthe11thWebforAllConference(p.36).ACM.

Seealso:Help-seekingSituations>DifficultyAccessingInformationHelp-seekingSituations>Difficultylocatingspecificinformation,itemsorfeatures

DifficultylocatingoraccessingmultimediacontrolsDefinition:Asituationthatarisesfromproblemsrelatedtolocatingoractivatingcontrolstoplayaudio/videofiles.Also,difficultyrecognizingwhetheraudioorvideooutputisgenerated,orthelengthorprogressleveloftheA/VmaterialplayinginaDL.

Factor(s):• • Unclearlabelingofaudio/videofilesandcontrolsofmediaplayers• Complexinformationpresentation• Toomanycontrolsinmediaplayers• Illogicalorderingofmediaplayercontrols• Lackoffeedbackfrommediaplayers• Lackofinstructionforoperatingmediaplayers

23

• UseofmediaplayersthatareincompatiblewithscreenreadersGuidelineorDesignRecommendation:1. Ensureusemultimediaplayerswithminimalplayercontrols2. Labeleachmultimediaplayercontrolinawaythatclearlyconveysitspurposeandfunction3. Ensureallmultimediaplayercontrolsareefficientlyaccessibleandoperable,including

keyboardcontrolandcompatibilitywithscreenreaders4. ProviderecognizableinformationaboutthelengthandprogressofanA/Vfileplayingina

DL5. Providemetadatainformationaboutmultimediaitems6. Provideinstructionsandhelpforaccessingaudio/videofilesRationaleandObjective:DLsofferarangeofaudio/videocontent.ThecomplexityoftheDLstructure,excessivegraphiccontent,andunlabeledcontrolsformanipulatingmultimediafilesdiscouragesBVIusersfromtryingtoaccessthesefiles.Clearinstructionsandkeyboard-accessibleinterfacedesignshouldbeprovidedtolocatethemediaandthecontrolstoplaythem.Textualformat,suchasalttextorARIA-labelsforthesecontrolsarerequired.Progressstatusistypicallyindicatedvisually(e.g.usingaprogressbarorsimilargraphic)inaformatthatisinaccessibletoBVIusers.Textualequivalentsshouldbeprovidedstatingthepercentageplayedorremaininginanaccessibletextualformat,orbyanaccessiblelabelindicatingthenameoftheobjectandthelevelofloadingprogress.Alternativeinformation,suchasaudiodescriptionscanbeusedifthevisualcontentinweb-basedaudio/videofilesprovidesinsufficientinformationtodescribethecontenttoBVIusers.Anydynamicfeatures,suchasFlash,shouldbeaccessiblebyBVIusers.

TechniquesandMethods:1.1.Utilizemediaplayerswiththesimplestandmoststandardizedcontrols(play,pause,stop,etc.)2.1.Provideameaningfullabelformultimediacontrolsthataccuratelyreflecttheirstate(e.g.play/pause)3.1.Providebasickeyboardaccessiblemultimediacontrolswithshortcuts(e.g.,play,stop,seek,rewind,forward,andspeedcontrol)3.2.AvoidusingFlashmediaorplayersunlesstheFlashcontentprovidesanaccessiblealternativethatisusablebyascreenreader4.1.Providesoundortextindicatorswhenloading,playingandstoppingaudio/videofile4.2.Providesoundortextindicatorsthatpresentthegeneraltimeestimateandvideolength4.3.Makeelementssuchasscriptsandappletstopresentloadingstatusdirectlyaccessibleorcompatiblewithassistivetechnologies.Looped-animationindicatorsshouldincludeatextexplanationoftheprocess.5.1.Specifytheavailabilityofaudioorvideocomponentsorlengthofmultimediafiles6.1.Provideinstructionsandgeneralcontext-sensitivehelportipsforaccessingaudio/videofiles

RecommendedFeatures:

24

1.1.Simpleandstandardizedcontrols2.1.MeaningfulLabelsoncontrols3.1.Keyboardaccessiblecontrols4.1.Soundortextindicators4.3.A.Accessibleloadingstatususingalternativetext4.3.B.Accessiblelooped-animationindicators5.1.Metadata6.1.Context-sensitivehelportips

Examples:1.1/2.1A.AccessibleYouTube(https://www.cs.unc.edu/~gb/Accessible-YouTube/index.html)2.1.B.Buttonlabelsappearas“Play”and“Pause”(e.g.,aria-label=”play”)

LibraryofCongressDigitalCollections

3.1.A.APlaybuttonshouldbereadbyscreenreaders(Thompson,2011)

25

3.1.B.UseYouTubewithascreenreader(https://support.google.com/youtube/answer/189278?hl=en)

3.2.AblePlayer(https://ableplayer.github.io/ableplayer/)4.1.Alternativetextforloadingimageorstatuslike“Videoisbeingloaded.50%ofloading.”

<divstyle=”visibility:hidden;display:none;right:0px;”role=”alertdialog”aria-busy=”true”aria-live=”assertive”><imgid=”processing”src=”PT_LOADING.gif”alt=”Processing…pleasewait”title=””/></div>

4.2.A.Audiodescription.Example:Anarratorsays,“Therearefiveimportantpoints.Theyare…20minvideo.”(10thandDecimals,2018)

4.2.B.Progressbartextupdated–http://www.afb.org/info/living-with-vision-loss/using-technology/assistive-technology-videos/screen-reading-technology/12355.1A.Descriptivemetadataaboutcontentcanbeprovidediftheaudio/videoisnotaccessible(e.g.,silentfilm)–DPLADPLAVideo:MiscellaneousVideo

5.1B.Descriptionsforlengthofanaudio/videofile

26

RelatedResources:3PlayMedia.(2020).Transcriptionvs.Captioning–What’sthedifference?.Retrievedfromhttps://www.3playmedia.com/2018/10/10/transcription-vs-captioning/10thsandDecimals.NationalScienceDigitalLibrary.(2018).Retrievedfromhttp://nsdl.oercommons.org/courses/10th-s-and-decimals/viewAblePlayer–Fullyaccessiblecross-browserHTML5mediaplayer.(2018).Retrievedfromhttps://ableplayer.github.io/ableplayer/AccessibilityOz:Videoaccessibilityprinciples.(2018).Retrievedfromhttps://www.accessibilityoz.com/factsheets/video/video-factsheet/AFB.DownloadtheAmericanFoundationfortheBlindAccessibleVideoPlayer,Version1.1.http://www.afb.org/info/programs-and-services/technology-evaluation/creating-accessible-websites/download-afbs-accessible-html5-video-player/1235CreatingAccessibleFlashContent.(2013).Retrievedfromhttps://webaim.org/techniques/flash/

27

Costa,L.C.,Almeida,N.S.,Correa,A.G.,Lopes,R.D.,&Zuffo,M.K.(2013).Accessibledisplaydesigntocontrolhomeareanetworks.IEEETransactionsonConsumerElectronics,59(2),422-427.

DigitalA11Y.AccessibleHTML5MediaPlayers@ResourcesRetrievedfromhttps://www.digitala11y.com/accessible-jquery-html5-media-players/Dolson,J.(2016),HowtoMakeVideosAccessibleforBlind,DisabledUsers.Retrievedfromhttps://www.practicalecommerce.com/How-to-Make-Videos-Accessible-for-Blind-Disabled-UsersDPLAVideo:MiscellaneousVideo.(2018).Retrievedfromhttps://dp.la/item/8abf2c3f4d5415613dadaf07fc238292?q=video&type=%22moving%20image%22&page=1HTMLLivingStandard.(2019).Retrievedfromhttps://html.spec.whatwg.org/#attr-media-autoplayUseYouTubewithascreenreader(https://support.google.com/youtube/answer/189278?hl=en)LibraryofCongressDigitalCollections.(2018).Retrievedfromhttps://www.loc.gov/item/00694020

Rodriguez-Sanchez,M.C.,Moreno-Alvarez,M.A.,Martin,E.,Borromeo,S.,&Hernandez-Tamames,J.A.(2014).Accessiblesmartphonesforblindusers:Acasestudyforawayfindingsystem.ExpertSystemswithApplications,41(16),7210-7222.

Sherwin,K.(2014).ProgressIndicatorsMakeaSlowSystemLessInsufferable.Retrievedfromhttps://www.nngroup.com/articles/progress-indicators/

Strumillo,P.,Skulimowski,P.,&Polanczyk,M.(2009).ProgrammingSymbiansmartphonesfortheblindandvisuallyimpaired.InComputersinMedicalActivity(pp.129-136).Springer,Berlin,Heidelberg.

TheAudioDescriptionProject.(n.d.).WhatisAudioDescription?Retrievedfromhttps://acb.org/adp/ad.htmlThompson,T.(2011).AccessibilityandtheYouTubePlayers.Retrievedfromhttp://terrillthompson.com/blog/44WebAim.(2013).Captions,Transcripts,andAudioDescriptions.https://webaim.org/techniques/captions/#ad

28

W3C.(2018).WCAG2.1Guideline1.4.2AudioControl.Retrievedfromhttps://www.w3.org/TR/WCAG21/#audio-controlW3C.(2018).WCAG2.1Guideline2.1.Keyboardaccessible.Retrievedfromhttps://www.w3.org/TR/WCAG21/#keyboard-accessibleW3C.(2018).WCAG2.1Guideline2.2.2Pause,Stop,Hide.Retrievedfromhttps://www.w3.org/TR/WCAG21/#pause-stop-hideW3C.(2018).WCAG2.1Guideline2.4.6HeadingsandLabels.Retrievedfromhttps://www.w3.org/TR/WCAG21/#headings-and-labelsW3C.(2018).WCAG2.1Guideline1.2.5AudioDescription(Prerecorded).Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.htmlW3C.(2018).WCAG2.1Guideline1.2.7ExtendedAudioDescription.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/extended-audio-description-prerecorded.htmlW3C.(2018).WCAG2.1Guideline1.2.Time-BasedMedia.Retrievedfromhttps://www.w3.org/TR/WCAG21/#time-based-mediaW3C.(2018).WCAG2.1Guideline1.2,Time-BasedMedia:ProvideAlternativesforTime-BasedMedia.Retrievedfromhttps://www.w3.org/TR/WCAG21/#time-based-mediaW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigable

Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),n2.

Zafar.A.(2017).Howtodesignaccessiblemobileexperiencesfortheblind.Retrievedfromhttps://willowtreeapps.com/ideas/how-to-design-accessible-mobile-experiences-for-the-blind


29

DifficultylocatingoraccessingsearchfeaturesDefinition:AsituationthatarisesfromadifficultyfindingoraccessingasearchfeatureinaDL,suchasasearchfilter,searchcategories,searchbox,searchsuggestions,oradvancedsearch.

Factor(s):

• Unclearlabeling• Complexinformationpresentation• Irrelevantsearchelements(needexamples)• Complex/unclearsearchstructure• Lackoftheindicationthatthereareauto-suggestions• LackoftheindicationthatthereistheadvancedsearchGuidelineorDesignRecommendation:1. OfferquickandeasypathstorelevantsearchfeaturesfromprominentlocationswithinaDL

page2. OfferrelevantsearchfunctionsatlogicallyappropriatelocationsonaDLpage3. Ensureeverycategoryofsearchfeatureshavesimilarfunctionsandappearanceforlarge

scaleDLsorintegratedDLs4. Labelsearchfeaturesandtheircomponentsinameaningfulway5. EnsuresearchfeaturesandtheircomponentsareaccessibletoBVIusersRationaleandObjective:TheremightbeseveralsearchfeaturesontheDLwebpage.AsearchboxisoneoftheprimaryelementsforausertofindrelevantinformationinaDL.Thisfeatureallowsuserstoinputkeywordstoexecuteasearchquery.Oncesearchresultsaregeneratedbythesearchkeywords/phrases,thoseresultscanoftenbefilteredbyadditionalcategoriesandfacets.DLsearchfeaturesaresometimesdifficultforBVIuserstolocate.Insomecases,thesesearchfeaturesarepositionedinasidewidgetthatisnotimmediatelyavailablewhenBVIusersarrowdownthroughthemaincontentregion.Therefore,itmightbehelpfulforBVIuserstoidentifysearchfeaturesiftheyareincludedintheupperormaincontentregionofthepage,andnotasidewidget.Furthermore,ifthesesearchfeaturesdonotspecifythattheyaresearchingwithinselectcategoriesratherthantheentireDLcollection,thismayleadtoconfusionfortheuser.Althoughauto-suggestionsareapopularfeature,someusersmightnotunderstandthatthereareauto-suggestions.Anindicationforthefeaturecanhelpuserstobenefitfromitwithoutconfusion.Anadvancedsearchfeaturemayoftenbeusedbymoreexperiencedusers.The

30

advancedsearchfeatureshouldbeplacednearthesimplesearchorbeavailableviaalinkfollowingthesimplesearch.

TechniquesandMethods:1.1.Provideskip-to-linkstoavarietyofsearchfeatureswithinaDL2.1.Placesearchfeatureorskip-to-linksinthetopnavigationregionofthepage3.1.Specifytherangeofthesearch(entiresite,withinacollection,withinresults,etc.)foreverysearchfeaturethroughrelevantlabels4.1.Placesubmitbuttonafterallothersearchfeatures/filters4.2.Addameaningfullabelforeachcomponentofeachfeature5.1.UseARIAelementstomakethesearchcomponentseasilyrecognizedandaccessible(Cifcioglu,2017)5.2.Addaccessibleheadingsbeforethesearchfeatures

RecommendedFeatures:1.1.Skip-to-searchfeaturelink3.1.Searchfeaturewithrange4.2.Meaningfullabels5.1.ARIAelements5.2.Accessibleheadings

Examples:2.1.A.Simplesearchboxaddedinthemainpageofthecollection.

2.1.B.Positionadvancedsearchfollowingsimplesearch–CONTENTdm

31

3.1.A.Specifysimplesearchtodifferentiatefromothertypesofsearches,suchasadvancedsearch,globalsearch,etc.

3.1.B.Addinstructionsasthelabelforthebox.

32

3.1.C.Addsearchtips.

4.2.A/5.2.A.<labelclass=”search-label”for=”search”>SearchaboutMarchonMilwaukee:</label><inputtype=”text”name=”search”id=”search”><inputtype=”text”name=”search”

4.2.B.Applylabelstounlabelededitfield->label(SimpleSearchEditSearchMarckonMilwaukee)

33

5.1.A.ARIA–combobox,listbox,andannounceelements(Cifcioglu,2017)

5.1.B.role=”combobox”inthe<input>field(informtoscreenreaderusers):theinputfieldisanauto-suggest;

5.1.C.aria-autocomplete=”both”inthe<input>field:screenreaderuserscanselectfromthesuggestionlistortypetheirowninput;

5.1.D.aria-ownstothe<input>fieldlinksthesuggestionlisttotheinputfield;

5.1.E.role=“listbox“inthesuggestionlist<div>containsalistofselectableitems;oraria-liveregions:1)Polite=thescreenreaderwillfinishwhatit’ssayingbeforeannouncingtheliveregioncontent2)Assertive=thescreenreaderwillinterruptwhatit’ssayingtoannouncethe

34

liveregioncontent3)Off=thescreenreaderwon’tannouncethecontentunlesstheuserfocusesonthatregion

5.1.F.ARIAeditableautocompletedropdown(https://www.w3.org/TR/wai-aria-practices/examples/combobox/aria1.1pattern/listbox-combo.html)

RelatedResources:Babich,N.(2017).DesignaPerfectSearchBox.https://uxplanet.org/design-a-perfect-search-box-b6baaf9599cBohman,P.(2013).HTML5Accessibility.Retrievedfromhttps://dequeuniversity.com/assets/html/jquery-summit/html5/slides/landmarks.htmlBustos,L.(2017).11TipsforAdvancedSearchUsability.Retrievedfromhttps://www.getelastic.com/advanced-search-usabilityCifcioglu,A.(2017).AnatomyofanAccessibleAutoSuggest.Retrievedfromhttps://uxmastery.com/anatomy-of-an-accessible-auto-suggest/FreedomScientific(2018).JAWSUIAScriptAPIDocumentationAccessibility.Retrievedfromhttps://www.freedomscientific.com/support/jawsdocumentation/UIAScriptAPIJacobS.(2013).5WaystoMakeYourE-CommerceWebsiteSearchFeatureConvert.Retrievedfromhttps://blog.kissmetrics.com/ecommerce-website-search/

LibraryofCongress.(2018).Searchhelp.Retrievedfromhttps://www.loc.gov/search/help/

W3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableW3C.(2017).WAI-ARIAAuthoringPractices1.1.Retrievedfromhttps://www.w3.org/TR/wai-aria-practices/Seealso:Help-seekingSituations>DifficultyAccessingInformationHelp-seekingSituations>Difficultylocatingspecificinformation,itemsorfeaturesHelp-seekingSituations>Difficultyconstructingorrefiningsearches>Difficultytrackingsearches

35

DifficultyEvaluatingInformation

DifficultyassessingformatofanitemDefinition:AsituationthatarisesfromadifficultydeterminingthefileformatofaniteminaDL

Factor(s):

• Unclearlabeling• Noalternativetext• Lackofdescription• LackofinstructionrelatedtospecificfileformatsGuidelineorDesignRecommendation:1. EnsurethefileformatofeachiteminaDLisclearlyspecifiedandprovidedtotheuser2. ProvideinstructionhowtouseeachfileformatRationaleandObjective:Theformatofanitem(e.g.photo,manuscript,audio,video,etc.)isaprimaryaccesspointforaBVIuserandneedstobeimmediatelyrecognizedbythescreenreader.IssuesarisewhentheuserisunabletodeterminewhattypeofresourcetheyareattemptingtoaccessintheDL.Forexample,“Text”asasimplemetadatadescriptorisambiguousinthatitcouldrefertoalinktoalternativetext,oritcouldrefertotheformatofanitem.ForBVIusers,therefore,thereneedstobeacleardescriptionforitemformattoclarifythat“Text”referstothetypeofdocument(e.g.scannedimageforamanuscript)andnotasupplementarytranscript;suchadistinctionwouldeliminatepotentialconfusionorsemanticambiguity.

TechniquesandMethods:1.1.DefinethemetadataresourcetypeofaDLitemusingDCMItypevocabularydesignations(e.g.text,sound,image,etc.)1.2.DefinethefileformatofaDLitemusingstandardizedInternetMediaTypevocabulary,formerlyknownasMIME(e.g.pdf,mp4,JPEG,etc.)1.3.SpecifythefileformatofaDLitemthroughitslabel2.1.Providegeneralhelponfrequentlyusedfileformatstoassistusersinrecognizingresourcetypes2.2.Providegeneralhelponinformationrelatedtosoftwareorapplicationtoolsneedtoaccessdifferentfileformatsofitems2.3.Providecontext-sensitivehelp(HelpTipsand/orinstructions)onhowtoaccesstheitemonfocus

36

RecommendedFeatures:1.1.Metadataresourcetype1.2.Metadatafileformat1.3.Labelwithfileformat2.1/2.2.GeneralHelp2.3.Helptipsand/orinstruction

Examples:1.2.Specificmetadatadescriptionofitemformats:e.g.“(scanned)imageforhand-writtenmanuscripts(jpg)”,“transcriptforanaudiointerviewfile(txt)”,“imageofnewspaper(tiff)”,“transcriptfornewspaperarticlephoto(pdf)”,“compoundobjectcontainingtwovideos,fivescreenshots,andonearticle”etc.

RelatedResources:IANA.org.(2020).InternetMediaType.Retrievedfromhttps://www.iana.org/assignments/media-types/media-types.xhtmlLibraryofCongress.RecommendedFormantStatement.Retrievedfromhttps://www.loc.gov/preservation/resources/rfs/index.htmlW3C.(2018).WCAG2.1Guideline1.1TextAlternatives.Retrievedfromhttps://www.w3.org/TR/WCAG21/#text-equivW3C.(2018).WCAG2.1Guideline1.2Time-basedMedia.Retrievedfromhttps://www.w3.org/TR/WCAG21/#time-based-mediaW3C.(2018).WCAG2.1Guideline1.3Adaptable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#adaptableW3C.(2018).WCAG2.1Guideline3.1Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readableXie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.SeeAlso:Help-seekingSituations>Difficultyevaluatinginformation

37

DifficultyassessingrelevanceofanitemDefinition:AsituationthatarisesfromadifficultyascertainingifanitemretrievedfromaDLcontainstheinformationrelevanttoaccomplishthetaskathand.Thisincludesadifficultytoefficientlyevaluaterelevanceatboththesearchresultslistlevelandatanindividualdocumentlevel.

Factor(s):

• Complexinformationpresentation• Unclearlabeling• Lackofcontextualinformation• Lackofdomainknowledge• Lackofsystemknowledge• Inadequatefeature• LackofdescriptiveinformationGuidelineorDesignRecommendation:1. Ensurethattheassociationbetweenqueryterms/relatedtermsandthesearchresults

list/eachretrieveditemareapparent2. Providedescriptiveinformationforeachiteminthesearchresults3. Provideinstructiononhowtoevaluatetherelevanceofaretrieveditematthesearch

resultslistlevelandattheindividualdocumentlevel4. AssistusersefficientlyevaluatesearchresultlistandretrievedindividualdocumentRationaleandObjective:InDLs,itisoftendifficultforBVIuserstodeterminewhycertainitemsareincludedinthesearchresults,whenintuitivelytheydonotappeartoberelatedtothesearchtermsorotherresults.Snippetsmightbehelpfulforunderstandingtherelevanceofanitemsincetheyusuallysummarize/describeanitemusingkeywords.Searchresultscanbequicklyaccessedthroughskiptolinks.Tomakesurethatresultsarerelevantintermsofcontent,itiscriticaltoclearlydescribetitlesandsummarieswithmeaningfulterms.

ItisoftenachallengeforBVIuserstoefficientlydeterminetherelevanceofindividualDLitemsreturnedbyasearchbecausetheinformationand/ordescriptionoftheitemareembeddedinacomplexinformationpresentation.ItisimportantthateachitemhaveaclearlydesignateddescriptionorsummaryabouttheresourcesothatBVIuserscanassessiftheitemmeetstheirinformationneed.Tofacilitatelocatingtheinformation,atextualsummaryortranscriptispreferred.Otherhelpfultechniquesincludeprovidingusertagsthatincludethesearchquerytermsoraviewer/tooloraudiodescriptiontoexplainthekeyfeaturesofvisualitems.

38

TechniquesandMethods:1.1.Addtags(e.g.,adding<strong>or<em>tags)toemphasizethequerytermsorrelatedtermsforbothsearchresultlistandindividualretrieveddocument1.2.Addheaderstoaparagraphthatcontainsquerytermsorrelatedtermswhenpossible(e.g.htmlfile,Pdfseeexample)forindividualretrieveddocument1.3.Suggestgroups(e.g.subjectsgrouporcollections)relatedtothesearchquery2.1.Provideasnippetofeveryiteminthesearchresultslistthatconsistsofasummary,includingkeytermsand/orrelevantparagraph(s)2.2.Displayusertagsandusercomments,whichcanincludetermsfromusers’perspectives2.3.Provideusefulandclearlylabeleditem-levelmetadata3.1.Providegeneralhelpinformation(e.g.usingbrowser’findfeaturetolookforqueryterms)explaininghowtodeterminetherelevanceofanitembeingreviewed3.2.Providecontext-sensitivehelptipsabouthowtoaccessdescriptiveinformationforthesearchresultlist4.1.Providetheoptionstosorttheresults(e.g.relevance,publicationtime,mediatype)4.2.Applyheadingtagstotitlesforeachoftheretrieveddocumentsinthesearchresultlist4.3.Provideaskiplinktogodirectlytosubject/collectionclustersatthetopofthepage

RecommendedFeatures:1.1.Emphasistag1.2.Paragraphheaders1.3.Subjectsorcollectionscluster2.1.Snippetsofcontentprovidedwitheachitem2.2.Usertagsandcomments2.3.Metadata3.1.Generalhelp,includingtextand/oraudioinstructions3.2.Context-sensitivehelptips4.1.Sorting/filteringoptions4.2.Headingtags4.3.Skiptolinktosubject/collection

Examples:2.3.Metadata(LibraryofCongressDigitallibrary,2018)

39

RelatedResources:AFB:TheVisuallyImpairedWebUser’sTechnology,Retrievedfromhttp://www.afb.org/info/programs-and-services/technology-evaluation/creating-accessible-websites/the-users-technology/1235ArtBeyondSight.(n.d.)Retrievedfromhttp://www.artbeyondsight.org/mei/verbal-description-training/samples-of-verbal-description/Chiti,S.,&Leporini,B.(2012,July).Accessibilityofandroid-basedmobiledevices:aprototypetoinvestigateinteractionwithblindusers.InInternationalConferenceonComputersforHandicappedPersons(pp.607-614).Springer,Berlin,Heidelberg.Do-It.(2017).Aretherestandardsorguidelinesforprovidingaudiodescription?Retrievedfromhttps://www.washington.edu/doit/are-there-standards-or-guidelines-providing-audio-descriptionLibraryofCongressDigitallibrary:Metadata.(2018).Retrievedfromhttps://www.loc.gov/item/2013651650/W3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.1Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readibleW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictable

40

Seealso:Help-seekingSituations>DifficultyEvaluatingInformation

41

DifficultywithHelp

DifficultydetectingorusingdynamicfeaturesandcontentDefinition:Asituationthatarisesfromadifficultyidentifyingorusingdynamicfeaturesandcontent.

Factor(s):

• Incompatibilitywithscreenreader• LackoffeedbackGuidelineorDesignRecommendation:1. EnsuredynamicfeaturesandcontentofaDLareaccessible2. Ensureaccessibilityofnotificationsforchangesorupdatesinfeaturesandcontent3. Informusersofthename,function,andstateoffeatures4. Offerassistanceindetectingandusingdynamicfeaturesandcontent5. ProvideinstructiononhowtodetectandusedynamicfeaturesandcontentRationaleandObjective:Comparedtostaticcontent,dynamiccontentiscontentthatchangesonapagewithoutre-loadingandwithoutanyinteractionwithusers.DynamicfeaturesmaybedifficultforBVIuserstoaccessiftheycannotinterpretthechangesincontent.Whencontentupdatesdynamically,screenreadersmaynotbeawareofchanges.Anychangesshouldbereportedbyscreenreaders,andthenewcontentshouldbedescribedfortheusereachtimethecontentchanges.

TechniquesandMethods:1.1.Mapdynamicfeaturesorcontenttokeyboardcommands1.2.Provideastaticversionofanydynamicfeaturesorcontentbylistingthemintheordertheyappearinthedynamicfeatureorcontent2.1./4.1.UseARIArolesandalertstonotifythechangesofdynamicfeaturesand/orcontent3.1.Provideanappropriatelabelreflectingthechangesforeachofthedynamicfeatures,associatedroleandcurrentstatus5.1.Providecontext-sensitivehelptipsdescribinghowtousedynamicfeaturesorcontent


42

1.1.Keyboard-accessiblefeaturesandcontent1.2.Staticversionofdynamiccontent2.1./4.1.ARIArolesandalerts3.1.Dynamiclabels5.1.Context-sensitivehelptips

Examples:1.2./2.1.A./4.1.A.CSScodestylestosupportkeyboardfocus–adda:focuswitha:hover.

a{color:black;background-color:white;text-decoration:underline}a:focus,a:hover{color:white;background-color:black;text-decoration:none}

2.1.B/4.1.B.ARIA&keyboardinteractionexample–expand/collapsehttps://www.w3.org/TR/wai-aria-practices-1.2/examples/accordion/accordion.html2.1.C/4.1.C/3.1.DynamiccontentusinganARIALiveRegion–http://schne324.github.io/live-region-playground/2.1.D/4.1.D.UsingARIALiveRegionsorrole=alerttoIdentifyErrors–http://pauljadam.com/demos/aria-alert-validation.html

RelatedResources:UCBerkeley.(2018).Top10TipsforMakingYourWebsiteAccessible.Retrievedfromhttps://webaccess.berkeley.edu/resources/tips/web-accessibility#accessible-dynamicUniversityofWashington.(2018).ProvidingVisibleFocusforKeyboardUsers.Retrievedfromhttps://www.washington.edu/accessibility/checklist/focus/W3C.(2018).WCAG2.1SuccessCriterion2.4.7FocusVisible(LevelAA).Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigation-mechanisms-focus-visibleSeealso:Help-seekingSituations>Difficultywithhelp

DifficultylocatingorunderstandinghelpinformationDefinition:

43

Asituationthatariseswhenausercannotfindtherelevanthelpinformation;whentheavailablehelpinformationisnoteasytounderstand;orwhentheavailablehelpinformationisnotusefulforthetaskathand.

Factor(s):

• LackofDLsystemknowledge• Lackofdomainknowledge• Complexinformationpresentation• Unclearinstruction• InadequatehelpGuidelineorDesignRecommendation:1. OfferhelpinformationrelevanttoalltaskssupportedbytheDL2. Assistusersinfindingrelevanthelpinformation3. Ensurehelpinformationisunderstandabletousersofallabilitylevels4. ExplainhowtoperformvariousfunctionsofaDLinameaningfulwayRationaleandObjective:UsersaccessingDLhelpinformationareusuallythosewhoareseekingadditionalinformationaboutorinstructionsonhowtouseDLfeatures.ForBVIusers,helpshouldbepresentedinclearlanguageintextualform.Explanationsshouldusecommonwordsratherthanjargon,asconciseaspossible,providinganaccurateexplanationofthepurposeandofferingsoftheDL.Whenusersneedmoreinformationaboutsomethingtheydon’tunderstand,itishelpfultoprovidelinkstorelatedinformation.Maintainingconsistentstructureacrosshelppageshelpsuserstobetterunderstandhelpinformationonvarioushelppages.

TechniquesandMethods:1.1.Setupascheduletoreviewandupdatehelppages1.2.MapeachhelpsectiontoeachofthetaskssupportedbyaDL2.1.Includelinkstocontext-sensitivehelpwithingeneralhelp2.2.Provideanoverviewofthehelptopics2.3.ProvidealinkforgeneralhelpatthetopofeveryDLpage.2.4.Dividehelpinformationintoshortsectionsandsubsections,usingheadingtagssuchas<H2>,<H4>,etc.2.5./3.1.Organizevarioussectionsofthehelppageinaconsistentstructureandformat3.2.Usesimplelanguagewithcommontermsratherthanjargonorprofessionallanguage3.3.Usesight-independentinstructionsorprovidealttextordescriptionsforvisualinstructiontopresenthelpinformation4.1Providestep-by-stepdirectionswithexamplesincompletingspecifictasksincontext-sensitivehelporsolvingcommonproblems(e.g.FAQ)4.2Includespecifichelptipsforscreenreaderusers

44

RecommendedFeatures:1.2.Comprehensivehelpcoverage2.1.Context-sensitivehelp2.1.Linkstocontext-sensitivehelp2.2.Helpoverview2.3.Prominenthelplink2.4.Headingtags2.5./3.1.Consistentstructureandformat3.2.Simplelanguage3.3.Nonvisualinstructionoralttext/description4.1.A.AStepbystepinstruction4.1.B.Examples4.2.Screenreadertips

Examples:2.2.Searchhelp(LibraryofCongress,2018)

RelatedResources:Snell,S.(2009).ClearandEffectiveCommunicationinWebDesign.Retrievedfromhttps://www.smashingmagazine.com/2009/02/clear-and-effective-communication-in-web-design/

45

W3C.(2018).WCAG2.1Guideline3.1Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readableSeealso:Help-seekingSituations>Difficultywithhelp

DifficultyrecognizingorinterpretingalabelDefinition:Asituationthatarisesfromthedifficultyunderstandingthemeaningoflabelsassociatedwithvariousfeatures,elements,orobjectswithintheDL.

Factor(s):

• Unclearlabeling• LackofsystemknowledgeGuidelineorDesignRecommendation:1. LabelfeaturesandelementsintheDLtoindicatetheirfunctions2. LabeltheitemsintheDLtoindicatethenatureofdocuments3. Ensuretheclarityofthepurpose,function,andoutcomeofusingfeaturesandelements4. Offerassistanceininterpretingthemeaningoflabelswhenevernecessary.RationaleandObjective:LabelingiscriticalindesigningaDLwebpage.Thefunctionoflabelsvarydependingontheirroleonthewebpage.BecauseDLsincludearangeofterminologyrelatedtothesystem,subject/topicareas,metadata,etc.,itisimportanttoprovideclearlabelsthatplainlydesignatethepurposeofthelabel.Labelingfornavigation,suchaslinks,shouldbefocusedon“wheretogo,”whilelabelingforidentificationofcontentsshoulddescribe“whatitis”byusingtitles,(sub)headings,taglines,orimageandvideocaptions.Foritemsdenotingadditionalinformation,labelingshouldexplaintherelationshipbetweenitems.Forwordswithallupper-casecharacters,somescreenreaders’defaultsettingistoreadupper-casetextletter-by-letter,therebyreducingreadabilityforBVIusers.

46

TechniquesandMethods:1.1.Describe“what”and“how”forthelabeloffeaturesandelements1.2.Labellinksconsistentlywiththetitleofthedestinationpage2.1.Describe“whatitis”forthelabelofanobject3.1.Usecommontermsinsteadofjargonwheneverpossible3.2.Avoidusingallupper-casecharactersinlabeling3.3.Addsupplementarytexttodescribethepurpose,function,andoutcomeoffeaturesandelementsifneeded4.1.ProvideaglossaryforthelabelsusedinaDL4.2.Providecontext-sensitivehelptipstopresenttheglossarytermforalabel

RecommendedFeatures:1.1.“What,”“how”orwheredescriptionsofafeatureorelementlabel2.1.“Whatitis”descriptionofanitemlabel3.1.Commonterminologies3.2.Mixed-caselabels3.3.Supplementarytext4.1.Glossary4.2.Context-sensitivehelptips

Examples:3.2.Donotlabelwithallcapitals.

(Source:Babich,2016)

RelatedResources:Babich,N.(2016).DesigningMoreEfficientForms:Structure,Inputs,LabelsandActions.Retrievedfromhttps://uxplanet.org/designing-more-efficient-forms-structure-inputs-labels-and-actions-e3a47007114f

47

Cutts,M.(2005).Gadgets,Google,andSEO.Retrievedfromhttps://www.mattcutts.com/blog/dashes-vs-underscores/Thurow,S.(2015).HowToCreateAWebsite’sNomenclature(OrLabelingSystem)ForOnlineFindability.Retrievedfromhttps://marketingland.com/create-websites-nomenclature-labeling-system-online-findability-131130WCAG2.0Guideline3.1Readable.(2008).Retrievedfromhttps://www.w3.org/TR/WCAG20/#meaningSeealso:Help-seekingSituations>Difficultywithhelp

DifficultyunderstandinghowtouseaDLDefinition:AsituationthatarisesfromdifficultyfiguringouthowtouseaDL,specificallydifficultygettingstartedinaDLordetermininghowtobestapproachtheDL.ThissituationtypicallyoccursatthestartofusingaDL.

Factor(s):

• Unclearinstructions• LackofDLsystemknowledge• Unclearlabeling• ComplexinformationpresentationGuidelineorDesignRecommendation:1. Clearlyconveythepurpose,functions,structure,andcoverageofaDL2. ProvideinstructiontoexplainhowtouseaDL3. ClearlyconveythepurposeofeachsectionofaDL4. ClearlyconveytheavailabilityofDLfeaturesandtheirfunctions5. EnsureDLfeedbackisaccessibleRationaleandObjective:

48

DLsshouldincludedescriptionsexplainingthepurposeoftheDLandinstructionsonhowtoeffectivelyusethesite.TheseintroductorydescriptionsshouldbeavailableinatextualformatforBVIusersandaccessiblethroughalinkormenu.Overallfeaturesshouldnavigable,operable,andusablewithascreenreader.UsingARIAfeaturescanbeeffectiveforascreenreadertoaccessinformationmoreeasily.DesigningalogicalwebpagelayoutshouldreduceaBVIuser’sneedtovisitinstructions.DLsthatoffercomplexpresentationofinformationorexcessivefunctions,suchasanavigationbarwithseverallinks,increaseaBVIuser’sloadastheuserattemptstogetorientedonhowtousetheDL,makingitdifficultfortheusertogetstarted.UnclearlabelsmakeusersquestionthepurposeoftheDL.CleardescriptionsinunderstandablelanguagearenecessaryforBVIuserstounderstandhowtobeginusingaDL,whichmaybeanewandunfamiliarsystem.Whenauserisnotclearonhowtousethesystem,tipsshouldbeprovidedtoorienttheuser.Providingadditionalinformationforthisorientation,suchaswhatthenextstepistousethesystem,orexplainingthepurposeofthesystem,mightbehelpfulforuserstorecognizetheutilityoftheDL.Theseinstructionsshouldbeprovidedinahelppage.

TechniquesandMethods:1.1.Providethepurpose,function,structure,andcoverageofaDLaspartof“AboutthisDL”(orsimilarlabel)asoneofthemenuitems2.1.ProvideaspecifichelppageincludinginstructionsonhowtousetheDL,accessibilityinstructionsforscreenreaderusers,andcontactinformationfortechsupport2.2.ProvideeasyaccesstohelpandFAQpages,suchas“Help”onmainmenu,onanavigationbar,orviainlinehelp3.1./4.1.Providemeaningfullabelsforsectionheadings,features,pagetitles,links,menus,tabs,forms,etc.4.2.Providecontext-sensitivehelptipsforDLfeatures5.1.Providetextorsoundalertstoconveythefeedback

RecommendedFeatures:1.1.Menuitems(e.g.AboutthiseDLorOverview)2.1.Helppagewithtutorials2.2.A.Listofshortcutsforscreenreadersusers2.2.B.HelpandFAQ3.1./4.1.Meaningfullabels4.2.Contextualhelptipsincluding:Hhelptipsand/inlinehelp5.1.Textorsoundalerts

Examples:1.1.A.Textdescriptionaboutacollection(LibraryofCongress,2018)

49

1.1.B./2.1.Help(Hathitrust,2018)

50

2.2.A.Helppagelink

51

2.2.B.Prominentlinktoexplicithelp(e.g.“Help”)inmenu

3.1./4.1.ClearlabelsreferencingtheDLcollection

52

4.2.Inlinehelp(e.g.Wikipedia)

53

RelatedResources:Hathitrust.(2018).Help–UsingtheDigitalLibrary.Retrievedfromhttps://www.hathitrust.org/help_digital_library#SearchTipsPatterson,M.(2017).BestPracticesforDesigningaHelpfulContactPage.Retrievedfromhttps://www.helpscout.net/helpu/contact-us-page-design/UCBerkley.(2018).Top10TipsforMakingYourWebsiteAccessible.Retrievedfromhttps://webaccess.berkeley.edu/resources/tips/web-accessibilityW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.1Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableSeealso:Help-seekingSituations>Difficultywithhelp

DifficultyunderstandingorusingaspecificfeatureDefinition:AsituationthatarisesfromadifficultyeitherunderstandingorusingafeatureofaDL.

Factor(s):

• Unintuitivefeatures• Unclearinstructions• Unclearlabelingoffeatures• LackofexperiencewithfeaturesGuidelineorDesignRecommendation:

54

1. Labelafeatureanditscomponentsreflectingtheirfunctionsbasedonuserexpectations2. Explainhowtouseafeatureeffectively3. OfferassistanceininteractingwithafeatureRationaleandObjective:FordesigninggeneralDLfeaturesandfunctions,thefirstconsiderationmightbewhetherthewebsiteisdesignedinalignmentwiththegoalormissionoftheDL.Withinthisframework,featuresorfunctionsshouldbedesignedbasedontheexpectationofusers.Forexample,BVIusersmayneedclarificationonthepurposeofafeatureandinstructiononhowtouseit.Instructionsforeachfeatureorfunctionshouldbeclearlydescribed.Forexample,step-by-steptutorialsorcontext-sensitiveinstructionalongsidethefeaturemightbehelpfultointerpretwhichcommandsneedtobeappliedtoactivatethefeature.Instructionsforfeaturesshouldbedescribedclearlyincommonlanguage.ManyDLsuseimagesorvisualsymbols,whichmightbeeffectiveforsightedusersbutmaypresentaproblemforBVIusers.TextualdescriptionsoffunctionsareneededforBVIusers.Sincedisplayingtoomanyfilteroptionsmayconfuseauser,someoptionscanbeprovidedasAdvancedSearchfeatures.

TechniquesandMethods:1.1.Designthelabelofafeatureindicatingitsfunctionbasedonuserneedsderivedfromauserstudyoruserfeedback1.2.Providetextlabelsanddescriptions(whichmayincorporateinvisibletextforsightedusers,)ratherthanimages1.3.UseWAI-ARIAtomakeDLfeaturesaccessibletoscreenreaders1.4.Provide“label”htmlcodetospecifythelabeland/orfunctionofafeature1.5.Applymeasuresforreadinglevel(e.g.Flesch-Kincaidgradelevel)toimprovethereadabilityoflabelsandinstructions2.1.Providestepbystepinstructions/tutorialsforeachfeature3.1.Providecontext-sensitivehelptipstoexplainhowtouseafeature3.2.Providefeedbackwhileauserisinteractingwithafeature

RecommendedFeatures:1.1.Intuitiveandspecificfeaturelabels1.2.Textlabelanddescription1.3.AccessiblefeaturesusingWAI-ARIA1.4.“label”HTMLcode2.1.Clearinstructions,step-by-steptutorials,ordemonstrations3.1.Content-sensitivehelptips3.2.Feedback

Examples1.1.A.Clearlabels

55

1.1.B.Removedfeaturesthataredifficulttoaccess.

56

1.2.Specificdescription.

57

1.4.Use“Label”htmlcodetofeatures

<labelfor=”French”>Whatisyourfavoritetypeofsaladdressing?<br>French</label><inputid=”French”type=”checkbox”name=”dressing1″value=”checkbox”><br><labelfor=”Italian”>Italian</label><inputid=”Italian”type=”checkbox”name=”dressing2″value=”checkbox”><br><labelfor=”Russian”>Russian</label><inputid=”Russian”type=”checkbox”name=”dressing3″value=”checkbox”>Retrievedfromhttps://www.afb.org/aw/5/2/147632.1.Europeanahelppage(Europeana,2018)

58

3.1.A.Invisibletextisaddedtoprovideanoveralldescriptionofthestructure:“Thesearchresultssectionconsistsofthreeareas:sortingoptions,displayoptions,andalistofsearchresults.”

3.1.B.Invisibledescription

59

RelatedResources:Babich,N.(2017).BestPracticesforSearchResults.Retrievedfromhttps://uxplanet.org/best-practices-for-search-results-1bbed9d7a311W3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#consistent-behaviorW3C.(2018).WCAG2.1Guideline3.3InputAssistance.Retrievedfromhttps://www.w3.org/TR/WCAG21/#minimize-errorWax,D.(2008).7EssentialGuidelinesForFunctionalDesign.Retrievedfromhttps://www.smashingmagazine.com/2008/08/7-essential-guidelines-for-functional-design/Xie,I.&Cool,C.(2009).Understandinghelpseekingwithinthecontextofsearchingdigitallibraries.JournaloftheAmericanSocietyforInformationScienceandTechnology,60(3),477-494.Seealso:Help-seekingSituations>Difficultywithhelp

60

DifficultyLocatingSpecificInformation,items,orfeatures

DifficultydetectingorlocatingsearchresultsDefinition:Asituationthatarisesfromoneofthefollowingdifficulties:detectingtheoutcomeofasearch,includingwhetherornotthesearchresultsaredisplayed;findingthesearchresults;anddeterminingwhethertheresultsreturnedreflectarecentlymodifiedsearchorarestilltheresultsofapriorsearch

Factor(s):

• Lackofsystemfeedback• Lackofappropriateheadinginformation• LackofcontextualinformationorcuesGuidelineorDesignRecommendation:1. Clearlylabeltheresultssectionforrecognizability2. ProvideashortcuttotheDLsearchresultlist3. Notifytheuserthatthequeryhasbeenprocessedandresultshavebeengenerated4. ProvideguidanceonhowtorecognizewhethersearchresultsweregeneratedorchangedRationaleandObjective:DLshavecomplexnavigationstructures;thereforeBVIusersneedtoexplorethepagetodeterminewhethertheresultshavebeendisplayed.ApplyingashortsoundindicatingsearchresultscanbehelpfulforaBVIusertorecognizethatsearchresultshavebeengeneratedinaDL.Inmanycases,whenBVIusersmodifytheirsearchtermsinthesearchbox,theyareunabletodeterminewhethernewresultshavebeengenerated.ProvidinganaudibleprogressindicatorwouldhelpBVIuserstopredicthowlongtheyshouldwaittogetthesearchresultsand/orwhethersearchresultshavebeendisplayed.Searchinstructionsortipscandescribethis.AdescriptionnearthetopofthepageorsearchboxspecifyingthatsearchresultsweregeneratedisasignificantmarkerforaBVIusertorecognizethatthesearchresultshavebeengeneratedandareaccessible.Applyingaheadingof“searchresults”atthetopoftheresultslistcanfacilitateeaseofnavigation.

61

TechniquesandMethods:1.1.Addaheadingtagtosearchresultssectiontitle2.1.Provideskiplinksandsectionheadersasshortcutstothesearchresults3.1.Usetextorsoundalertstoindicatethestatusofthesearchprogress3.2.Addtextand/orsoundalerttoindicatethatsearchresultsweregeneratedorupdated3.3.Displayanotificationnearthesearchboxindicatingthestatusofthesearchresults4.1.Providehelpinrecognizingwhensearchresultsaregenerated4.2.IncludesearchtermsandthenumberofresultsintheSearchResultsheading.AnARIAliveregionmightbeusedtospeakshorttextwithnumberofsearchresultsreturned,forexample:“pageloaded,2results”

RecommendedFeatures:1.1.SearchResultssectionheading2.1A.Sliplinks2.1B.Sectionheaders3.1/3.2.Sound/textindicator3.3.Statusnotification4.1.Tipsandhelp4.2.Searchterm(s)displayedinresultsheading

Examples:3.1./3.2.Soundindicationforawebpageupdate(pseudocode).

<script>functionplaySound(){//codeforplayroutine}</script><bodyonload=”playSound()”><h>Playasoundwheneverthewebpageisupdated</h></body>

3.3.Adescriptionfornoresult–SmithsonianInstitution

62

4.2.Aresultheader

63

RelatedResources:Barbich,N.(2017).AComprehensiveGuidetoWebDesign.Retrievedfromhttps://www.smashingmagazine.com/2017/11/comprehensive-guide-web-design/SmithsonianDigitalLibrary.(2018).Nosearchresultpage.Retrievedfromhttps://library.si.edu/gsearch/dianosauW3C.(2018).WCAG2.13.2.5ChangeonRequest.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/change-on-request.htmlSeeAlso:Help-seekingSituations>Difficultylocatingspecificinformation,itemsorfeaturesHelp-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

64

Difficultylocatingaspecificword,phrase,orrelatedtermDefinition:Asituationthatarisesfromadifficultyfindingaword,phrase,orrelatedtermwithinthetextcontentofaDL.

Factor(s):

• Complexinformationpresentation• Lackofdescription• LackofindicatorsforkeytermsGuidelineorDesignRecommendation:1. Enabletextsearchingwithinthecaptioningortranscriptofavideoitem2. Supporttextsearchforrelatedterms3. Provideinstructionshowtoperformtextsearch(e.g.aspecificword,phraseorrelated

term)withinaDL4. EnsuretheoutputoftextsearchisaccessibleRationaleandObjective:SinceBVIuserscannotquicklyskimthecontentofapage,BVIusersoftenusethedesignatedscreenreaderFindfunction,whichisthesameas“Ctrl+F”forsightedusers.Exactmatchingforaspecificwordcanbeextendedtorecommendedrelatedwordsorsuggestedspellingrevisions.SearchtoolsthatusehighlightingorboldingoffoundtermsarenotnecessarilyusefulforBVIusersbecausetheymaynotberecognizedbyscreenreadersoftware.Instead,othertypesofnon-visualindicatorsareneeded.Sometimespageshavemetadataorkeywordsthatarenotdisplayedonthescreenbutcauseapagetoappearinthe“search”results.Whenauserperformsa“find”inthepage,nothingisfound.Thiscanbeveryconfusingandfrustrating.Audiotracksofaudioandvideoitemsaredifficultorimpossibletosearch,sohavingtheabilitytosearchthecaptiontrackofanaudioorvideoitemishelpful.

TechniquesandMethods:1.1.Providethecaption/transcriptofavideoitemasaseparatesearchabledocument(e.g.,PDF)2.1.IncorporateadictionarywithrelatedtermsintoaDL3.1.Providesearchtipsandinstructiononhowtoperformatextsearch4.1.Useheadingtagstohighlighttheresultsoftextsearch


65

1.1.Caption/transcriptassearchabledocument2.1.Findrelatedterms3.1.Searchtipsandinstruction4.1.Headingtags

Examples:1.1.Caption/transcriptassearchabledocument

4.1.Headingaddedfortheinputtedterm

66

RelatedResources:W3C.(2018).WCAG2.1Guideline3.1Readable.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/readableW3C.(2018).WCAG2.1Guideline3.3InputAssistance.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/input-assistanceWeakley,R.(2017).Buildinganaccessibleauto-complete.Retrievedfromhttps://www.slideshare.net/maxdesign/building-an-accessible-autocompleteWishYouCouldSearchWithinaVideo?UseanInteractiveTranscript!.Retrievedfromhttps://www.3playmedia.com/2018/10/10/search-interactive-transcript/

67

Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.YoutubeSubtitlesSearch.Retrievedfromhttps://chrome.google.com/webstore/detail/youtube-subtitles-search/aijacjhncladoajlfgeffggcbbopcljc?hl=en-USSeeAlso:Help-seekingSituations>Difficultylocatingspecificinformation,itemsorfeatures

DifficultylocatingmetadataDefinition:AsituationthatarisesfromadifficultyinfindingthemetadataforaDLitem

Factor(s):

• Lackofthevisibilityofmetadata• LackoflabelingformetadataGuidelineorDesignRecommendation:1. Offeraquickandeasywaytofindeachelementofthemetadataforanitem.2. OfferaquickandeasywaytoidentifyeachelementofthemetadataforanitemRationaleandObjective:Metadataisnotthecontentitself,butratherdescriptiveinformationaboutthecontent.Itmayincludeinformationaboutthetype,subject,author,place,etc.Sometimesmetadataisplacedfarawayfromapagetitle,whichmakesitdifficultforBVIuserstolocate.ThedesignofDLmayinformusersthatthereismetadatabyprovidingalinkorbyplacingthemetadatadirectlybelowthepagetitle.ProvidingaheaderforthemetadatasectionmayhelpBVIuserslocateit.

TechniquesandMethods:1.1.Presentmetadatadirectlybeloworneartheitem1.2.Provideaninternallinktoametadatasectionifmetadatacannotbeplacedclosetotheitem1.3.Useheadingtagsformetadatasection

68

2.1.ProvideconsistentlabelsformetadataelementsthroughoutaDL2.2.Providealttextforthedefinitionofeachelementofmetadata

RecommendedFeatures:1.2.Internallinks1.3.Sectionheadings2.1.Consistentlabels2.2Alttext

Examples:1.2.Metadatalink.

RelatedResources:MinnesotaHistoricalSociety.(2012).ElectronicRecordsManagementGuidelines.Retrievedfromhttp://www.mnhs.org/preserve/records/electronicrecords/ermetadata.phpSeeAlso:Help-seekingSituations>Difficultylocatingspecificinformation,itemsorfeatures

DifficultylocatingoraccessinginformationrelatedtovisualitemsDefinition:Asituationthatarisesfromthedifficultytofindandgainaccesstoalternativetext,transcriptsordescriptionforvisualitemsinadigitallibrary.

Factor(s):

• Unavailabilityorlackoftranscriptsforvisualitems• Unclearlabelingofcontrolsformediaplayers

69

• Complexinformationpresentation• Toomanyclicksrequiredtoaccessatranscript• Lackofashortcuttoatranscript(e.g.headingorinvisiblelinks)GuidelineorDesignRecommendation8. Provideconciseandmeaningfulalternativetextforallvisualitems9. Providetranscriptsforimagesoftextdocuments10. Provideaudiodescriptionsforvideomaterials11. Providedescriptivemetadataforeachimageorvideoitem12. Ensurealternativetext,transcriptsanddescriptionsforvisualitemscanbeeasilylocated13. Ensurealternativetext,transcriptsanddescriptionsforvisualitemscanbeeasilyaccessed14. Providehelpinformationregardingalternativetext,transcript,ordescriptionaccessRationaleandObjective:ProvidingatexttranscriptforanimageoravideoitemishelpfulforBVIuserstosearchforakeywordorscanoverallcontent.Specifically,sinceDLsincludearangeofheterogeneouscontent,includingillustratedbooks,photos,maps,manuscripts,etc.,itisnecessarytoincludeatexttranscriptinadocumentformthatisaccessible.Preferably,thetranscriptshouldbeinmarkuplanguageforwebpages,suchasHTML/XMLdocumentformat,asitisconsideredtobemosteasilyaccessiblebyscreenreaders.Regardingdownloadableformats,becausePDFformattypicallyrequiresup-to-dateassistivetechnologyandaplug-inforaccessingthePDFfiles,MicrosoftWordformatmightbemoreappropriate.Acaptionandmetadatashouldalsobeprovidedtoofferadditionalinformationalongwiththetranscript.Also,providingaclearlabelforthetranscriptisimportantbecause“text”metadatareferstotexttype,butBVIusersmaymistakethistermtomean“transcript.”ItmightbebeneficialtoaddinvisibleheadingsforBVIuserstosupporteaseofnavigation.

TechniquesandMethods:1.1.Provideasupplementarydescriptionforavisualitemnexttotheitemwithaclearlabel2.1.Provideanoptiontodownloadatranscriptofavisualitem2.2.Providepartialtranscriptsiffulltranscriptsareunavailable,andclearlyindicateapartialtranscriptisavailableforavisualitem3.1.Offeraudiodescriptionforscenesofvideosbetweendialogues4.1.Provideaclearandconcisedescriptionofavisualitemsinmetadata5.1.Provideanoptionfortranscriptdisplaynexttoavisualitem5.2.Add“Transcript”asinvisiblepartofthetitleforaheading5.1./6.1.Addaninvisible“Skiptotranscript”link7.1.Provideacontext-sensitivedescriptionforinformationembeddedinavisualitem.Forexample,iftheimageportraysprotestorsholdingasignfortheirprotest,BVIaudiencesshouldbeprovidedwithcontextualinformationonthebroadermeaningofthesigninadditiontothetextorthevisualimage.


70

1.1.A.Alttext1.1.B.Meaningfullabels2.1.Downloadabletranscriptfeature2.2.Transcriptdisplayfeature3.1.Invisibleaudiodescriptioncontrols4.1.Descriptionelementinmetadata5.1./6.1.Skip-to-transcriptlinks5.2.Invisibleheadings7.1.Context-sensitivedescription

Examples:1.1.A.Enabledtranscriptfeaturethatprovidesatext-basedrepresentationofthevisualcontent

1.1.B.Use“accessinterview”,“viewmovie”,or“listentoaudiorecording.”Inthemediaexample,linkstothemediaopenedinanewbrowsertab,butthisbehaviorwasnotindicatedwiththelink.Anattributetitle=“Opensinnewwindow”wouldhaveaddressedtheissue.

1.1.C.Replacethefirstimagewiththesecondimagewiththe“image”tabselected,sothatreaderscanseebothversionsofthecontent

2.1.Makethetranscriptdownloadablein.txtformat(e.g.“downloadtranscripthere”)similartotheHathiTrustdigitallibrarywheremetadataisdownloadableintextformat(.txt).(HathiTrust,2018)

71

3.1.Audiodescription(ArtBeyondSight,n.d.)

72

4.1.Clearlabelingformetadata(confusionbetweentranscriptandmetadata):Objectdescription->Folderlevelmetadata&Description->Itemlevelmetadata.

73

5.1.A.Invisibleheadings–aheadingnotvisibletosightednotvisibletosightedusersbutreadablebyscreenreaders

5.1.B/6.1Invisiblelinkadded:SkiptoTranscriptlinktoactivatetexttabiflinktotranscriptisavailable

74

RelatedResources:Bitstreams(2018).InteractiveTranscriptshavearrived.Retrievedfromhttps://blogs.library.duke.edu/bitstreams/2018/02/16/interactive-transcripts-arrived/Griffin,E.(2015).Tipsformakingwebvideo&audioaccessible.http://www.3playmedia.com/2015/07/13/tips-for-making-web-video-audio-accessible/Graves,A.,Mohamed,A.R.,&Hinton,G.(2013).Speechrecognitionwithdeeprecurrentneuralnetworks.InAcoustics,speechandsignalprocessing(ICASSP),2013IEEEInternationalConference(pp.6645-6649).IEEE.

Hathitrust.(2018).Retrievedfromhttps://babel.hathitrust.org/cgi/mb?a=listis;c=464226859;sort=title_a;pn=1;lmt=ftIngle,R.R.,Fujii,Y.,Deselaers,T.,Baccash,J.,&Popat,A.C.(2019).AScalableHandwrittenTextRecognitionSystem.arXivpreprintarXiv:1904.09150.

Muehlberger,G.,Seaward,L.,Terras,M.,Oliveira,S.A.,Bosch,V.,Bryan,M.,…&Gatos,B.(2019).Transformingscholarshipinthearchivesthroughhandwrittentextrecognition.JournalofDocumentation.

PennState.CaptionGuidelinesandpolicy.Retrievedfromhttps://accessibility.psu.edu/video/captions/

75

Transcripts.(2019).Retrievedfromhttps://www.w3.org/WAI/media/av/transcripts/#where-to-put-transcripts.VideoCaptions.(2019).Retrievedfromhttps://www.w3.org/WAI/perspective-videos/captions/.WCAG2.1.(2018).2.4.6HeadingsandLabels.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/headings-and-labels.htmlXie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.

Zhong,Y.,Raman,T.V.,Burkhardt,C.,Biadsy,F.,&Bigham,J.P.(2014,April).JustSpeak:enablinguniversalvoicecontrolonAndroid.InProceedingsofthe11thWebforAllConference(p.36).ACM.


DifficultylocatingoraccessingmultimediacontrolsDefinition:Asituationthatarisesfromproblemsrelatedtolocatingoractivatingcontrolstoplayaudio/videofiles.Also,difficultyrecognizingwhetheraudioorvideooutputisgenerated,orthelengthorprogressleveloftheA/VmaterialplayinginaDL.

Factor(s):• • Unclearlabelingofaudio/videofilesandcontrolsofmediaplayers• Complexinformationpresentation• Toomanycontrolsinmediaplayers• Illogicalorderingofmediaplayercontrols• Lackoffeedbackfrommediaplayers• Lackofinstructionforoperatingmediaplayers• Useofmediaplayersthatareincompatiblewithscreenreaders

76

GuidelineorDesignRecommendation:7. Ensureusemultimediaplayerswithminimalplayercontrols8. Labeleachmultimediaplayercontrolinawaythatclearlyconveysitspurposeandfunction9. Ensureallmultimediaplayercontrolsareefficientlyaccessibleandoperable,including

keyboardcontrolandcompatibilitywithscreenreaders10. ProviderecognizableinformationaboutthelengthandprogressofanA/Vfileplayingina

DL11. Providemetadatainformationaboutmultimediaitems12. Provideinstructionsandhelpforaccessingaudio/videofilesRationaleandObjective:DLsofferarangeofaudio/videocontent.ThecomplexityoftheDLstructure,excessivegraphiccontent,andunlabeledcontrolsformanipulatingmultimediafilesdiscouragesBVIusersfromtryingtoaccessthesefiles.Clearinstructionsandkeyboard-accessibleinterfacedesignshouldbeprovidedtolocatethemediaandthecontrolstoplaythem.Textualformat,suchasalttextorARIA-labelsforthesecontrolsarerequired.Progressstatusistypicallyindicatedvisually(e.g.usingaprogressbarorsimilargraphic)inaformatthatisinaccessibletoBVIusers.Textualequivalentsshouldbeprovidedstatingthepercentageplayedorremaininginanaccessibletextualformat,orbyanaccessiblelabelindicatingthenameoftheobjectandthelevelofloadingprogress.Alternativeinformation,suchasaudiodescriptionscanbeusedifthevisualcontentinweb-basedaudio/videofilesprovidesinsufficientinformationtodescribethecontenttoBVIusers.Anydynamicfeatures,suchasFlash,shouldbeaccessiblebyBVIusers.

TechniquesandMethods:1.1.Utilizemediaplayerswiththesimplestandmoststandardizedcontrols(play,pause,stop,etc.)2.1.Provideameaningfullabelformultimediacontrolsthataccuratelyreflecttheirstate(e.g.play/pause)3.1.Providebasickeyboardaccessiblemultimediacontrolswithshortcuts(e.g.,play,stop,seek,rewind,forward,andspeedcontrol)3.2.AvoidusingFlashmediaorplayersunlesstheFlashcontentprovidesanaccessiblealternativethatisusablebyascreenreader4.1.Providesoundortextindicatorswhenloading,playingandstoppingaudio/videofile4.2.Providesoundortextindicatorsthatpresentthegeneraltimeestimateandvideolength4.3.Makeelementssuchasscriptsandappletstopresentloadingstatusdirectlyaccessibleorcompatiblewithassistivetechnologies.Looped-animationindicatorsshouldincludeatextexplanationoftheprocess.5.1.Specifytheavailabilityofaudioorvideocomponentsorlengthofmultimediafiles6.1.Provideinstructionsandgeneralcontext-sensitivehelportipsforaccessingaudio/videofiles

RecommendedFeatures:1.1.Simpleandstandardizedcontrols2.1.MeaningfulLabelsoncontrols

77

3.1.Keyboardaccessiblecontrols4.1.Soundortextindicators4.3.A.Accessibleloadingstatususingalternativetext4.3.B.Accessiblelooped-animationindicators5.1.Metadata6.1.Context-sensitivehelportips

Examples:1.1/2.1A.AccessibleYouTube(https://www.cs.unc.edu/~gb/Accessible-YouTube/index.html)2.1.B.Buttonlabelsappearas“Play”and“Pause”(e.g.,aria-label=”play”)

LibraryofCongressDigitalCollections

3.1.A.APlaybuttonshouldbereadbyscreenreaders(Thompson,2011)

3.1.B.UseYouTubewithascreenreader(https://support.google.com/youtube/answer/189278?hl=en)

78

3.2.AblePlayer(https://ableplayer.github.io/ableplayer/)4.1.Alternativetextforloadingimageorstatuslike“Videoisbeingloaded.50%ofloading.”

<divstyle=”visibility:hidden;display:none;right:0px;”role=”alertdialog”aria-busy=”true”aria-live=”assertive”><imgid=”processing”src=”PT_LOADING.gif”alt=”Processing…pleasewait”title=””/></div>

4.2.A.Audiodescription.Example:Anarratorsays,“Therearefiveimportantpoints.Theyare…20minvideo.”(10thandDecimals,2018)

4.2.B.Progressbartextupdated–http://www.afb.org/info/living-with-vision-loss/using-technology/assistive-technology-videos/screen-reading-technology/12355.1A.Descriptivemetadataaboutcontentcanbeprovidediftheaudio/videoisnotaccessible(e.g.,silentfilm)–DPLADPLAVideo:MiscellaneousVideo

5.1B.Descriptionsforlengthofanaudio/videofile

79

RelatedResources:3PlayMedia.(2020).Transcriptionvs.Captioning–What’sthedifference?.Retrievedfromhttps://www.3playmedia.com/2018/10/10/transcription-vs-captioning/10thsandDecimals.NationalScienceDigitalLibrary.(2018).Retrievedfromhttp://nsdl.oercommons.org/courses/10th-s-and-decimals/viewAblePlayer–Fullyaccessiblecross-browserHTML5mediaplayer.(2018).Retrievedfromhttps://ableplayer.github.io/ableplayer/AccessibilityOz:Videoaccessibilityprinciples.(2018).Retrievedfromhttps://www.accessibilityoz.com/factsheets/video/video-factsheet/AFB.DownloadtheAmericanFoundationfortheBlindAccessibleVideoPlayer,Version1.1.http://www.afb.org/info/programs-and-services/technology-evaluation/creating-accessible-websites/download-afbs-accessible-html5-video-player/1235CreatingAccessibleFlashContent.(2013).Retrievedfromhttps://webaim.org/techniques/flash/

80

Costa,L.C.,Almeida,N.S.,Correa,A.G.,Lopes,R.D.,&Zuffo,M.K.(2013).Accessibledisplaydesigntocontrolhomeareanetworks.IEEETransactionsonConsumerElectronics,59(2),422-427.

DigitalA11Y.AccessibleHTML5MediaPlayers@ResourcesRetrievedfromhttps://www.digitala11y.com/accessible-jquery-html5-media-players/Dolson,J.(2016),HowtoMakeVideosAccessibleforBlind,DisabledUsers.Retrievedfromhttps://www.practicalecommerce.com/How-to-Make-Videos-Accessible-for-Blind-Disabled-UsersDPLAVideo:MiscellaneousVideo.(2018).Retrievedfromhttps://dp.la/item/8abf2c3f4d5415613dadaf07fc238292?q=video&type=%22moving%20image%22&page=1HTMLLivingStandard.(2019).Retrievedfromhttps://html.spec.whatwg.org/#attr-media-autoplayUseYouTubewithascreenreader(https://support.google.com/youtube/answer/189278?hl=en)LibraryofCongressDigitalCollections.(2018).Retrievedfromhttps://www.loc.gov/item/00694020

Rodriguez-Sanchez,M.C.,Moreno-Alvarez,M.A.,Martin,E.,Borromeo,S.,&Hernandez-Tamames,J.A.(2014).Accessiblesmartphonesforblindusers:Acasestudyforawayfindingsystem.ExpertSystemswithApplications,41(16),7210-7222.

Sherwin,K.(2014).ProgressIndicatorsMakeaSlowSystemLessInsufferable.Retrievedfromhttps://www.nngroup.com/articles/progress-indicators/

Strumillo,P.,Skulimowski,P.,&Polanczyk,M.(2009).ProgrammingSymbiansmartphonesfortheblindandvisuallyimpaired.InComputersinMedicalActivity(pp.129-136).Springer,Berlin,Heidelberg.

TheAudioDescriptionProject.(n.d.).WhatisAudioDescription?Retrievedfromhttps://acb.org/adp/ad.htmlThompson,T.(2011).AccessibilityandtheYouTubePlayers.Retrievedfromhttp://terrillthompson.com/blog/44WebAim.(2013).Captions,Transcripts,andAudioDescriptions.https://webaim.org/techniques/captions/#ad

81

W3C.(2018).WCAG2.1Guideline1.4.2AudioControl.Retrievedfromhttps://www.w3.org/TR/WCAG21/#audio-controlW3C.(2018).WCAG2.1Guideline2.1.Keyboardaccessible.Retrievedfromhttps://www.w3.org/TR/WCAG21/#keyboard-accessibleW3C.(2018).WCAG2.1Guideline2.2.2Pause,Stop,Hide.Retrievedfromhttps://www.w3.org/TR/WCAG21/#pause-stop-hideW3C.(2018).WCAG2.1Guideline2.4.6HeadingsandLabels.Retrievedfromhttps://www.w3.org/TR/WCAG21/#headings-and-labelsW3C.(2018).WCAG2.1Guideline1.2.5AudioDescription(Prerecorded).Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/audio-description-prerecorded.htmlW3C.(2018).WCAG2.1Guideline1.2.7ExtendedAudioDescription.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/extended-audio-description-prerecorded.htmlW3C.(2018).WCAG2.1Guideline1.2.Time-BasedMedia.Retrievedfromhttps://www.w3.org/TR/WCAG21/#time-based-mediaW3C.(2018).WCAG2.1Guideline1.2,Time-BasedMedia:ProvideAlternativesforTime-BasedMedia.Retrievedfromhttps://www.w3.org/TR/WCAG21/#time-based-mediaW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigable

Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),n2.

Zafar.A.(2017).Howtodesignaccessiblemobileexperiencesfortheblind.Retrievedfromhttps://willowtreeapps.com/ideas/how-to-design-accessible-mobile-experiences-for-the-blind


82

DifficultylocatingoraccessingsearchfeaturesDefinition:AsituationthatarisesfromadifficultyfindingoraccessingasearchfeatureinaDL,suchasasearchfilter,searchcategories,searchbox,searchsuggestions,oradvancedsearch.

Factor(s):

• Unclearlabeling• Complexinformationpresentation• Irrelevantsearchelements(needexamples)• Complex/unclearsearchstructure• Lackoftheindicationthatthereareauto-suggestions• LackoftheindicationthatthereistheadvancedsearchGuidelineorDesignRecommendation:6. OfferquickandeasypathstorelevantsearchfeaturesfromprominentlocationswithinaDL

page7. OfferrelevantsearchfunctionsatlogicallyappropriatelocationsonaDLpage8. Ensureeverycategoryofsearchfeatureshavesimilarfunctionsandappearanceforlarge

scaleDLsorintegratedDLs9. Labelsearchfeaturesandtheircomponentsinameaningfulway10. EnsuresearchfeaturesandtheircomponentsareaccessibletoBVIusersRationaleandObjective:TheremightbeseveralsearchfeaturesontheDLwebpage.AsearchboxisoneoftheprimaryelementsforausertofindrelevantinformationinaDL.Thisfeatureallowsuserstoinputkeywordstoexecuteasearchquery.Oncesearchresultsaregeneratedbythesearchkeywords/phrases,thoseresultscanoftenbefilteredbyadditionalcategoriesandfacets.DLsearchfeaturesaresometimesdifficultforBVIuserstolocate.Insomecases,thesesearchfeaturesarepositionedinasidewidgetthatisnotimmediatelyavailablewhenBVIusersarrowdownthroughthemaincontentregion.Therefore,itmightbehelpfulforBVIuserstoidentifysearchfeaturesiftheyareincludedintheupperormaincontentregionofthepage,andnotasidewidget.Furthermore,ifthesesearchfeaturesdonotspecifythattheyaresearchingwithinselectcategoriesratherthantheentireDLcollection,thismayleadtoconfusionfortheuser.Althoughauto-suggestionsareapopularfeature,someusersmightnotunderstandthatthereareauto-suggestions.Anindicationforthefeaturecanhelpuserstobenefitfromitwithoutconfusion.Anadvancedsearchfeaturemayoftenbeusedbymoreexperiencedusers.The

83

advancedsearchfeatureshouldbeplacednearthesimplesearchorbeavailableviaalinkfollowingthesimplesearch.

TechniquesandMethods:1.1.Provideskip-to-linkstoavarietyofsearchfeatureswithinaDL2.1.Placesearchfeatureorskip-to-linksinthetopnavigationregionofthepage3.1.Specifytherangeofthesearch(entiresite,withinacollection,withinresults,etc.)foreverysearchfeaturethroughrelevantlabels4.1.Placesubmitbuttonafterallothersearchfeatures/filters4.2.Addameaningfullabelforeachcomponentofeachfeature5.1.UseARIAelementstomakethesearchcomponentseasilyrecognizedandaccessible(Cifcioglu,2017)5.2.Addaccessibleheadingsbeforethesearchfeatures

RecommendedFeatures:1.1.Skip-to-searchfeaturelink3.1.Searchfeaturewithrange4.2.Meaningfullabels5.1.ARIAelements5.2.Accessibleheadings

Examples:2.1.A.Simplesearchboxaddedinthemainpageofthecollection.

2.1.B.Positionadvancedsearchfollowingsimplesearch–CONTENTdm

84

3.1.A.Specifysimplesearchtodifferentiatefromothertypesofsearches,suchasadvancedsearch,globalsearch,etc.

3.1.B.Addinstructionsasthelabelforthebox.

85

3.1.C.Addsearchtips.

4.2.A/5.2.A.<labelclass=”search-label”for=”search”>SearchaboutMarchonMilwaukee:</label><inputtype=”text”name=”search”id=”search”><inputtype=”text”name=”search”

4.2.B.Applylabelstounlabelededitfield->label(SimpleSearchEditSearchMarckonMilwaukee)

86

5.1.A.ARIA–combobox,listbox,andannounceelements(Cifcioglu,2017)

5.1.B.role=”combobox”inthe<input>field(informtoscreenreaderusers):theinputfieldisanauto-suggest;

5.1.C.aria-autocomplete=”both”inthe<input>field:screenreaderuserscanselectfromthesuggestionlistortypetheirowninput;

5.1.D.aria-ownstothe<input>fieldlinksthesuggestionlisttotheinputfield;

5.1.E.role=“listbox“inthesuggestionlist<div>containsalistofselectableitems;oraria-liveregions:1)Polite=thescreenreaderwillfinishwhatit’ssayingbeforeannouncingtheliveregioncontent2)Assertive=thescreenreaderwillinterruptwhatit’ssayingtoannouncethe

87

liveregioncontent3)Off=thescreenreaderwon’tannouncethecontentunlesstheuserfocusesonthatregion

5.1.F.ARIAeditableautocompletedropdown(https://www.w3.org/TR/wai-aria-practices/examples/combobox/aria1.1pattern/listbox-combo.html)

RelatedResources:Babich,N.(2017).DesignaPerfectSearchBox.https://uxplanet.org/design-a-perfect-search-box-b6baaf9599cBohman,P.(2013).HTML5Accessibility.Retrievedfromhttps://dequeuniversity.com/assets/html/jquery-summit/html5/slides/landmarks.htmlBustos,L.(2017).11TipsforAdvancedSearchUsability.Retrievedfromhttps://www.getelastic.com/advanced-search-usabilityCifcioglu,A.(2017).AnatomyofanAccessibleAutoSuggest.Retrievedfromhttps://uxmastery.com/anatomy-of-an-accessible-auto-suggest/FreedomScientific(2018).JAWSUIAScriptAPIDocumentationAccessibility.Retrievedfromhttps://www.freedomscientific.com/support/jawsdocumentation/UIAScriptAPIJacobS.(2013).5WaystoMakeYourE-CommerceWebsiteSearchFeatureConvert.Retrievedfromhttps://blog.kissmetrics.com/ecommerce-website-search/

LibraryofCongress.(2018).Searchhelp.Retrievedfromhttps://www.loc.gov/search/help/

W3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableW3C.(2017).WAI-ARIAAuthoringPractices1.1.Retrievedfromhttps://www.w3.org/TR/wai-aria-practices/Seealso:Help-seekingSituations>DifficultyAccessingInformationHelp-seekingSituations>Difficultylocatingspecificinformation,itemsorfeaturesHelp-seekingSituations>Difficultyconstructingorrefiningsearches>Difficultytrackingsearches

88

DifficultyIdentifyingCurrentStatus,Path,orCursorMode

DifficultydetectingorlocatingsearchresultsDefinition:Asituationthatarisesfromoneofthefollowingdifficulties:detectingtheoutcomeofasearch,includingwhetherornotthesearchresultsaredisplayed;findingthesearchresults;anddeterminingwhethertheresultsreturnedreflectarecentlymodifiedsearchorarestilltheresultsofapriorsearch

Factor(s):

• Lackofsystemfeedback• Lackofappropriateheadinginformation• LackofcontextualinformationorcuesGuidelineorDesignRecommendation:5. Clearlylabeltheresultssectionforrecognizability6. ProvideashortcuttotheDLsearchresultlist7. Notifytheuserthatthequeryhasbeenprocessedandresultshavebeengenerated8. ProvideguidanceonhowtorecognizewhethersearchresultsweregeneratedorchangedRationaleandObjective:DLshavecomplexnavigationstructures;thereforeBVIusersneedtoexplorethepagetodeterminewhethertheresultshavebeendisplayed.ApplyingashortsoundindicatingsearchresultscanbehelpfulforaBVIusertorecognizethatsearchresultshavebeengeneratedinaDL.Inmanycases,whenBVIusersmodifytheirsearchtermsinthesearchbox,theyareunabletodeterminewhethernewresultshavebeengenerated.ProvidinganaudibleprogressindicatorwouldhelpBVIuserstopredicthowlongtheyshouldwaittogetthesearchresultsand/orwhethersearchresultshavebeendisplayed.Searchinstructionsortipscandescribethis.AdescriptionnearthetopofthepageorsearchboxspecifyingthatsearchresultsweregeneratedisasignificantmarkerforaBVIusertorecognizethatthesearchresultshavebeengeneratedandareaccessible.Applyingaheadingof“searchresults”atthetopoftheresultslistcanfacilitateeaseofnavigation.


89

1.1.Addaheadingtagtosearchresultssectiontitle2.1.Provideskiplinksandsectionheadersasshortcutstothesearchresults3.1.Usetextorsoundalertstoindicatethestatusofthesearchprogress3.2.Addtextand/orsoundalerttoindicatethatsearchresultsweregeneratedorupdated3.3.Displayanotificationnearthesearchboxindicatingthestatusofthesearchresults4.1.Providehelpinrecognizingwhensearchresultsaregenerated4.2.IncludesearchtermsandthenumberofresultsintheSearchResultsheading.AnARIAliveregionmightbeusedtospeakshorttextwithnumberofsearchresultsreturned,forexample:“pageloaded,2results”

RecommendedFeatures:1.1.SearchResultssectionheading2.1A.Sliplinks2.1B.Sectionheaders3.1/3.2.Sound/textindicator3.3.Statusnotification4.1.Tipsandhelp4.2.Searchterm(s)displayedinresultsheading

Examples:3.1./3.2.Soundindicationforawebpageupdate(pseudocode).

<script>functionplaySound(){//codeforplayroutine}</script><bodyonload=”playSound()”><h>Playasoundwheneverthewebpageisupdated</h></body>

3.3.Adescriptionfornoresult–SmithsonianInstitution

90

4.2.Aresultheader

91

RelatedResources:Barbich,N.(2017).AComprehensiveGuidetoWebDesign.Retrievedfromhttps://www.smashingmagazine.com/2017/11/comprehensive-guide-web-design/SmithsonianDigitalLibrary.(2018).Nosearchresultpage.Retrievedfromhttps://library.si.edu/gsearch/dianosauW3C.(2018).WCAG2.13.2.5ChangeonRequest.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/change-on-request.htmlSeeAlso:Help-seekingSituations>Difficultylocatingspecificinformation,itemsorfeaturesHelp-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

92

DifficultyidentifyingacurrentlocationortrackingpathsDefinition:Asituationthatarisesfromdifficultyidentifyingthecurrentlocation,monitoringthepathtowhichausermoved,andreturningtoapreviouslocationwithinaDL.

Factor(s):

• Lackofcontextualinformation• Complexinformationpresentation• Unclearlabelingofstructuralelements• Missingnavigationaids• Broken“back”buttonGuidelineorDesignRecommendation:1. MaintainhierarchicalnavigationstructuresconsistentlyacrossDLpages2. ArticulatethecurrentlocationandpathsthroughaDL3. TitleeachDLpage,eachsectionofthatpage,andlandmarksinameaningfulway4. AllowtheusertoreturntoapreviouslyvisitedlocationsinaDL5. LabelallnavigationelementsinameaningfulwayRationaleandObjective:ToeffectivelynavigateaDL,usersmustbeabletoanswerthequestion“WhereamI?”Knowingthecurrentlocationandotherpossiblenavigationpathsiscriticalininformationretrieval,andfailingtorecognizethecurrentlocationisacommonprobleminDLnavigation.Usersshouldbeinformedabouttheircurrentlocationwithinasetofrelatedpages.Forusersofscreenreaders,anavigationlandmarkisaquickwaytojumptothenavigation.Asitemapshowing1)thelocationofthecurrentpageintheDL;2)thestructureofthewebsite(howthepagesinterconnect;)and3)thepathofthenavigation,maybehelpful.Theuseofbreadcrumbsand/orsitemapsmayimprovenavigabilityandreducethenumberofactionsbyindicatinghigher/lower-levelpagesandtherelationshipbetweenwebpages,aswellasthelocationoftheuserwithintheDL’shierarchy.BreadcrumbscanalsoshowthehistoryofhowauserinteractedwiththeDLwebpage.

TechniquesandMethods:1.1.Useconsistentnavigationaids(navigationmenu,sitemap,tabs)onallpagesofaDL1.2.Designnavigationaids,suchasmenubarsandsitemaps,withahierarchicalstructure2.1.Addlocationindicatorssuchasbreadcrumbsoneachpage2.2.Provideanaccessiblesitemaptaboneverypage,describingthecurrentlocationwithina

93

DLstructure2.3.CreateURLstomatchwithitemtitles3.1./5.1.Providemeaningfullabelsforpagetitles,sectiontitles,andlandmarktitles4.1.UserHTML5historyAPItogeneratealistofvisitedpages

RecommendedFeatures:1.1.Consistentnavigationaids1.2.A.Menubar1.2.B./2.2.Accessiblesitemap2.1.Breadcrumbs2.3.DescriptiveURLs3.1./5.1.Pagetitles,sectiontitlesandlandmarktitles4.1.A.HTML5HistoryAPI(e.g.pushState)4.1.B.Visitedpagelinks

Examples:1.2.NavigationTreeviewExampleUsingComputedProperties–Keyboardsupportfromhttps://www.w3.org/TR/wai-aria-practices/examples/treeview/treeview-2/treeview-2a.html2.1.A.WAI-ARIABreadcrumbExamplefromhttps://www.w3.org/TR/wai-aria-practices/examples/breadcrumb/index.html<navaria-label=”Breadcrumb”class=”breadcrumb”>

2.1.B.BreadcrumbswithHomelinkinthenavigationbar(Europeana,theEUdigitalplatformforculturalheritage,2018)

2.1.C.Searchresultlinkinthebreadcrumb(trail)

94

2.3.ClearURLpathstructure(eg./collection/248/item/31versus/item?sessionid=9871209387498&token=918123…)3.1.A./5.1.A.MoreelaborationsaddedforJAWS’sreading–renamingthelinkforsearchresults,descriptionsaddedfornavigationmarks–“Previous/NextSearchResult”(invisible,butreadablebyJAWS),e.g.<spanclass=”secondary_button_iconicon_arrow_w”>PreviousSearchResult</span>

3.1.B./5.1.B.Clearlabelingfornavigationindicators.

3.1.C/5.1.CClearlabeling:Rename“DigitalCollection”to“MarchonMilwaukeeDigitalCollection”

95

4.1.A.ApplyJavaScriptHTML5HistoryAPIs,suchashistory.pushState(),history.back/forward(),andhistory.go(index),whichcanbeusedtomoveforwardandbackward,movetoaspecificpagevisited.

4.1.B.Avoid‘target=”blank”’forlinksbecausethiscanbreakbrowsernavigation.

RelatedResources:Europeana.(2018).Exhibitions.Retrievedfromhttps://www.europeana.eu/portal/en/exhibitionsFaçanha,A.R.,Viana,W.,Pequeno,M.C.,deBorbaCampos,M.,&Sánchez,J.(2014,June).Touchscreenmobilephonesvirtualkeyboardingforpeoplewithvisualdisabilities.InInternationalConferenceonHuman-ComputerInteraction(pp.134-145).Springer,Cham.Gube,J.(2009).BreadcrumbsInWebDesign:ExamplesAndBestPractices.Retrievedfromhttps://www.smashingmagazine.com/2009/03/breadcrumbs-in-web-design-examples-and-best-practices/Holst,C.(2014).4DesignPatternsThatViolateBack-Button,Expectations.Retrievedfromhttps://baymard.com/blog/back-button-expectationsMarkus,N.,Malik,S.,Juhasz,Z.,&Arató,A.(2012,July).Accessibilityfortheblindonanopen-sourcemobileplatform.InInternationalConferenceonComputersforHandicappedPersons(pp.599-606).Springer,Berlin,Heidelberg.MotoCMS.(2014).BreadcrumbNavigationExplained:Types,Benefits,Guidelines.Retrievedfromhttps://www.motocms.com/blog/en/breadcrumb-navigation/OpenLibrary.(2018).Retrievedfromhttps://openlibrary.org/

96

Sutton,J.(2002).AGuidetoMakingDocumentsAccessibletoPeoplewhoareBlindorVisuallyImpaired.AmericanCounciloftheBlind,Washington,DC

Theng,Y.L.,Duncker,E.,Mohd-Nasir,N.,Buchanan,G.,&Thimbleby,H.(1999,September).Designguidelinesanduser-centreddigitallibraries.InInternationalConferenceonTheoryandPracticeofDigitalLibraries(pp.167-183).Springer,Berlin,Heidelberg.

W3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline2.4.8Location.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/location.htmlW3C.(2018).WCAG2.1Guideline2.4.2PageTitled.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/page-titled.htmlW3C.(2018).WCAG2.13.2.3ConsistentNavigation.Retrievedfromhttps://www.w3.org/TR/WCAG21/#consistent-navigationW3C.(2018).WCAG2.12.1.1Keyboard.Retrievedfromhttps://www.w3.org/TR/WCAG21/#keyboardW3C.(2018).WCAG2.12.4.3FocusOrder.Retrievedfromhttps://www.w3.org/TR/WCAG21/#focus-orderW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#consistent-navigationXie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.SeeAlso:Help-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

97

DifficultyidentifyingitemsthatrequiredownloadingbeforeviewingDefinition:AsituationthatarisesfromthedifficultyindistinguishingbetweenanitemthatmaybeaccesseddirectlyinaDLversusanitemthatisonlyaccessibleafterdownloading.

Factor(s):

• Lackofcontextualinformation• UnclearlabelingGuidelineorDesignRecommendation:1. Indicatewhichitemsthatmustbefirstdownloadedinordertobeviewed2. ProvideguidanceonhowtoviewitemsdirectlyfromaDLaswellasviewingthose

requiringdownload3. FacilitatedisplayofitemsthatrequiredownloadingRationaleandObjective:SomeDLitemscanbeimmediatelyaccessedinthebrowserwithoutdownloading,whileothersneedtobedownloadedinordertoaccessthem.Cleartextualdescriptionsareneededtodistinguishwhichitemscanbeaccesseddirectly.Asmuchaspossible,itemsshouldbeprovidedinawaythatisimmediatelyavailable,sinceitemsthatrequiredownloadingmostoftenalsorequireadditionalsoftwaretoaccess.Moreover,thetimerequiredtodownloaditemscanbesignificant,especiallyifafastinternetconnectionisnotavailable.

TechniquesandMethods:1.1.Addacleartextindicatorifanitemneedstobedownloadedinordertoviewit2.1.Providethefileformatdesignationforeachitemaspartofthemetadata2.2.Providehelptipsandinstructionregardinghowtoview/downloaditemsindifferentformats2.3.Provideinformationonwhatsoftwareisneededtoviewitemsthatfirstrequiredownloading,includinglinkstothatsoftware,whenavailable3.1.Providefilteroptionstodisplayonlyitemsthatrequiredownloadingbeforeviewingoronlyitemsthataredirectlyviewable

RecommendedFeatures:1.1.Textindicators2.1.Metadata—fileformat2.2.Helptipsandinstructions

98

2.3.Softwareneeded3.1.FilteroptionsExamples:3.1.Afilteroptionforonlineitems:DPLA–SmithsonianInstitution

RelatedResources:SmithsonianDigitalLibrary.(2018).SmithsonianLibraries.Retrievedfromhttps://library.si.edu/W3C.(2018).WCAG2.1Guideline1.1:Text-alternatives.Retrievedfromhttps://www.w3.org/TR/WCAG21/#text-alternativesW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableW3C.(2019).WAI_ARIAAuthoringPractices1.1.Retrievedfromhttps://www.w3.org/TR/wai-aria-practices-1.1/

99

SeeAlso:Help-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

DifficultynavigatingthroughaDLpageDefinition:AsituationthatarisesfromdifficultynavigatingthroughaDL.

Factor(s):

• Lackoftheconsistentpagestructure• ComplexInformationPresentationGuidelineorDesignRecommendation:1. EnsureDLpageshaveaconsistentstructureandlayout2. EnablequickandeasywaystonavigatefromonepointtoanotherwithinaDL3. Labelnavigationalaidsinameaningfulway4. ProvidehelpregardinghowtonavigatethroughaDLRationaleandObjective:BVIusersdependonthetextandstructuralinformationtounderstandandnavigateaDLpagestructure.Itmaybehelpfultousemeaningfultags—calledsemanticmarkup—suchas<blockquote>,<p>,<em>,or<h>ratherthanpresentation-basedHTMLsuchaswouldbeusedforsightedusers.Also,DLwebpagesarecomposedofseveralregions.Eachregionshouldfunctionaccordingtoaspecificpurpose,andthepagestructureshouldbedesignedwithalogicalflow.HTML5andARIAlandmarksforaregioncanbeusedforeaseofnavigationbyascreenreader.Thepagestructureshouldbedesignedwithalogicalflow.Themainnavigationmenushouldbeconsistentlylocatedinthetopareaofthepage.Eachmenucategoryshouldincludespecificsections.Somenavigationsaids,suchasbreadcrumbs,mayhelpBVIusersnavigatethesite.LinksshouldbenamedinameaningfulwayusinglabelsratherthanURLs.Addinginternallinkstoimportantfeatures,suchassearchresultsandmetadataforaparticularitem,maybehelpfulwhenthosefeaturesarefarfromthetoparea.Importantitemsandsectionsshouldbeatthestartand/ortheendofthewebpage,whicharemorerecognizableforBVIusers.AddingHTMLelements,suchasskip-to-linksthatdirecttheassistivetechnologytoskipoverdesignelementsorinformationnotpertinenttothepageorthesearch,mightbeusefulforBVIusers.


100

1.1.IncorporateconsistenttopmenuacrossaDL,consistingofnomorethan10itemsandgroupingitemsiftherearemorethan101.2.PositionimportantitemsatthebeginningofaDLpage1.3.Useasinglecolumntextlayout2.1.Providebreadcrumbsfornavigation2.2.Provideinternallinks,headingsandlandmarksforquicknavigation2.3.Provideasitemapwithhyperlinkstoeachpage2.4.UsesemanticHTMLtofacilitatenavigation3.1.Providealabeloranalttextforeachnavigationaidtospecifyitsfunction3.2.UseARIA-labelstoprovideuniquenamesforscreenreaders,avoidingtheuseorARIA-hiddenattributesonanelement,whichmakeselementsinaccessibletoscreenreadersandotherassistivetechnologies3.3.Providemeaningfultitlesassectionheaderswithheadingtagstosupportnavigation4.1.ProvidenavigationtipsandinstructionregardinghowtousenavigationaidswithinandacrossDLpages

RecommendedFeatures:1.1.Navigationbar/menu1.3.Singlecolumntextlayout2.1.Breadcrumbs2.2.A.Internallinks/SkiptoContentlinks2.2.B.Headings2.2.C.Landmarks2.3.Sitemapwithhyperlinks2.4.NamedAnchors3.1./3.3.Meaningfullabels3.2.HTML5andARIAlandmarkswithnames(e.g.<section>,role=”region”(ARIArole),(e.g<section>andARIARolerole=”region”)4.1.Navigationtipsandinstruction

Examples:2.1.A.Breadcrumb:<navaria-label=”Breadcrumb”class=”breadcrumb”><li><ahref=”./index.html”aria-current=”page”>BreadcrumbExample</a></li>

Formore:https://www.w3.org/TR/wai-aria-practices/2.1.B.Breadcrumbincludingresultspath(Europeana,2018)

101

2.2.Invisiblelinksadded:“Skiptoeventdetails”and“Returntothumbnail”foranitem

2.3.SitemapforBVIusers(TheLibraryofCongress,2018)

102

3.2.HTML5elementsandcorrespondingARIAroles

<header>–role=”banner”,<nav>-role=”navigation”,<main>–role=”main”,<section>,<footer>–role=”contentinfo”,role=”search”,<aside>–role=”complementary”,<article>,<form>–role=”form.e.g.<headerrole=”banner”><p>logo,etc.here</p></header><navrole=”navigation”><ul><li>navigation</li></ul></nav><mainrole=”main”><p>maincontentarea</p></main><footerrole=”contentinfo”><p>copyright,etc.here.</p></footer>

RELATEDRESOURCES

103

Bohman,P.(2013).HTML5andARIALandmarks.Retrievedfromhttps://dequeuniversity.com/assets/html/jquery-summit/html5/slides/landmarks.htmlBorysowich,C.(2007).DesigningWebsiteNavigationalaids.Retrievedfromhttps://it.toolbox.com/blogs/craigborysowich/designing-website-navigational-aids-123107

Buzzi,M.C.,Buzzi,M.,Leporini,B.,&Paratore,M.T.(2013,September).Vibro-tactileenrichmentimprovesblinduserinteractionwithmobiletouchscreens.InIFIPConferenceonHuman-ComputerInteraction(pp.641-648).Springer,Berlin,Heidelberg.

Crestodina,A.(2017).WebsiteNavigation:7BestPractices,DesignTipsandWarnings.Retrievedfromhttps://www.orbitmedia.com/blog/website-navigation/DequeUniversity.Adda“SkipNavigation”LinktoHelpKeyboardUsersReachMainContentFaster.Retrievedfromhttps://dequeuniversity.com/tips/add-skip-navigation-link.Europeana.(2018).Breadcrumbincludingresultspath.Retrievedfromhttps://www.europeana.eu/portal/en/record/2064109/Museu_ProvidedCHO_Spielzeugmuseum_der_Stadt_N_rnberg__Museum_Lydia_Bayer__67267__Datensatz_.html?q=rabbit

Hennig,S.,Zobl,F.,&Wasserburger,W.W.(2017).AccessibleWebMapsforVisuallyImpairedUsers:RecommendationsandExampleSolutions.CartographicPerspectives.

HTML5Accessibility.HTML5andARIALandmark.Retrievedfromhttps://dequeuniversity.com/assets/html/jquery-summit/html5/slides/landmarks.html.Lynch,P.J.&Horton,S.(2017).Webstyleguide3rdedition.Retrievedfromhttp://webstyleguide.com/wsg3/6-page-structure/3-site-design.htmlNielsen,J.andLi,A.(2017).MegaMenusWorkWellforSiteNavigation.Retrievedfromhttps://www.nngroup.com/articles/mega-menus-work-well/

Park,K.,Goh,T.,&So,H.J.(2014,December).Towardaccessiblemobileapplicationdesign:developingmobileapplicationaccessibilityguidelinesforpeoplewithvisualimpairment.InProceedingsofHCIKorea(pp.31-38).HanbitMedia,Inc..

SurfingtheInternetwithJAWSandMAGic!.(2011).NavigatingWebPages.Retrievedfromhttp://doccenter.freedomscientific.com/doccenter/doccenter/rs25c51746a0cc/2011-04-05_surfsuplessonone/04_navigating.htm

104

TheLibraryofCongress–Sitemap.(2018).Retrievedfromhttps://www.loc.gov/nls/site-map/Wangetal.(2017).EnablingIndependentNavigationforVisuallyImpairedPeoplethroughaWearableVision-BasedFeedbackSystem.IEEEInternationalConferenceonRoboticsandAutomation.Retrievedfromhttps://groups.csail.mit.edu/drl/wiki/images/f/fb/Wearnavi-vision-icra2017.pdf.Webpagefx.(2013).DesigningthePerfectHyperlink—It’sNotasSimpleasYouThink.Retrievedfromhttps://www.webpagefx.com/blog/web-design/hyperlink-design/WebPageMistakes.(2018).WebsiteNavigation.Retrievedfromhttp://www.webpagemistakes.ca/website-navigation/W3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2016).ARIALandmarksExample.Retrievedfromhttps://www.w3.org/TR/wai-aria-practices/examples/landmarks/region.htmlW3C.(2018).Providingasitemap.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Techniques/general/G63.W3C.SupportedStatesandProperties.Retrievedfromhttps://www.w3.org/TR/wai-aria-1.0/states_and_properties#aria-hiddenSeeAlso:Help-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

DifficultyrecognizingcurrentstatusofaDLDefinition:AsituationthatarisesfromthedifficultydetectingifaDLpageisintheprocessofloading,orhasloaded,orwhetherapagehasrefreshed.

Factor(s):

• Lackoffeedback• Lackofcontextualinformation

105

GuidelineorDesignRecommendation:1. Ensurethatpageloadingstatusorpageupdatestatusisrecognizable2. Reducepageloadingtime3. ExplainhowtodetectachangeorupdateinthestatusofaDLRationaleandObjective:BecauseDLscontainavarietyofheterogeneouscontentandanarrayoffileformatswithindigitalcollections,DLsareatriskofpresentingcontentthatmayextendpage-loadingtime.Applyingashortsoundtoindicatepage-loadingstatusallowsBVIuserstoknowifthewebpageiscompletelyloadedonareal-timebasisandalleviatestheneedfortheusertorepeatedlycheckthestatusbar.Avoidingcomplexelementsandlarge-sizeobjectsinthewebpagecanbehelpfulfordecreasingtheloadingtime.Audibleprogressindicatorsmaybehelpfulwhenusersneedtowaituntilthepageloadiscomplete.Alternatively,usingaskeletonscreen,whichincludesdisplaying“mockups”ofcontentelementsthatutilizeminimaltextualmessagesratherthanimages,allowsuserstoaccessinformationmorequicklyastheitemsaredisplayed,eventhoughsomecontentsarenotyetcompletelyloaded.

TechniquesandMethods:1.1.Provideclear,unique,andmeaningfulpagetitleinitstitleelementsoitisdiscerniblethattheuserhasactivatedanewpage1.2.AddanalertroletothetitleelementofeachDLpage1.3.Providesoundortextindicatorstoalerttheusersthepageloadingstatus(inprogress,completed,andreadyforinteraction),possiblyanarrayofsounds,includingdifferentpitchesrelatedtothedifferentpercentages1.4.Addasound,preferablyincludingtextreadaloud,indicatingloadedwebpagecompletion1.5.AlertusersabouttheunavailabilityofaDLduetonetworkorserverconnectionfailuresusingasimpledialoguebox2.1.Minimizelarge-sizeobjects(suchasembeddedvideoandslideshowwidgets)andunoptimizedback-endcode/sublet/appletsthatincreasepageloadingtime2.2.UsetoolssuchasPageSpeedInsightstohelpdeterminethecausesofslowloadingtime(https://developers.google.com/speed/pagespeed/insights/)3.1.Offerhelptipsandinstructionstoenable/disableauto-refreshofDLpagesfromwebbrowsersettingsRecommendedFeatures:1.1.A.UniquePageTitle1.1.B.Titleelement1.2.Alertrole1.3/1.4.A.Sound/textindicator1.3./1.4BARIA-live=”assertive”(seeexamplebelow)1.5.Simpledialoguebox3.1.Helptipsandinstruction

106

Examples:1.3/1.4.TheissuecanbeeliminatedbyusingARIA-live=”assertive”onthepageload/percentageindicator.Notethatthe“assertive”optionisrecommendedtoavoidlongrecitationofpageloadpercentages.ItwouldbehelpfultouseARIAliveregiontospeak“loaded”orsimilarbyreactingtoaneventthatindicatespageisloaded.

https://labs.levelaccess.com/index.php/Progress_Bar_with_ARIA_Live_RegionsRelatedResources:Bock,M.(2017).BuildingSkeletonScreenswithCSSCustomProperties.Retrievedfromhttps://css-tricks.com/building-skeleton-screens-css-custom-properties/Leporini,B.,&Paternò,F.(2004).Increasingusabilitywheninteractingthroughscreenreaders.Universalaccessintheinformationsociety,3(1),57-70.Shakir,S.(2017).StopUsingLoadingSpinner,There’sSomethingBetter.Retrievedfromhttps://blog.iamsuleiman.com/stop-using-loading-spinner-theres-something-better/W3C.(2018).WCAG2.1Guideline1.4.2AudioControl.Retrievedfromhttps://www.w3.org/TR/WCAG21/#audio-controlW3C.(2018).WCAG2.13.2.5ChangeonRequest.Retrievedfromhttps://www.w3.org/WAI/WCAG21/Understanding/change-on-request.html

107

Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),n2.Retrievedfromhttp://informationr.net/ir/20-2/paper673.html#.XnkVkNNKhTYSeeAlso:Help-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

Difficultyrecognizingpre-existingtextinaninputboxDefinition:AsituationthatarisesfromthedifficultyofrecognizingifaninputfieldintheDLisalreadypopulatedwithsomedata(ortext).

Factor(s):

• LackofFeedback• Failuretoclearsearchboxonfocus• Useof“placeholder”textGuidelineorDesignRecommendation:1. Ensurethatpresenceofpre-existingtextinaninputfieldisannouncedbeforetheuser

startsinteractingwiththatfield2. Avoid“placeholder”textinformfields3. Provideinstructionrelatedtopre-existingandplaceholdertextRationaleandObjective:SinceBVIusersarenotabletoviewwhatisintheinputboxbutrelyonauditorycues,theymayexperiencedifficultiesinrecognizingpre-existingtextifnocuesareprovided.Thisisespeciallytruefor“placeholder”text.Manyscreenreadersdonotreadplaceholdertext.Insituationswherethereistextremainingfromtheprevioussearch,BVIusersassumethatthesearchboxisclear.Inaddition,DLfeaturesthatincludeNewSearch/WithinSearchcomponentsassociatedwiththesearchfieldcauseconfusionforBVIuserswhointerpretthefirstasalinktogenerateanew,emptysearchfield,ratherthananassociatedfilteringfeatureaccompanyingapriorkeywordsearch.Someuserswouldnotassumeatextboxisemptyandwouldcheckbeforetypingtext;however,itisthereforedifficultforBVIuserstobenefitfromtextsuggestionsand/orautocompletions.

108

TechniquesandMethods:1.1.Alertuserstothepresenceofpre-existingtextintheinputfieldwhenthefocusisatthestartoftheinputfield,2.1.Providetextsuggestionsassearchtipsoutsidethesearchbox3.1.Providesearchinstructiononhowtocheckwhetherthereispre-existingtextinthesearchbox

RecommendedFeatures:1.1.ARIAlivealerts2.1.Searchtips3.1.Searchinstruction

Examples:1.1.Whenthefocusmovesonthesearchboxwithpre-existingtext,ascreen-readerwillreadthepre-existingtext.

RelatedResources:Damaceno,R.J.P.,Braga,J.C.,&Mena-Chalco,J.P.(2018).Mobiledeviceaccessibilityforthevisuallyimpaired:problemsmappingandrecommendations.UniversalAccessintheInformationSociety,17(2),421-435.Don’tUseThePlaceholderAttribute—SmashingMagazine.Retrievedfromhttps://www.smashingmagazine.com/2018/06/placeholder-attribute/Fulton,G.(2017).AccessibilityBasics:DesigningforVisualImpairment.Retrievedfromhttps://webdesign.tutsplus.com/articles/accessibility-basics-designing-for-visual-impairment–cms-27634Miura,T.,Matsuzaka,H.,Sakajiri,M.,&Ono,T.(2012,October).Usagesanddemandstotouchscreeninterface:AquestionnairesurveyinJapanesevisuallyimpairedpeople.InSystems,Man,andCybernetics(SMC),2012IEEEInternationalConferenceon(pp.2933-2938).IEEE.PlaceholdersinFormFieldsAreHarmful–NielsenNormanGroup.Retrivedfromhttps://www.nngroup.com/articles/form-design-placeholders/Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),n2.

SEEALSO:

Help-seekingSituations>Difficultyidentifyingcurrentstatus,path,orcursormode

109

ConfusionAboutMultiplePrograms,DLStructures,orSearchResultsStructure

ConfusionaboutdigitallibrarystructureandbrowsecategoriesDefinition:Asituationthatarisesfromauser’sdisorientationwithintheoverallstructure,layout,orbrowsecategorieswithinaDL.

Factor(s):

• Systemknowledge• Unclearlabeling• Complexinformationpresentation• Lackofcontextualinformation• UnclearinstructionGuidelineorDesignRecommendation:1. MaintainalogicalhierarchicalstructurefortheDL,includingpagelayout,content

organization,andbrowsecategories2. Ensurethatstructuralelementshavemeaningfullabels3. ExplainthestructureoftheDLanditsbrowsecategoriesandhowtointeractwithits

structuralelementsRationaleandObjective:ForBVIusers,acomplicateddigitallibrarystructuremayposeachallengefornavigatingtheDL.TheyareunabletorecognizethestructureoftheDL,therebyfailingtodeterminetheappropriatecourseofaction.Therefore,asimplepredictiveandhierarchicalstructureiseasilyunderstood.BrowsecategoriesareoneofthemainfeaturesforBVIuserstointeractwithaDL,butduetosophisticatedinformationpresentation,browsecategoriesmaybetoocomplicatedforusers,andtheyavoidtakingthisroute.

TechniquesandMethods:1.1.OrganizeaDLfromgeneraltospecificinitsgeneralstructureandbrowsingstructureuptoamaximumofthreenestedlevels1.2.Placethemostfrequentlyusedinformationatthetopofeachlevelofitsstructure1.4.MaintainalogicalhierarchicalheadingstructureacrosstheDL

110

1.5.MaintainaconsistentandsimplifiedpagelayoutacrosstheDL1.6.Provideoptionsforfacet-basedbrowsingbysubjects,creators,etc.2.1.AssignmeaningfulanduniquetitlestoindividualsectionsoftheDL2.2.Assignmeaningfulanduniquelabelswithhyperlinksforeachofthebrowsingcategoriesandsubcategories3.1.Provideinstruction(help),whichexplainstheDLstructureandbrowsecategoriesstructure

RecommendedFeatures:1.1.Generaltospecificstructure1.2.Frequentlyusedinformationatthetoplevel1.3.A.Single-columnlayout,ifpossible1.3.B.Linearstructure1.4.Nestedheadingstructure1.5.Consistentlayout1.6.Facet-basedbrowsing2.1.Sectiontitles2.2.Browsecategorylabelswithhyperlinks3.1.Tutorial/instruction/tips

Examples:1.3.A.Single-columnlayoutcanbeusedindetailpages.Thirdcolumnlayoutcanbeusedin:homepage,landingpages,mainnavigation.Fourth/TreeFourthcolumnlayoutcanbeusedin:filterspage,detailpagewithinpagenavigation.(EuropeanCommission,2018).

1.3.B.Alinearstructureinthepagelayout(EuropeanCommission,2018).

111

2.1.Subtitle

113

2.2.A.ConsistencyinlabelinghelpsusersunderstandthestructureofaDL

114

2.2.B.Sectionnames

2.2.C.LinkandDateadded.

115

3.1.A.Briefinstructionaddedtoexplainthebrowsestructureandapplysectionheaderlabelssothattheinstructioncanalsobeskippedbyscreenreader.

3.1.B.DescriptionaddedforTimeline/Keyterms

116

RelatedResources:Croxford,S.,&Rundle,C.(2013).BlindPeopleandAppsonMobilePhonesandTablets–ChallengesandPossibilities.InContemporaryErgonomicsandHumanFactors2013(Vol.343,No.346,pp.343-346).ROUTLEDGEinassociationwithGSEResearch.EuropeanCommission.(2018).Gridandpagelayout.Retrievedfromhttps://ec.europa.eu/info/resources-partners/guidelines-websites-under-eceuropaeu/grid-and-page-layout_en#gridJasek,C.(2004).Howtodesignlibrarywebsitestomaximizeusability.Elsevier:SanDiego.

Lynch,P.&Horton,S.SiteStructure.Retrievedfromhttp://webstyleguide.com/wsg3/3-information-architecture/3-site-structure.htmlW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#consistent-navigationW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictable

117

Whitenton,K.(2013).Flatvs.DeepWebsiteHierarchies.https://www.nngroup.com/articles/flat-vs-deep-hierarchy/Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.Seealso:Help-seekingSituations>Confusionaboutmultipleprograms,DLstructures,orsearchresultsstructure

DifficultyunderstandingresultsstructureorlayoutDefinition:AsituationthatarisesfromthedifficultyunderstandingtheoverallstructureorlayoutofthesearchresultsdisplayedbytheDL.

Factor(s):

• LackofDLsystemknowledge• Complexinformationpresentation• Unclearlabeling(tabsnotproperlylabeled)• LackofcontextualinformationGuidelineorDesignRecommendation:1. Maintainasimpleandconsistentlogicalstructureandlayoutforpresentingsearchresults

intheDL2. Ensurethatstructuralelementsofsearchresultshavemeaningfullabels3. Explainthestructureandlayoutofsearchresultspresented,aswellashowtointeractwith

thestructuralelements4. EnableuserstocontroltheirsearchresultslayoutsRationaleandObjective:

118

Displayingsearchresultsinawaythatisclear,well-labeled,andconsistentiskeytohelpingusersunderstandandnavigatethem.ResultsstructureandlayoutmaybecomplicatediftheDLwebpagesincludeavarietytypeofstructures,suchas1)avisualgallery,2)mappedresultsonamap,3)displayingrelatedorsimilarly-nameditems,4)clusteringresults,5)displayingmixedtypesofresults,etc.Theresultsstructureshouldbesimplified,includingminimalelementsandunderstandablemetadata.Theresultssectionshouldbeproperlylabeledtodesignatethesearchresultsregion.Eachresulttitleshouldbeformattedwiththeheadertag(<h#>)toallowBVIuserstoquicklynavigatethroughtheresultslistbytitles.AsummaryofresultsmightbehelpfulforBVIuserstorecognizetheresults,suchasthenumberofresults,resultslayout,and/ortipsforhowtoreorganizetheresults.Clearinstructionshouldbeprovidedtoinformonhowtouseandmodifytheresultslayout.

TechniquesandMethods:1.1.Formatresultsinatable/listformat1.2.Displayeachresultiteminaconciseformatforrapidscanning1.3.Provideanoptionforresultlayoutdisplay1.4.DesignvisuallayoutsthatcanbeconvertedintothetextuallayoutforBVIusers(e.g.webpagesincludingvisualcontentsthatcanbeconvertedintowebpagesincludingonlytext)2.1.Provideclearsearchresultssectionheader2.2.Labelresultstitlesusingheaders3.1.Provideinstructionsregardingtheresultstructure/layout4.1.Allowuserstoswitchresultslayoutsthroughdetailed/simplelayouts,orfacets(e.g.,contenttype,date/era,region,genre,etc.).

RecommendedFeatures:1.1.Simpleresultsstructure1.3.Resultlayoutoptions(list/grid)1.4.Textonlyversion.2.1./2.2.Resulttitlewithheadingtags.<h2>SearchResult#itemsfound</h2>3.1.Context-sensitiveinstructions/tips

Examples:1.4.Textualdescription–textview(Hathitrust,2018)

119

RelatedResources:Hathitrust(2018).Retrievedfromhttps://babel.hathitrust.org/cgi/pt?id=mdp.39015073480538;view=1up;seq=1Russell-Rose,T.(2013).DesigningSearch:ResultsPages.Retrievedfromhttps://uxmag.com/articles/designing-search-results-pagesW3C.(2018).WCAG2.1Guideline2.4Navigable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#navigableW3C.(2018).WCAG2.1Guideline3.2Readable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#readableW3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableSeealso:Help-seekingSituations>Confusionaboutmultipleprograms,DLstructures,orsearchresultsstrcuture

120

Avoidancetendency

Avoidanceofformat,approach,orfeaturesDefinition:Asituationthatarisesfromavoidanceofaspecificfileformat(image),acertainapproachtoretrieveinformation(e.g.,browsingacollection),oraspecificDLfeature(e.g.,advanced/dynamic/embeddedfeature)

Factor(s):

• Unclearlabeling• Lackofalttext• Previousexperience• Lackofretrievalknowledge• LackofsystemknowledgeGuidelineorDesignRecommendation:1. Offerassistanceinusingvisualitems,browsingcollections,andinteractingwith

advanced/dynamic/embeddedfeatures2. Provideexplanationsonusingvisualitems,browsingcollections,andinteractingwith

advanced/dynamic/embeddedfeaturesusingkeyboardcommandsRationaleandObjective:Imageitems,browsingapproach,advancedsearch,anddynamic/embeddedfeaturesarevisuallyorientedbyDLdesign;soBVIusersfindthesefeaturesdifficultandcomplextouse.Althoughadvancedsearchfeaturesarerelativelypopularamongsightedusers,thosefeaturescouldbeharderforblindDLuserstouseiftheydonothaveanycontextaboutthemortheyfindthosefeaturestobeoverlycomplex.InstructionscouldhelpblindDLusersunderstandhowtomanipulateandactivatethesefeatureswithoutsight.Purposeandoperationofbrowsecategories,advancedsearchfeatures,anddynamic/embeddedDLfunctionsmaynotbeobviouswithoutsight,therebypromptingBVIuserstoavoidthem.Usingmeaningfullabelsforsuchfeaturescouldaidtheirdetectionbylisteningandclearlyconveytheirpurpose/function,therebyhelpingtheusers.

TechniquesandMethods:1.1.Provideaninvisiblelinkindicatingtheavailabilityofatranscript,description,orsummaryforeachofthevisualitemsandhowtoaccessit

121

1.2.Provideanoverviewofhowthebrowsecategoriesareclassifiedatthebeginningthebrowsesection1.3.Provideclearlabelstospecifybrowsecategoriesandsearch/dynamic/embeddedfeatures1.4.Providetipsonwhattheadvanced(utilityofthecomponents)/dynamic(thechangeoffeatures)/embeddedfeature(availabilityofthefeature)onkeyboardfocusisandhowtouseit2.1.Provideclearinformation,usertutorials,anddemonstrationsonhowtousevisualitems,locateandunderstandbrowsecategories,andadvanced/dynamic/embeddedfeaturesusingkeyboardcommands

RecommendedFeatures:1.1.Invisiblelinks1.2.Overviewofthebrowsecategories1.3.Clearlabels1.4.Helptips2.1.Tutorialsanddemonstrations

Examples1.3.Searchboxnaming:SimpleSearch,&placeholdertext:SearchMarchonMilwaukee.

2.1.A.Advancedsearchtutorials(Hathitrust,2018)

122

2.1.B.Instructionforchoosingauto-completionornotinChrome.

2.1.C.Supplementsearchjargon(e.g.Boolean/Proximitysearch)withsimplifieddefinitions

https://lucene.apache.org/core/2_9_4/queryparsersyntax.htmlhttps://support.google.com/websearch/answer/2466433?hl=en

123

Relatedresources:Hathitrust.(2018).Advancedsearchtutorials.Retrievedfromhttps://www.hathitrust.org/help_digital_library#SearchTipsSeealso:Help-seekingSituations>DifficultyaccessinginformationHelp-seekingSituations>ConfusionaboutmultipleprogramsandDLstructuresHelp-seekingSituations>Difficultywithhelp

124

DifficultyConstructingorRefiningSearches

DifficultyconstructingsearchqueriesDefinition:Asituationthatarisesfromadifficultyformulatingasearchstatement.

Factor(s):

• UnclearInstruction• LackofFeedback• LackofSystemKnowledge• LackofDomainKnowledge• LackofRetrievalKnowledgeGuidelineorDesignRecommendation:1. Explainhowtoconstructasearchstatementandselectsearchtermsforeffectively

formulatingaDLsearch2. Offerassistanceduringtheprocessofformulatingasearchstatement3. IndicateerrorsastheyoccurwhenenteringsearchstatementsRationaleandObjective:UserssometimeshavedifficultyconstructingsearchqueriesinDLsandmayapplysimplekeywordsoralengthyquery,astheyarenotcertainastothelevelofspecificitythatismosteffectivewhensearchingaDL.Auto-completionandsuggestionsarehelpfultoidentifymorerelatedorrelevantterminology.Spellingerrorsareanothertypeofmistakeinconstructionofsearchquerieswhichcanbecorrectedbyauto-completionand/orrelatedtextsuggestions.Thepresenceofauto-suggestionsshouldberecognizablebyBVIusers,andtheusershouldbeabletoselectthesuggestedtermsusingthekeyboard.ARIAcode,suchas“aria-live”canbeusedtoinformBVIusersabout“liststatus”changesasBVIuserstypeintheinputfield.InmanyDLs,thesearchengineworksbasedonaBooleansearchalgorithmwheresearchtermsshouldadheretoacontrolledvocabulary;therefore,usersmaynotknowwhichtermsareacceptable.Showingpopulartermsand/orcontrolledvocabularytermsoccurringinthedigitalcollectionmaybehelpfulinreducinginstancesofthisproblem.

TechniquesandMethods:1.1Providegeneralhelpinformationingeneralhelppage1.2/2.1.Providecontext-sensitivehelptips(e.g.searchtips,autosuggestiontips)forsearch

125

statementconstruction2.2.Implementauto-suggestionsforrelatedtermsderivedfromacontrolledvocabularyinthesearchbox.Thereareseveralopensourcealgorithmsthatcanbeapplied.Theperformanceofthealgorithmforauto-suggestionsiscritical.2.3.Implementinvisiblesearchsuggestions2.4.UseARIAmarkupontheinputfieldtoenabletheselectionofsuggestedterms3.1.Presentspellingsuggestionsbasedonadictionarywhenspellingerrorsaredetected3.2.Implementappropriatealgorithmstoshowspellingsuggestionsdirectlyinthesearchinputfield3.3.Providetextandsoundalertstoindicatethepresenceoferrorsandsuggestedtermsinthesearchbox

RecommendedFeatures:1.1.Generalhelp1.2/2.1Contextsensitivehelp2.2.A.Auto-suggestionforrelatedterms2.2.B.Searchboxwithrelatedterms2.3.Invisiblesearchsuggestions2.4.ARIAelements(e.g.aria-live,aria-activedescendantattribute,role,aria-autocomplete,aria-owns,aria-label,aria-describedby,aria-selected)3.1.AAuto-suggestionforspelling(e.g.Didyoumean…?)3.1.BSearchboxspellingsuggestions3.3.Textandsoundalerts

Examples:2.2./2.3./2.4.aria-autocomplete=”both”

Autocompletion:<inputaria-describedby=”instruction”><divid=“instruction”aria-live=”assertive”style=”display:none;”>….describetheinstructionforautocompletesuchasuseupanddownkeytoreviewsuggestions</div><lirole=”option”aria-selected=”false”>apple</li>role=“listbox“role=”combobox”aria-activedescendant=”suggestion1”aria-live=”assertive”

126

RelatedResources:Cifcioglu,A.(2017).AnatomyofanAccessibleAutoSuggest.Retrievedfromhttps://uxmastery.com/anatomy-of-an-accessible-auto-suggest/WCAG2.0Guideline3.3Inputassistance.Retrievedfromhttps://www.w3.org/TR/WCAG20/#minimize-error

Xie,I.&Cool,C.(2009).Understandinghelpseekingwithinthecontextofsearchingdigitallibraries.JournaloftheAmericanSocietyforInformationScienceandTechnology,60(3),477-494.

Seealso:Help-seekingSituations>Difficultyconstructingorrefiningsearches

127

DifficultyrefiningsearchqueriesDefinition:Asituationthatarisesfromadifficultymodifyingasearchstatementfromthepriorsearch,particularlynarrowingorbroadeningasearchstatement.

Factor(s):

• LackofFeedback• LackofDomainknowledge

GuidelineorDesignRecommendation:1. Explainhowtorefinethemostrecentsearchstatement,specificallynarrowingor

broadeningasearchstatement2. Offerassistanceinrefiningasearch,particularlynarrowingorbroadeningasearch

statement3. RationaleandObjective:BecausesearchtermsassociatedwithcontrolledvocabularymightgeneratemorerelevantresultsinaDLsearch,searchqueriesmayrequirereformulationusingcontrolledvocabularytermsratherthancommonsearchterms.Auto-suggestionsareahelpfulwayforuserstoidentifycontrolledvocabularytermsandconstructmoreeffectivesearchqueries.Thepresenceofauto-suggestionsshouldberecognizedbyBVIusersandactivatedthroughtheuseofakeyboard.Incaseof“noresults,”auto-suggestionsmightprovideadditionalrelatedorrelevanttermstosupportusers.Narrowingdownthesearchresultsisastepthatfollowsthedisplayofsearchresults,wheretheuserattemptstoreducethenumberofavailableitems.TherearemanyapproachesfornarrowingdownresultswhichshouldbeprovidedbytheDL.Usertagsmightbemorefamiliartosomeusers;suchtagscanbeusedtodisplayrelatedresultsandsupportanarrowing-downofthesearchresults.Broadeningistheoppositeprocessofnarrowingresults.Broadeningisalesscommonactivitythannarrowing,duetothealreadyoverwhelmingquantityofresultsthattypicallyappearinDLsearchresultslists.OneimportantconsiderationaDLshouldaccountforisahierarchicalcategorydesign.Subjectmappingbasedonhierarchicalrelationshipsmightbehelpfultobroadensearchscopes.Usertagsmayalsobeusedtodisplayrelatedresultsandthusbroadenthesearch.Suggestingrelatedsearchqueriesmighthelptheusertoobtainalargerquantityofsearchresults.

TechniquesandMethods:1.1.Providegeneralhelpinformationaboutqueryreformulationonageneralhelppage1.1/2.1.Providecontext-sensitivehelptips(e.g.searchtips)forsearchstatementreformulation2.2.Incorporatecontrolledvocabulariesandusertagsintheauto-suggestionsprovided2.3.Displaylistsofcontrolledvocabularytermsandotherrelatedtermsusedforindexing

128

objectsintheDL2.4.Provideasubjectmapshowinghierarchicalrelationshipbetweensubjects/categories2.5.Providebreadcrumbstoallowbroadeningthesearchresults2.6.Providerelatedsearchfeatures(e.g.finddocumentslikethisone)2.7.Provideintuitiveandaccessiblesortingfeaturestonarrowdownsearchresultsbyvarioustypesoffacetsoruserselectedterms2.8.Provideoptionstonarrowsearchresultsbyvarioustypesoffacets,aspects,orfeaturesusedtoclassifyinformation,e.g.subject,date,location,coverage,etc.2.9.Provide“withinsearch”featurestonarrowdowntheresults

RecommendedFeatures:1.1.Generalhelp1.1/2.1.Context-sensitivehelptips2.2.Usertags2.2/2.3.Controlledvocabularies2.3Relatedterms2.4Subjectmapdescription2.5.Breadcrumbs2.6.Relatedsearchfeature2.7.Sortingfeatures2.8Facet-basedsearch2.9.Searchwithinfeature

Examples2.2.aria-autocomplete=”both”role=“listbox“role=”combobox”aria-activedescendant=”suggestion1”aria-live=”assertive”Interactioninthesearchbox:Addtextshowingwhetherthereispre-existingtextornot.

129

RelatedResources:Babich,N.(2017).BestPracticesforSearchResults,https://uxplanet.org/best-practices-for-search-results-1bbed9d7a311Cifcioglu,A.(2017).AnatomyofanAccessibleAutoSuggest.https://uxmastery.com/anatomy-of-an-accessible-auto-suggest/Hu,R.,Lu,K.&Joo,S.(2013).Effectsoftopicfamiliarityandsearchskillsonqueryreformulationbehavior.ProceedingsoftheAnnualMeetingoftheAmericanSocietyforInformationScienceandTechnology,50,1-9.

WCAG2.0Guideline3.3Inputassistance.(2008).Retrievedfromhttps://www.w3.org/TR/WCAG20/#minimize-errorXie,I.&Cool,C.(2009).Understandinghelpseekingwithinthecontextofsearchingdigitallibraries.JournaloftheAmericanSocietyforInformationScienceandTechnology,60(3),477-494.

Seealso:Help-seekingSituations>Difficultyconstructingorrefiningsearch

130

DifficultytrackingsearchesDefinition:AsituationthatarisesfromdifficultymonitoringtheprogressionofsearchtermsusedinaseriesofpastsearchesinaDL.

Factor(s):

• InadequatefeaturesforuserstotrackpastsearchactivitiesGuidelineorDesignRecommendation:1. Makesearchtermsfrompreviousqueriesavailableonrequestforreuseandcombination2. Enablerefiningofthemostrecentquery3. ExplainhowtomonitortheprogressionsofpreviouslyusedsearchtermsRationaleandObjective:Foruserswhotendtousethesamesearchtermsmorethanonce,retainingthesearchhistorycansavetimeonsubsequentsearches.Listsofpastauto-suggestionsandkeywordhistoryhelpuserstofindarelevanttermorphrasebytryingtopredictit.Displaytherecentlyvisitedlinks/URLscanbeusefulformonitoringsearches,too.

TechniquesandMethods:1.1.Savesearchtermsusedinasession1.2.Providesearchhistoryfeaturestoallowuserstodisplaytheirpreviousqueriesuponrequest2.1.Keepthemostrecentqueryinthesearchbox2.2.Adda“clearsearch”featurenexttothesearchbox3.1.Providehelptipsandexplanationforhowtomonitortheprogressionofsearchterms

RecommendedFeatures:1.1.Searchtermssavingfeature1.2.Searchhistoryfeaturethatretainssearchtermsforasinglesession2.1.Pre-populatedsearchbox2.2.Clearsearchfeature3.1.Helptipsandinstruction

Examples:1.1.Previoussearchtermsinthesearchbox(Europeana,2018)

131

1.2.Searchhistory(SmithsonianInstitution,2018)

RelatedResources:Europeana.(2018).Search.Retrievedfromhttps://www.europeana.eu/portal/en/search?q=rabbit&qf%5B%5D=englandNeilson,J.(2004).GuidelinesforVisualizingLinks.Retrievedfromhttps://www.nngroup.com/articles/guidelines-for-visualizing-links/SmithsonianInstitution.(2018).Searchhistory.Retrievedfromhttp://collections.si.edu/search/history.htmW3C.(2018).WCAG2.1Guideline1.3Adaptable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#adaptable

132

W3C.(2018).WCAG2.1Guideline3.2Predictable.Retrievedfromhttps://www.w3.org/TR/WCAG21/#predictableW3C.(2018).WCAG2.1Guideline3.3Inputassistance.Retrievedfromhttps://www.w3.org/TR/WCAG21/#input-assistanceSeeAlso:Help-seekingSituations>Difficultyconstructingorrefiningsearches

133

DifficultywithCompatibilityIssues

SituationsrelatedtocompatibilityissuesDefinition:Asituationthatarisesfromthedifficultyaccessing/navigating/locatingDLcontentsandcomponentsacrossdiverseDLplatforms,screen-readersoftware,Webbrowserapplications,andoperatingsystems.

Factor(s):

• Lackofsystemfeedback• Inadequatesystemknowledge• Inadequateassistivetechnologyknowledge• UnclearinstructionGuidelineorDesignRecommendation:1. EnsureDLmaintainsaccessibility,navigability,andsearchabilityacrossdiverseDL

platforms,screen-readersoftware,Webbrowserapplications,andoperatingsystems2. EnsurethatDLaccessibilityacrossdiverseplatformsisalsomaintainedovertimedespite

platformupdatesandmodifications3. Informusersaboutthecompatibilityofbrowsers,helperapplications,andscreen-readers

toaccessaDL4. IndicatewhenauserfocusmovesinoroutofaDLRationaleandObjective:ComplicatedDLstructureandincompatibilitybetweenwebbrowsers,applications,andscreenreadersareabarriertoaccessinginformationintheDLwebpages.Inaddition,BVIusersmaybecomeconfusedbyfeatures,suchasdialogueboxes,andbeunabletodistinguishtheirlocationwithinthewebcomponent/application.Itisimportanttomaintainconsistencyandensurepredictablesystemresponses.SomeHTML/ARIAstandardsarenotsupportedbybrowsers,webapplications,andscreenreaders.Tofollowpervasivestandardsispractical,butadditionalworkmayberequiredtoensurefunctionality.

TechniquesandMethods:1.1.TestcurrentDLplatformwithrecommendedapplicationssuchasscreen-readersoftware,includingupcomingreleases,whenavailable1.2.TestcurrentDLplatformwithcommonbrowsersandoperatingsystems1.3.ConductusertestingwithpilotcollectionsandthenmodifyorenhancefeaturesandcapabilitiesthatarefoundtobeproblematicbeforeDLlaunch

134

2.1.Scheduleregular,recurringaccessibilityandusabilitytestingofaDLwithrealusers,includingdiversescreen-readersoftware,Webbrowserapplications,andoperatingsystems3.1.ProviderecommendationsofpreferredbrowsersthataremostcompatiblewithagivenDLsystem3.2.Providerecommendationsforwhichhelperapplications,screen-readers,andassistiveplatformsarecompatibleandsupportedforagivenDLsystem4.1.ProvidealternativetextorsoundalertstonotifytheuserwhenthefocusmovesinoroutoftheDL

RecommendedFeatures:3.1Recommendedcompatiblebrowsersandapplications3.2.Instructions/tips4.1.Textandsoundalerts

Examples:1.1./1.2./3.1./3.2.ScreenreadercompatibilityforsomeoftheHTMLcodes(e.g.<span>and<br>arereadas“blank”inInternetExplorer)indifferentbrowsers.

*Somescreenreadersmaynotworkinaspecificbrowser.Forexample,inMicrosoftEdge,JAWSisnotworkingwell.Headingsandlabelswerenotread(recognized)byJAWS.H(forheading),tab,andarrowkeysarenotworkingcorrectly.TheoveralldescriptionforthewebpagestructureisnotprovidedbyJAWS,either.

RelatedResources:

135

Noupe.(2009).SimplicityinGoodWebDesign:Advantages&How–to.Retrievedfromhttps://www.noupe.com/design/simplicity-in-good-web-design-advantages-how-to.htmlPowerMapper.(2017).HTMLelements:Screenreadercompatibility.Retrievedfromhttps://www.powermapper.com/tests/screen-readers/elements/Xie,I.,Babu,R.,Joo,S.,&Fuller,P.(2015).Usingdigitallibrariesnon-visually:Understandingthehelp-seekingsituationsofblindusers.InformationResearch:AnInternationalElectronicJournal,20(2),paper673.Retrievedfromhttp://InformationR.net/ir/20-2/paper673.html.WCAG2.0Guidelines1.1,1.2,1.3,1.4.(2008).Retrievedfromhttps://www.w3.org/TR/WCAG20/#perceivableWCAG2.0Guideline3.2Predictable.(2008).Retrievedfromhttps://www.w3.org/TR/WCAG20/#consistent-behaviorSeeAlso:Help-seekingSituations>DifficultywithcompatibilityissuesHelp-seekingSituations>Confusionaboutmultipleprogramsandstructures

136

Glossary A Accesspathway Navigation features that indicate the ways an item can be accessed.

Altattribute An HTML attribute that provides information in an alternative format for an image on a webpage using a text display. It is used when a user cannot view an image and wants to read the text alternative instead.

AlternativeText(AltText) A word or phrase (typically less than 100 characters long) used in the Alt Attribute of an image item or graphical interface element that describes its content or function in the context.

ARIA The acronym for Accessible Rich Internet Applications. It is a set of attributes that define ways to make web content and web applications more accessible to people with disabilities.

B Browsingstructure A function or feature that organizes the digital collections in a digital library for easier skimming.

BVI The acronym for Blind and Visually Impaired, and it refers to BVI users who rely on screen readers to understand DL content.

C Caption A text transcription for the audio track of a movie or video, and it synchronizes with the audio of a video. Captions are designed to ensure the viewer can understand all of the essential audio in the video including not only the spoken audio but also the non-speech sounds that are essential to the understanding of the video and are normally shown in brackets.

Colorcontrast The difference in luminance between two colors (adjacent or overlaid).

Contentchangeindicator A cue, such as a sound alert or notification that informs or provides awareness to BVI users when dynamic content is changing within a page without a user’s input.

137

Context-sensitivehelp A help function that delivers immediate assistance to the user without the user having to leave the current context they are working in.

CSS The acronym for Cascading Style Sheets. It is used to format webpage layouts by defining styles for text, tables, and other elements in a webpage’s HTML.

D Description It is one of the metadata elements which offer text summary for a digital object.

DL(s) The acronym for Digital Library or Digital Libraries

DynamicFeatures Features of a digital library, such as a play button, a Flash player, or a banner, change their content with or without a user’s input.

E F Functionaldescription A description that explains a function and its role (what it is, how it works) in a digital library.

G H HandwrittenTextRecognition(HTR) Technology that transcribes handwritten text contained in scanned images into digital text.

High-qualityrecognition A high resolution setting for image scanning and text recognition. For digital images, the recommended scan level is at least 400 dpi for high quality.

I Imagedescription A text statement that provides detailed description of an image, and it is one element of the metadata.

Interactiveaudio A sound technology that creates audio in real-time in reaction to a user’s action or changes in the digital environment.

138

Intuitivelabel A label of the feature, based on common knowledge or a given title name, which is as close to the targeted user’s expectation as possible.

J JAWS The acronym for Job Access with Speech (Screen Reader program). One of the screen readers for blind and visually impaired users.

K Keyboardaccessibleelements All the elements and functions in a digital library, such as clickable icons and buttons, which are navigable and operable by keyboard without any interruption.

L LocationIndicators Indicators that provide the exact location or position within a digital library that a user is currently interacting with.

Looped-animationindicator An audio indicator for when a user interacts with an animation that repeats images seamlessly, such as animated GIFs or banners.

M Metadata It is commonly called as ‘data about data’ that includes structured data to describe and organize resources in the digital environment and enables users to discover and use the content of digital libraries.

N Navigationindicators An indicator that shows where a user is currently located in a digital library and which sections they have browsed through.

O OCR The acronym for Optical Character Recognition. It is a method to convert physical text, such as printed text or handwritten text, to digital text by scanning physical documents.

139

Onlineitemfilter A filter that shows whether an item can be available online or only offline, or both. It can also provide file formats, such as HTML, Word, or PDF.

P Placeholdertext A character, word or sentence that temporarily fills the space in a box until it is ready to be used.

Pre-existingtext Text, such as a placeholder text or a previous search term input by the user, which is already listed in a digital library’s input box or search box.

Q R

S Screenreader A software program that reads textual information through synthesized speech, and it offers specialized keyboard commands to operate a computer interface.

Scannedimage A digitized version of an image created using a scanning device or a digital camera

SearchInstruction/searchtips An explanation of how to use search tools or functions in a digital library.

Searchjargonexplanation Explanation for specialized language, vocabulary, or terms that are used for search functions or search methods

Searchtermdisplay A populated list of suggested search terms that automatically appear in a search box after a user enters a query in a digital library.

Skip-linkforvisualitems A feature that allows a user to jump to visual items, such as images.

Snippet/summary A brief description that summarizes a list of items, search results, or collections.

140

Sortingoptions Arranging or ordering information or data by certain criteria, such as time or publication year.

Speechrecognitiontechnique A technique that converts an analog speech signal to a digital sequence of words using computer programs.

Staticcontent Content that can be delivered to an end user without having to be generated, modified, or processed.

Structuredescription A statement for providing information on a current interface framework and layout of a digital library.

Subtitle A text description displays at the bottom of a video screen that translates or transcribes the audio dialogue, and it synchronizes with the audio of a video. It does not include non-speech elements.

T Transcript A text script that is derived from audio tracks or scanned documents.

U V W WCAG The acronym for Web Content Accessibility Guidelines. These are guidelines created by W3C to increase accessibility in the web environment for users who have had difficulty accessing information resources on the web.

X

Y Z

141

References 3PlayMedia. (2018). Transcription vs. Captioning – What’s the Differnce?. Retrieved from https://www.3playmedia.com/2018/10/10/transcription-vs-captioning/ ABBYY. (n.d.). What is OCR and OCR technology? Retrieved from https://www.abbyy.com/en-us/finereader/what-is-ocr/ American Foundation for the Blind. (n.d.). Screen readers. Retrieved from https://www.afb.org/blindness-and-low-vision/using-technology/assistive-technology-products/screen-readers Baker, J. (2018). The science of color contrast – an expert designer’s guide. Retrieved from https://medium.muz.li/the-science-of-color-contrast-an-expert-designers-guide-33e84c41d156 Berkeley Web Access. (2014). What is a screen reader anyway? Retrieved from https://webaccess.berkeley.edu/ask-pecan/what-is-a-screen-reader Bosco, G. (n.d.). Translation Techniques. Retrieved from https://www.interproinc.com/blog/translation-techniques Collins. (n.d.). Context-sensitive. Retrieved from https://www.collinsdictionary.com/us/dictionary/english/context-sensitive Colorsontheweb. (n.d.). Color Contrast. Retrieved from www.colorsontheweb.com/Color-Theory/Color-Contrast Computer Hope. (2019). Placehoder text. Retrieved from https://www.computerhope.com/jargon/p/plactext.htm Dictionary.com. (n.d.). Intuitive. Retrieved from https://www.dictionary.com/browse/intuitive?s=ts Dictionary.com. (n.d.). Jargon. Retrieved from https://www.dictionary.com/browse/jargon Dictionary.com. (n.d.). Search Term. Retrieved from https://www.dictionary.com/browse/search-term?s=t Dictionary.com. (n.d.). subtitle. Retrieved from https://www.dictionary.com/browse/subtitle?s=t Dictionary.com. (n.d.). Caption. Retrieved from https://www.dictionary.com/browse/caption Docparser. (n.d.). What is OCR and What is it used for?. Retrieved from https://docparser.com/blog/what-is-ocr/ Dynamsoft. (2016). Recommended scan settings for the best OCR accuracy. Retrieved from https://www.dynamsoft.com/blog/insights/scan-settings-for-best-ocr-accuracy/ Eplublisher. (2019). Understanding Context-Sensitive Help. Retrieved from https://www.webworks.com/Documentation/Reverb/index.html#page/Preparing%20and%20Publishing%20Content/Preparing%20DITA%20Files.3.13.htm Freecodecamp. (n.d.). Basic HTML and HTML5:Add placehoder text to a text field. Retrieved from https://learn.freecodecamp.org/responsive-web-design/basic-html-and-html5/add-placeholder-text-to-a-text-field/ Gaikwad, S., Gawali, B., Yannawar, P. (2010). A review on Speech Recognition Technique. Retrieved from https://pdfs.semanticscholar.org/1062/8132a34301f66a0af4bc485f05e3988cdc44.pdf Gibb, R. (2016). What is Static Content? Retrieved from https://blog.stackpath.com/static-content/ Henri. (2016). 25 Examples of excellent navigation indicator designs. Retrieved from https://bashooka.com/inspiration/25-examples-of-excellent-navigation-indicator-designs/

142

Mathieu. (2016). 7 Translation techniques to facilitate your work. Retrieved from https://culturesconnection.com/7-translation-techniques/ Merriam-Webster. (n.d.). Description. Retrieved from https://www.merriam-webster.com/dictionary/description Projectbarbq.com. (2003). Group report: What is IS Interactive Audio? And What Should It Be?. Retrieved from https://www.projectbarbq.com/bbq03/bbq03r5.htm Raventools. (n.d.). What is the ALT Attribute?. Retrieved from https://raventools.com/marketing-glossary/alt-attribute/ Ross, Rob. (2001). Interactive Music…er, Audio. Retrieved from https://www.gamasutra.com/view/feature/131489/interactive_musicer_audio.php TechTerms. (n.d.). CSS. Retrieved from https://techterms.com/definition/css Thomas Walker (2017). Enhance Your User Help Experience with Context-Sensitive Help in Confluence. Retrieved from https://www.k15t.com/blog/2018/02/enhance-your-user-help-experience-with-context-sensitive-help-in-confluence Veroniiica. (2018). How to write alt text and image descriptions for the visually impaired. Retrieved from https://www.perkinselearning.org/technology/blog/how-write-alt-text-and-image-descriptions-visually-impaired W3C. (2001). Metadata and Resource Description. Retrieved from https://www.w3.org/Metadata/ W3C. (2003). WAI (Printable) Glossary. Retrieved from https://www.w3.org/WAI/GL/Glossary/printable.html W3C. (2008). 2.1.1.Keyboard. Retrieved from https://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable W3C. (2016). WAI-ARIA Overview. Retrieved from https://www.w3.org/WAI/standards-guidelines/aria/ W3schoos.com. (n.d.). HTML <img> alt Attribute. Retrieved from https://www.w3schools.com/tags/att_img_alt.asp Watson, L. (2005). What is a screen reader?. Retrieved from https://www.nomensa.com/blog/2005/what-screen-reader WebAIM. (n.d.). Keyboard Accessibility. Retrieved from https://webaim.org/techniques/keyboard/ WhatIS.com. (2012). alt text (alternative text). Retrieved from https://whatis.techtarget.com/definition/alt-text-alternative-text WordStream. (n.d.). Search Term:What are Search Term?. Retrieved from https://www.wordstream.com/search-term Xie, I., Babu, R., Joo, S. & Fuller, P. (2015). Using digital libraries non-visually: understanding the help-seeking situations of blind users. Information Research, 20(2), paper 673. Retrieved from https://files.eric.ed.gov/fulltext/EJ1065689.pdf Xie, I., & Matusiak, K. (2016). Discoverdigitallibraries:Theoryandpractice. Elsevier.