<?xml version="1.0" encoding="utf-8"?>
<article xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="JATS-journalpublishing1-mathml3.xsd" dtd-version="1.2" article-type="Dialog Box">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">weave</journal-id>
<journal-title-group>
<journal-title>Weave (WEAVE)</journal-title>
</journal-title-group>
<issn pub-type="epub"></issn>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">7583</article-id>
<article-id pub-id-type="manuscript">elements-structure-aesthetics-sy-edits-iv-revisions.docx</article-id>
<article-id pub-id-type="doi">10.3998/weaveux.7583</article-id>
<title-group>
<article-title>Elements, Structure, and Aesthetics: Improving Usability and Accessibility on a Library Website Home Page</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Ochoa</surname>
<given-names>Isabel Vargas</given-names>
</name>
<email>ivargas2@csustan.edu</email>
<aff id="aff1"><institution>CALFORNIA STATE UNIVERSITY, STANISLAUS</institution></aff>
</contrib>
</contrib-group>
<pub-date><day>21</day><month>4</month><year>2026</year></pub-date>
<volume>9</volume><issue>1</issue>
<issue-title></issue-title>
<fpage></fpage>
<lpage></lpage>
<history>
<date date-type="received"><day></day><month></month><year></year></date>
<date date-type="rev-recd"><day></day><month></month><year></year></date>
<date date-type="accepted"><day>10</day><month>11</month><year>2025</year></date>
</history>
<permissions>
<copyright-statement></copyright-statement>
<copyright-year></copyright-year>
<license><license-p>CC BY 4.0</license-p></license>
</permissions>
<abstract id="ABS1"><p id="P1">I describe redesigning a university library home page to improve usability for students and enhance accessibility by meeting WCAG 2.2 level AA standards for state and local government websites. I modified content and elements on the home page aimed at improving the website&#x2019;s design for usability. Before implementing the redesigned home page, I conducted a usability study with university students to test both the redesigned home page prototype and the existing home page. Students preferred the redesigned home page; however, feedback from students also described continued challenges with library terminology.</p></abstract>
<kwd-group>
<kwd></kwd>
</kwd-group>
<funding-group/>
<counts>
<fig-count count="4"/>
</counts>
<custom-meta-group>
<custom-meta id="competing-interest">
<meta-name></meta-name>
<meta-value></meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec id="S1"><title>Background</title>
<p>The University Library website of the California State University, Stanislaus, provides resources for Stanislaus and San Joaquin counties and surrounding communities in the state. The university&#x2019;s student population is 71 percent first generation, 67 percent female, and 62 percent Hispanic/Latino(a), thus making it a Hispanic Serving Institution (<xref ref-type="bibr" rid="R2">California State University, Stanislaus, 2023</xref>).</p>
<p>I conducted an assessment and study in the spring of 2020 to test the library website for its menu navigation design and its use of library terminology (<xref ref-type="bibr" rid="R9">Vargas Ochoa, 2020</xref>). Since then, the library website has aimed to provide accessible and user-friendly web pages, resources, and content. In 2024 the Federal Register published the Department of Justice&#x2019;s final rule updating its regulations for Title II of the Americans with Disabilities Act, requiring local and state governments to adhere to WCAG Version 2.1 level AA as the technical standard for accessibility in their websites (U.S. Department of Justice Civil Rights Division, 2024). Essentially, our library website must ensure that its content is accessible and meets technical standards, advancing the plan to improve the website&#x2019;s overall usability for our students and campus community.</p>
<p>A library home page influences not only a student&#x2019;s learning experience, but their perception of library resources and services and whether students will return to the library. In fall 2024, the library website had various elements on its home page:
<list list-type="bullet">
<list-item><p>library catalog</p></list-item>
<list-item><p>library hours</p></list-item>
<list-item><p>social media section</p></list-item>
<list-item><p>research help button links</p></list-item>
<list-item><p>reservation quick links</p></list-item>
<list-item><p>carousel slideshow for events and news &#x2022;	calendar of events</p></list-item>
<list-item><p>featured databases</p></list-item>
<list-item><p>slideshow of featured books</p></list-item>
</list>
Over time, we added content to the home page as we expanded and promoted our services. These elements were stacked closely in similar shapes and font sizes, creating a uniform but overcrowded design. To begin redesigning the website with usability and accessibility in mind, I focused on spacing out elements, grouping related elements, and implementing diverse colors and font designs, based on other academic library websites and findings from recent library website usability studies from the University of Toronto (Guay et al., 2018) and the University of South Africa (<xref ref-type="bibr" rid="R7">Tella, 2019</xref>).</p>
<p>Organized and minimal spacing helps users navigate through the various promoted elements on the home page. If spacing is tight or scarce, the user may not know where to start finding information. Blank space, or minimal spacing, helps users identify key elements and highlighted content (<xref ref-type="bibr" rid="R1">Alonso-Virg&#x00F3;s et al., 2019</xref>). Grouping related elements also creates a structure that directs users to certain elements based on priority. Having grouped elements with similar shapes, colors, or under the same section or heading provides clarity. Grouped elements positioned at the top or top-left areas of the home page are also areas that attract users&#x2019; attention, and designers should consider this when organizing and prioritizing content (<xref ref-type="bibr" rid="R6">Still, 2018</xref>).</p>
<p>Redesigning the library home page to improve accessibility and usability required grouping and restructuring elements, minimizing and resizing content, implementing simple aesthetics in relation to the organization&#x2019;s theme, and ensuring the website continues to meet accessibility guidelines.</p>
</sec>
<sec id="S2"><title>Redesigning the Home Page</title>
<p>In addition to consulting the website&#x2019;s analytics, I referred to recently published literature on website optimization and redesign, including <xref ref-type="bibr" rid="R3">Firth&#x2019;s <italic>Practical Web Accessibility</italic> (2024)</xref>, <xref ref-type="bibr" rid="R6">Still&#x2019;s (2018)</xref> article on web page visual hierarchy, <xref ref-type="bibr" rid="R5">Khawaja&#x2019;s (2023)</xref> article on accessibility and public libraries, and an article on web developers&#x2019; recommended usability guidelines (Alonso-Virgos et al., 2019). Following this, there were many modifications to make to the elements and contents on the library&#x2019;s home page. I made significant changes in the grouping and positions of content and elements. For example, I grouped research-help links and reduced them from five links to three. I also eliminated quick links to library services based on their usage according to our website&#x2019;s analytics.</p>
<p>In terms of visual design, I focused on the size of content, number of elements, and location on the page. I increased the font size and image size to improve usability. I reconfigured the structure of the home page by adding blank space to increase visibility of certain elements, giving users a visual break from the various sections and further highlighting elements. I removed links and text with little user interaction to provide a minimalist structure, and I enlarged other elements for visual clarity.</p>
<fig id="F_1" position="float"><label>Figure 1.</label><caption><p>The screenshot on the left is of the then current home page. There are visibly more boxes of content, the content is congested in width, and the website is longer in height. The image on the right depicts the redesigned home page. There are less boxes of content, highlighted content is bigger in size, and the content feels more spaced out.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="weaveux.7583-f0001.jpg" /></fig>
<sec id="S3"><title>Accessibility</title>
<p>I also implemented these changes in conformity with WCAG level AA guidelines. Screen readers look at certain labels, including the role of the website&#x2019;s content, such as whether it&#x2019;s a link or a button; the content&#x2019;s name, label, and description; or the status of the content, such as whether it&#x2019;s a disabled or checked box (<xref ref-type="bibr" rid="R3">Firth, 2024</xref>). Screen readers scan content through heading structure and reading order. When reenvisioning the layout of the homepage, I focused on reading order and heading structure by initially designing the elements in a linear layout to see what elements were more prominent and viewed first. You can view the linear layout of your web page by removing CSS in the &#x201C;Inspect&#x201D; view in your browser. You may also select the Accessibility Tree View while in the &#x201C;Inspect&#x201D; view to see how screen readers interpret your home page&#x2019;s content structure.</p>
<p>Most home pages are designed first to be visually appealing, but it&#x2019;s important not to prioritize aesthetics over accessibility. Some changes I made to the redesigned home page were:
<list list-type="bullet">
<list-item><p>selected a sans serif font family for all content&#x2014;except for the font family for the headings which I selected for aesthetics and campus website uniformity</p></list-item>
<list-item><p>changed font size from using pixels to using relative units, with most of the content at 1.2rem and for all else to be at least 1rem</p></list-item>
<list-item><p>enabled navigable controls for the carousel slideshow</p></list-item>
<list-item><p>distinguished links through text decoration like underlining, borders, textured background images, or text decoration on hovering, and ensured links had a focus when navigated through keyboard keys</p></list-item>
<list-item><p>added empty attributes to decorative images since they are ignored by screen readers, in addition to adding clear alternative text</p></list-item>
<list-item><p>modified size of images and font for mobile responsiveness</p></list-item>
<list-item><p>added descriptions, captions, or links to images unless purely decorative</p></list-item>
<list-item><p>added hidden headings for screen readers for content that is visually distinguishable but does not have a heading</p></list-item>
<list-item><p>added ARIA landmarks throughout the home page, including roles for the header, navigation, main sections, and footer</p></list-item>
<list-item><p>used ARIA labels for content with icons and added descriptions for buttons with little text</p></list-item>
</list>
Additionally, I made content on the home page larger but not overwhelming on the average computer screen size (21 to 27 inches) to prevent overstimulation for the user. For users with cognitive impairments, using spatial comprehension, clear highlighted content, and universal iconography is important, along with the use of simple language and active voice.</p>
<p>After designing the prototype, I ran accessibility reports using accessibility checking tools such as accessibilitychecker.org and WAVE Web Accessibility. I also used WebAIM&#x2019;s contrast checker and manually navigated the website home page using my computer&#x2019;s keyboard. To assess the drafted redesign of the library home page and to collect feedback, I created a usability study for students to test the home pages.</p>
</sec>
<sec id="S4"><title>Designing the Usability Study</title>
<p>I designed the home page usability study to test the new elements on the prototype home page and compare the prototype to the existing home page. I also gathered written feedback from the students in the form of a questionnaire at the end of the usability study.</p>
<p>I conducted the usability study in the fall semester of 2024 on three separate dates in the libraries of the main campus and the regional campus. During the scheduled days, students participated on a walk-in basis in both the morning and afternoon.</p>
<p>The study included sixteen tasks and a written questionnaire. There were eight tasks to test the prototype home page and a duplicate of the same eight tasks to test the then-current home page. The two different task groups were labeled Group A and Group B. Group A began with testing the prototype home page then tested the current home page, and Group B began with the current home page then tested the prototype home page. This was to prevent the results from being skewed, since it may be easier for students to complete tasks on the second home page after completing the tasks on the first home page, regardless of what that first home page was. I used the software Snagit to record the students&#x2019; computer screens as they completed the tasks. I saved and collected their videos anonymously and labeled each video by number and group.</p>
<p>I recruited students by asking some faculty and staff to share the usability study flyer with their students. I also recruited through the library&#x2019;s social media platforms, the library website, and through the campus&#x2019; disability services for students. Incentives to encourage participation were two gift card raffles, snacks, and extra credit. </p>
</sec>
</sec>
<sec id="S5"><title>Findings from the Usability Study: Data Collected and Results</title>
<p>Fifteen students participated in the usability study. Students completed the usability study in an average of 20 minutes. I invited Disability Resource Services students, or students registered with disabilities, to participate; however, if they participated, their disability status was not recorded.</p>
<sec id="S6"><title>Tasks</title>
<p>The tasks asked students to find content in the following topics: course reserves, research guides, library exhibits, study rooms, library hours, featured databases, featured books, and materials request. For Group A, who tested the prototype home page first, it was more difficult to find &#x201C;course reserves&#x201D; on the prototype page than on the current home page. Students testing the current home page first, Group B, had a lot more difficulty completing tasks on finding library exhibits, the featured databases, and submitting a materials request than students testing the prototype home page. Overall, finding course reserves and library exhibits and submitting a materials request were difficult for both Group A and Group B students to complete on both home pages.</p>
<p>In the second half of the testing, students completed tasks at a much faster rate for both home pages in comparison to the first home pages they tested. However, students continued to have difficulty finding course reserves, library exhibits, and submitting a materials request.</p>
</sec>
<sec id="S6a"><title>Questionnaire</title>
<p>I gave the written questionnaire to the students after they completed the tasks for both home pages. The questionnaire included a rating scale and open-ended questions that asked students for suggested improvements and feedback on the home pages. <xref ref-type="fig" rid="F_2">Figure 2</xref> shows the results of the Usability Study Questionnaire.</p>
<fig id="F_2" position="float"><label>Figure 2.</label><caption><p>This chart illustrates the participants&#x2019; overall rating of the prototype home page in comparison to the current home page</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="weaveux.7583-f0002.jpg" /></fig>
<p /><p>Based on the rating scale in the questionnaire, most participants found the prototype home page easier to navigate than the current home page and was overall preferred.</p>
<p>Written suggestions for the prototype home page included improvements in the elements&#x2019; size and color. Many students expressed wanting to see more colors to distinguish the different sections and buttons, instead of the one-color campus theme. A student commented that some of the sections on the prototype home page &#x201C;take up space on the screen,&#x201D; while another student commented that they would like to see bigger text. Two students expressed their confusion with library jargon, specifically with the tasks that asked them to find library course reserves and library exhibits. Most of the participants commented that they liked the organizational structure of the redesigned prototype home page and felt it was easier to navigate than the current home page. One student commented that they liked how &#x201C;topics were grouped together.&#x201D;</p>
</sec>
</sec>
<sec id="S7"><title>Implementing the Redesigned Prototype</title>
<p>I implemented the redesign of the home page in January 2025, during the university&#x2019;s academic break and before the start of the spring semester. I modified the prototype home page based on student feedback and suggestions for improvement and observations from the usability study. <xref ref-type="fig" rid="F_3">Figure 3</xref> shows our previous homepage design. <xref ref-type="fig" rid="F_4">Figure 4</xref> shows the redesigned homepage.</p>
<fig id="F_3" position="float"><label>Figure 3.</label><caption><p>Our previous homepage with boxed content and various buttons that do not have distinguishable features, and groups of content that are not needed on the homepage.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="weaveux.7583-f0003.jpg" /></fig>
<fig id="F_4" position="float"><label>Figure 4.</label><caption><p>Our redesigned home page with ample use of the screen width and less content that previously increased the height.</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="weaveux.7583-f0004.jpg" /></fig>
<p /><p>I minimized blank space on the prototype home page to reduce excessive space. At first I had significantly increased the font size of text headings on the prototype home page, but after the usability study I decreased them slightly, along with the size of buttons and content sections, specifically the gallery slideshow image size. Even so, the content sections remain bigger than the<italic> </italic>previous home page&#x2019;s content sections. I implemented the university&#x2019;s secondary colors, along with the primary colors, to add variety to the content. I added patterns to the button backgrounds for the content that was grouped by theme and separated by color to adhere to accessibility recommendations for users who do not see colors. I tested changes to the home page to ensure it was meeting WCAG AA guidelines for accessibility using accessibility checking tools previously mentioned. I checked content structure and order manually as recommended by accessibility tools. If users find an accessibility issue, they can submit a new form on the website&#x2019;s footer. </p>
</sec>
<sec id="S8"><title>Findings After Implementation</title>
<p>To assess the engagement of the redesigned home page after the implementation, I compared the home page&#x2019;s analytics using the platform Crazyegg, a heatmaps tool. Before implementing the redesign, the top three durations it took users to click on an element or link on the home page were:
<list list-type="order">
<list-item><p>1.5&#x2013;2 seconds (16 percent of clicks)</p></list-item>
<list-item><p>3&#x2013;4 seconds (10 percent of clicks)</p></list-item>
<list-item><p>10&#x2013;15 seconds (8 percent of clicks)</p></list-item>
</list>
After implementing the redesign, the top three durations it took for users to click on an element or a link were similar, however with higher percentages:
<list list-type="order">
<list-item><p>1.5&#x2013;2 seconds (19 percent of clicks),</p></list-item>
<list-item><p>3&#x2013;4 seconds (10 percent of clicks),</p></list-item>
<list-item><p>10&#x2013;15 seconds (8.7 percent of clicks)</p></list-item>
</list>
After the redesign, users found information quicker; however, we had fewer visits than the semester before. Both factors may be influenced by the fact that I collected the statistics halfway through the academic year when students had already been using the library website. I also compared the visual engagement in our heat map analytics on both home pages in the first thirty days of the fall and spring semesters, before and after the redesign. Before the redesign, the buttons for &#x201C;course reserves,&#x201D; &#x201C;ask a librarian,&#x201D; and the sections for &#x201C;events calendar&#x201D; and &#x201C;featured databases&#x201D; had little to no engagement. After the redesign, there was an increase in visits to &#x201C;course reserves,&#x201D; &#x201C;events calendar,&#x201D; and &#x201C;library exhibits.&#x201D;</p>
</sec>
<sec id="S9"><title>Limitations and Reflection</title>
<p>A challenging aspect of the study was seeing how much students struggled with specific library terminology. Phrases like &#x201C;library exhibits,&#x201D; &#x201C;materials request,&#x201D; &#x201C;course reserves,&#x201D; and &#x201C;featured databases&#x201D; confused students. To complete tasks using these library terms, students used both the library website&#x2019;s search function and an outside search tool as they sought to define the terms. Some students even searched for these terms using the library catalog.</p>
<p>For example , for the &#x201C;featured databases&#x201D; task, students clicked on the &#x201C;all databases&#x201D; link on the home page instead of scrolling down to view the featured databases section also on the home page. This behavior wasn&#x2019;t unsuccessful, as the &#x201C;all databases&#x201D; web page also promoted featured databases; however, it wasn&#x2019;t the expected way of accessing them, especially since they were testing the home page. Library terminology has been and will continue to be a barrier when it comes to patron engagement in library services and resources, especially when navigating content online (<xref ref-type="bibr" rid="R4">Guay et al., 2019</xref>). Adding icons and grouping elements can help students contextualize the terminology and better understand their meanings. To adhere to accessibility guidelines, the library website should also be mobile responsive. The current mobile version of the library website is user-friendly and accessible; however, it was not part of the usability study. For future studies, testing mobile screens will help note areas of improvement for the home page on smaller screens. Implementing a card sorting task will also be instrumental. Asking students to group elements on the home page will help library staff identify what library services and terminology users understand and are familiar with. This usability study demonstrated that our current students agreed with grouping similar elements together and removing unnecessary content to maintain a minimalistic approach. Although students preferred a home page with bigger elements and more colors, to ensure accessibility and usability, the size of the elements should not take up most of the standard computer screen size, and aesthetic features should be compatible with accessibility guidelines. </p>
</sec>
</body>
<back>
<ref-list><title>References</title>
<ref id="R1"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Alonso-Virg&#x00F3;s</surname>, <given-names>L.</given-names></string-name>, <string-name><surname>Espada</surname>, <given-names>J. P.</given-names></string-name>, &amp; <string-name><surname>Crespo</surname>, <given-names>R. G.</given-names></string-name></person-group> (<year>2019</year>). <article-title>Analyzing compliance and application of usability guidelines and recommendations by web developers</article-title>. <source>Computer Standards and Interfaces</source>, <volume>64</volume>, <fpage>117</fpage>&#x2013;<lpage>132</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.csi.2019.01.004">https://doi.org/10.1016/j.csi.2019.01.004</ext-link></mixed-citation></ref>
<ref id="R2"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>California State University, Stanislaus</collab></person-group>. (<year>2023</year>, <month>April</month> <day>12</day>). <source>Quick facts</source>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.csustan.edu/iea/institutional-data/quick-facts">https://www.csustan.edu/iea/institutional-data/quick-facts</ext-link></mixed-citation></ref>
<ref id="R3"><mixed-citation publication-type="book"><person-group person-group-type="author"><string-name><surname>Firth</surname>, <given-names>A.</given-names></string-name></person-group> (<year>2024</year>). <source>Practical web accessibility: A comprehensive guide to digital inclusion</source> (<edition>2nd</edition> ed.). <publisher-name>Apress</publisher-name>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1007/979-8-8688-0152-5">https://doi.org/10.1007/979-8-8688-0152-5</ext-link></mixed-citation></ref>
<ref id="R4"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Guay</surname>, <given-names>S.</given-names></string-name>, <string-name><surname>Rudin</surname>, <given-names>L.</given-names></string-name>, &amp; <string-name><surname>Reynolds</surname>, <given-names>S.</given-names></string-name></person-group> (<year>2019</year>). <article-title>Testing, testing: A usability case study at University of Toronto Scarborough Library</article-title>. <source>Library Management</source>, <volume>40</volume>(<issue>1&#x2013;2</issue>), <fpage>88</fpage>&#x2013;<lpage>97</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1108/LM-10-2017-0107">https://doi.org/10.1108/LM-10-2017-0107</ext-link></mixed-citation></ref>
<ref id="R5"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Khawaja</surname>, <given-names>P.</given-names></string-name></person-group> (<year>2023</year>). <article-title>Accessibility of public library websites in the United States</article-title>. <source>Universal Access in the Information Society</source>, <volume>22</volume>(<issue>3</issue>), <fpage>1047</fpage>&#x2013;<lpage>1057</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1007/s10209-022-00866-y">https://doi.org/10.1007/s10209-022-00866-y</ext-link></mixed-citation></ref>
<ref id="R6"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Still</surname>, <given-names>J. D.</given-names></string-name></person-group> (<year>2018</year>). <article-title>Web page visual hierarchy: Examining Faraday&#x2019;s guidelines for entry points</article-title>. <source>Computers in Human Behavior</source>, <volume>84</volume>, <fpage>352</fpage>&#x2013;<lpage>359</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.chb.2018.03.014">https://doi.org/10.1016/j.chb.2018.03.014</ext-link></mixed-citation></ref>
<ref id="R7"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Tella</surname>, <given-names>A.</given-names></string-name></person-group> (<year>2019</year>). <article-title>The determinants of library and information science undergraduate students&#x2019; first impression of university library websites</article-title>. <source>Education and Information Technologies</source>, <volume>24</volume>(<issue>1</issue>), <fpage>277</fpage>&#x2013;<lpage>294</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.1007/s10639-018-9769-4">https://doi.org/10.1007/s10639-018-9769-4</ext-link></mixed-citation></ref>
<ref id="R8"><mixed-citation publication-type="web"><person-group person-group-type="author"><collab>U.S. Department of Justice Civil Rights Division</collab></person-group>. (<year>2024</year>, <month>April</month> <day>8</day>). <source>Fact sheet: New rule on the accessibility of web content and mobile apps provided by state and local governments</source>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="uri" xlink:type="simple" xlink:href="https://www.ada.gov/resources/2024-03-08-web-rule/">https://www.ada.gov/resources/2024-03-08-web-rule/</ext-link></mixed-citation></ref>
<ref id="R9"><mixed-citation publication-type="journal"><person-group person-group-type="author"><string-name><surname>Vargas Ochoa</surname>, <given-names>I.</given-names></string-name></person-group> (<year>2020</year>). <article-title>Navigation design and library terminology: Findings from a user-centered usability study on a library website</article-title>. <source>Information Technology and Libraries</source>, <volume>39</volume>(<issue>4</issue>), <fpage>1</fpage>&#x2013;<lpage>15</lpage>. <ext-link xmlns:xlink="http://www.w3.org/1999/xlink" ext-link-type="doi" xlink:type="simple" xlink:href="https://doi.org/10.6017/ital.v39i4.12123">https://doi.org/10.6017/ital.v39i4.12123</ext-link></mixed-citation></ref></ref-list>
</back>
</article>
